Unexpected network traffic to SMB shares #7241

Closed
opened 2026-01-31 00:58:45 +00:00 by claunia · 6 comments
Owner

Originally created by @JannesMeyer on GitHub (Apr 1, 2020).

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

image

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

Originally created by @JannesMeyer on GitHub (Apr 1, 2020). # 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](https://news.ycombinator.com/item?id=22325292) you do not expect any outgoing connections unless explicitly requested # Actual behavior ![image](https://user-images.githubusercontent.com/704336/78147397-f963d180-7422-11ea-8d5f-916d04e4f2d0.png) Source is my desktop computer Remote is my NAS device with some SMB file shares (but none of them are mapped to drive letters)
claunia added the Needs-TriageResolution-ExternalNeeds-Tag-FixProduct-Terminal labels 2026-01-31 00:58:45 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Apr 1, 2020):

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

@zadjii-msft commented on GitHub (Apr 1, 2020): 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
Author
Owner

@JannesMeyer commented on GitHub (Apr 1, 2020):

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)

@JannesMeyer commented on GitHub (Apr 1, 2020): 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`)
Author
Owner

@zadjii-msft commented on GitHub (Apr 1, 2020):

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

@zadjii-msft commented on GitHub (Apr 1, 2020): 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`? ```json "disabledProfileSources": ["Windows.Terminal.PowershellCore"] ``` and try again? That should disable the lookup for pwsh installs. You could also try ```json "disabledProfileSources": ["Windows.Terminal.PowershellCore", "Windows.Terminal.Wsl", "Windows.Terminal.Azure", "Windows.Terminal.Telnet"] ``` to be comprehensive about all the possible dynamic profiles
Author
Owner

@JannesMeyer commented on GitHub (Apr 1, 2020):

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.

@JannesMeyer commented on GitHub (Apr 1, 2020): 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.
Author
Owner

@zadjii-msft commented on GitHub (Apr 1, 2020):

Hey no problem! I'm glad it was something in your own config after all, thanks for following up!

@zadjii-msft commented on GitHub (Apr 1, 2020): Hey no problem! I'm glad it was something in your own config after all, thanks for following up!
Author
Owner

@DHowett-MSFT commented on GitHub (Apr 1, 2020):

@JannesMeyer (thanks for following up! I was really curious about this one when I saw you on Hacker News 😄)

@DHowett-MSFT commented on GitHub (Apr 1, 2020): @JannesMeyer (thanks for following up! I was really curious about this one when I saw you on Hacker News 😄)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7241