Windows access to the shared folder, using the SMB protocol, the default use of 139 and 445 ports, the corporate office network does not know why the policy is not allowed to use the 445 port, so usually access to the share is to go 139 port;
The pit daddy is sometimes unexpectedly some office computer cannot access the share, check the service: Server, Workstation, computer Browser, there is no problem, the Microsoft Network file and Printer Sharing also no problem, the firewall is closed, NetBIOS settings are also open, is not accessible;
View Access Port Find this computer only to connect to the server port 445, it is strange, why not go 139, the default should be: If the client enabled NetBIOS, then the connection will be access to both 139 port and 445 port, if the port from 445 to get a response, Then the client will send the RST to port 139, terminate the connection, and then the SMB from the 445 port, if not from the 445 port to get a response, but from 139 to get a response, then the session from the 139 port. NetBIOS Protocol I opened it, why not take effect?
After the final troubleshooting, the original computer name is caused by a duplicate, SMB in the use of NetBIOS with 139 port to establish a connection when the local network will see if there is a duplicate, if the name is the same, to prevent conflict, only use 445 port;
So it's OK to change the computer name.
In fact, this computer is not added to the domain, if added to the domain, there will not be such a problem, and the computer name is not added domain, you must change the computer names restart before you can add a domain.
Windows cannot access the share using port 139