(imported topic written by Sean_Mahanay91)
Does anyone know which ports are used when accessing a nullshare.
Is it TCP 139, TCP, 445, UDP 137, or UDP 138? I think it is TCP 445, but i would like to confirm it.
Thanks
(imported comment written by mynameisbear91)
Sean Mahanay
Does anyone know which ports are used when accessing a nullshare.
Is it TCP 139, TCP, 445, UDP 137, or UDP 138? I think it is TCP 445, but i would like to confirm it.
Thanks
FYI, the term “null share” refers to a share that can be accessed anonymously. When a service starts up with the SYSTEM account (which BigFix does, along with most services on a standard Windows machine) the SYSTEM account logs on with null (basically, zero) credentials. When the BigFix client attempts to connect to the share where your Office files are located, it will be unable to access the share unless the system hosting the files is configured to allow anonymous (unauthenticated) access to the share.
So basically, the short answer is that whatever port(s) your normal users use to access the server from their desktop should be the same port(s) used to connect to a null share. (I don’t even like the term null share, but it’s a holdover from windows NT, where the registry keys to enable null shares on a server contained the phrase “NullShare”)
The long answer is that it depends, but if you are running XP/2003 and higher clients and servers, TCP/445 is a safe bet, because it all rides on top of SMB (445) on XP/2003 and higher. This is still not a complete picture, but it really all depends on what protocols you have enabled.
If anyone has any other input or corrections, feel free. 