Windows Networking - Port 445 Only?
Last response: in Networking
I am trying to find the answer to a simple question...
I have two Windows servers separated by a firewall. (Win2k/Win2k3)
I need to transfer files using robocopy to a local file share on one server, using a local account on that server.
Can I open just Port 445 between the two servers and be able to access the file share?
This requires authenticating to the local account and the ability to transfer files.
If your answer is for me to open 137, 138, 139 or even (shudder) 135 then you'd better have a real reason for suggesting they be opened and provide collaborative documentation, not just linking to outdated pages that suggest opening those ports.
I have two Windows servers separated by a firewall. (Win2k/Win2k3)
I need to transfer files using robocopy to a local file share on one server, using a local account on that server.
Can I open just Port 445 between the two servers and be able to access the file share?
This requires authenticating to the local account and the ability to transfer files.
If your answer is for me to open 137, 138, 139 or even (shudder) 135 then you'd better have a real reason for suggesting they be opened and provide collaborative documentation, not just linking to outdated pages that suggest opening those ports.
More about : windows networking port 445
http://support.microsoft.com/kb/204279
You only need the NetBIOS ports 135, 137, et al., if your OS doesn't support “direct host SMB”. With “direct host SMB”, Windows runs SMB directly over TCP/IP, and thus eliminates the need for those other NetBIOS ports. For backward compatibility, of course, it will try them if necessary.
FWIW, according to the SMB wiki, "Since Windows 2000, SMB by default runs directly on top of TCP — a feature known as "direct host SMB" where the file server listens on TCP port 445 instead of 139."
You only need the NetBIOS ports 135, 137, et al., if your OS doesn't support “direct host SMB”. With “direct host SMB”, Windows runs SMB directly over TCP/IP, and thus eliminates the need for those other NetBIOS ports. For backward compatibility, of course, it will try them if necessary.
FWIW, according to the SMB wiki, "Since Windows 2000, SMB by default runs directly on top of TCP — a feature known as "direct host SMB" where the file server listens on TCP port 445 instead of 139."
Related ressources:
- ForumWindows 2000 server trying to connect port 139 & 445 to an..
- ForumBlocking Port:445 on Windows 2000 Professional
- ForumWindows Xp, svchost.exe connecting to random ips with remote port 445
- ForumSafemode w/ networking works
- ForumWindows 7 x32 hangs/freezes randomly, only safe mode+ networking works
- ForumHigh Ping Times from only my computer
- ForumOnly ethernet port on my mobo just stopped working
- ForumRadeon HD 6850 and Athlon II X3 445 is a bad combination
- ForumAMD athlon ii x3 445 unlocking to phenom x4 failed...
- ForumA6-3500 or atlon ii x3 445 ?
- ForumPort 113 is closed
- ForumHow do I Restrict port access to single IP Address
- ForumDVI No signal, after Windows 8 Startup and Bios screen
- ForumHow I overclocked my Athlon II X3 445 Rana/Biostar A885G+
- Forum80C After Unlocking Athlon II X3 445 ?
- ForumRouter Setup
- ForumI saved C:windows/system32/drivers/etc/hosts in my documents but now it doenst w
- ForumGateway Port Redirection, ACL, RRAS, DHCP, DNS
- Forum[Solved] Port Checker SAys my ports are open but game's server dont work?
- ForumWindows 7 error Network Cable Unplugged
- More resources
Read discussions in other Networking categories
!
