Get the App
SLTechnology News&Howtos  ›  Servers  › 

Windows cannot access the domain server

Shulou Source: shulou.com Published: 2022-06-02 16:33:08 10月03日 Update

Domain server S and client C are on different Lans. C can normally access the domain folder of S before, but due to the influence of blackmail virus, a lot of prevention and control measures have been taken. This includes shutting down many services and blocking firewall ports. Now the antivirus software has been updated and I want to restore access, but I can't connect.

First of all, domain access is mainly on ports 139 and 445. Using both ports tested by telnet ServerIP 139 and telnet ServerIP 445, the connection was found to be fine.

Then use\\ ServerIP access to indicate that you cannot connect.

If it doesn't feel normal, use netstat-ant | findstr ServerIP and check the connection status when you enter\\ ServerIP. It is found that Client is using destination port 80 to access Server. It must be wrong.

Find another C' to confirm. Connection S uses port 445 and everything is fine. Judge that there is something wrong with C.

Du Niang came out, and a man from 51cto introduced to check whether the Computer Browser service is turned on. The inspection found that the service was indeed turned off, turned on immediately, and found that the fault remained the same.

Thanks to that guy for reminding me to check the system service. Besides this, NetBIOS is also a hard-hit area for prevention and control. Check TCP/IP NetBIOS Helper, which is also disabled. Enable, return to normal.

It is concluded that if NetBIOS is not enabled, the workstation will access the domain server on destination port 80. As a reminder of experience.

Tags: Service port check server buddy status purpose different wrong two client client local area LAN workstation feeling I want measures failure file Apple Docker Huawei Linux macOS MariaDB Microsoft MySQL NVidia OPPO Reno Shulou Information Xiaomi Docker Microsoft Redmi