Windows cannot access the domain server

The domain server S is located on a different LAN than client C. C before the normal access to the domain folder s, but due to ransomware virus impact, do a lot of prevention and control measures. This includes shutting down many services and blocking firewall ports. Anti-virus software is now updated to restore access, but there is no connection.

First, domain access is primarily 139 and 445 ports. Using Telnet ServerIP 139 and Telnet ServerIP 445 tested two ports, the connection is found to be OK.

You can then use \\ServerIP access to indicate that you cannot connect.

Not feeling normal, use netstat-ant|findstr ServerIP to view the connection status when entering \\ServerIP. Discover that the client is actually accessing the server with destination port 80. It must have been wrong.

Find another C ' confirmation. Connect s using 445 ports everything is OK. Judge C has a problem.

Degrees Niang, 51cto a man introduced check Computer Browser service is open. The inspection found that the service was closed, opened immediately and found that the failure was still true.

Or thank the man, remind me to check the system services. In addition to this, NetBIOS is also the hardest hit. Checking for TCP/IP NetBIOS Helper is also a prohibited state. Enabled, return to normal.

Conclusion: If NetBIOS is not enabled, the workstation will access the domain server with destination port 80. As a reminder of experience.

This article is from "Balsam Pear" blog, please make sure to keep this source http://golehuang.blog.51cto.com/7499/1929880

Windows cannot access the domain server