Unexpected network traffic to SMB shares

[JannesMeyer]

Steps to reproduce

1. Open terminal
2. Observe the popup about an outgoing connection on port 5000 by your firewall of choice (if it's configured to warn about that)

Expected behavior

According to DHowett on Hacker News you do not expect any outgoing connections unless explicitly requested

Actual behavior

Source is my desktop computer
Remote is my NAS device with some SMB file shares (but none of them are mapped to drive letters)

[zadjii-msft]

That's crazy - I really wouldn't expect that to happen. Does this repro with cmd.exe as your shell? Maybe this is powershell trying to enumerate some file?

Also, what Windows version and Windows Terminal version are you running? I wouldn't expect this on any version, but you never know

[JannesMeyer]

Yes, I have just reproduced it with cmd.exe as the default shell in profiles.json and I have also reproduced it with an empty PowerShell profile (I had some small customisations in my Profile.ps1).

Windows Terminal Version: 0.10.781.0
Windows Version: 10.0.18362.720

Edit: It does not happen with cmd.exe or powershell.exe when I use them in a classic terminal (i.e. Win+R, cmd.exe or powershell.exe)

[zadjii-msft]

Huh, that's certainly weird. Maybe this is caused by us trying to enumerate the pwsh installs you have?

Could you try adding this to the root of your profiles.json?

    "disabledProfileSources": ["Windows.Terminal.PowershellCore"]

and try again? That should disable the lookup for pwsh installs. You could also try

    "disabledProfileSources": ["Windows.Terminal.PowershellCore", "Windows.Terminal.Wsl", "Windows.Terminal.Azure", "Windows.Terminal.Telnet"]

to be comprehensive about all the possible dynamic profiles

[JannesMeyer]

Thanks for your help! It turns out that it was entirely my own fault.

I found an old profile that I had forgotten about... With a custom icon that's being loaded from the NAS...

Sorry for bothering you with this! After removing the custom icon it stopped happening.