Windows xp lan cannot access network neighbors

Windows xp lan cannot access network neighbors

Windows XP is installed on the LAN and cannot be accessed from Windows 98. Windows XP and Windows XP cannot communicate with each other. When the workstation accesses the server, the server name can be seen in the workstation's "Network Neighbor", but no shared content can be seen after clicking it, or the system prompts that no network path or no access is allowed.

The solution is listed now!

1. Check the physical connection between computers.

2. Make sure that TCP/IP is installed on all computers and works properly.

3. Run the ping command to test the connection between two computers in the network.

4. Run the ping command to test whether the name resolution in the network is normal.

5. Correctly install network components.
First, right-click "Network Neighbor"-"properties" and select the NIC to be shared. Set the IP address to the same CIDR Block of the LAN. For example, 192.168.1.x. Check whether NetBIOS is enabled in the Advanced properties of TCP/IP.
In a network system built using winnt4.0, the unique identifier of each host is its NetBIOS name, the system uses WINS service, information broadcast mode, and lmhost file to resolve NetBIOS names to corresponding IP addresses for information communication.
In the internal network system (also known as the LAN), it is very convenient and fast to use NetBIOS name for information communication. However, the unique identifier of a host over the Internet is its FQDN-format domain name (163.com). On the internet, DNS standards are used to resolve a domain name to a corresponding IP address, win2k supports dynamic dns. machines running the Active Directory Service can dynamically update the DNS table.
The WINS service is no longer needed in the Win2k network, but Win2k still supports wins, which is due to backward compatibility. Currently, most networks are hybrid networks, including systems such as WIN98 and WINXP and Win2k. Therefore, NetBIOS must be bound to the TCP/IP protocol to resolve the computer name.
Check whether the "file and print service" component is selected. If it is deselected, "Browse service" is not bound to the NetBIOS interface. A Windows-based computer that becomes a backup browser and does not enable "file and print sharing" cannot share the browsing list with the client. Any computer that will be included in the browsing list must also enable "file and print sharing ".

6. Enable print and file sharing.

7. Start the "Computer Browser" service.

8. Use the Guest account.
Open Control Panel-> User Account or choose Administrative Tools-> Computer Management-> local users and groups to open the Guest account

9. Allow the guest (guest) account to access from the network.
Enter gpedit. MSC, pop up the Group Policy Manager, in 'computer configuration-Windows Settings-local policy-user rights assignment, the policy "Deny access to this computer from the network" prevents access to this computer from the network. If there is a guest account, the solution is to delete the Guest account in the denied access.

10. Firewall:
Make sure that the firewall that comes with WINXP is not enabled. Enable local connection properties-> advanced, and disable the Internet Connection Firewall. If a third-party firewall product is used, see its user manual to ensure that the firewall does not prohibit communications on the following ports: UDP-137, UDP-138, TCP-139, TCP-445 (Win2k and later operating systems only ).
The latest SP2 patch of Windows XP has greatly improved the ICF and has more powerful functions. The ICF has its own settings. After SP2 is installed, the ICF firewall is enabled by default, no external active connections are allowed. Even local applications need to make settings in the license list to access the network.
However, the firewall blocks normal network browsing service communication, and the result is that someone else cannot see your computer in the network neighbors. Is there any perfect way to allow browsing services while enabling the firewall.
If ICF is enabled, open the attribute. In the service column, select Add. The add service dialog box contains four edit boxes, at the top of which is the description service name, which is easy to remember, from top to bottom, the second is the IP address or name of the Application Service. enter 127.0.0.1 to indicate the local machine.
The following is the internal and external port number. The TCP/UDP next to it indicates whether the port is a UDP connection or a TCP connection.
Enter 3 services in the following table.
Name protocol port
NetBIOS Name Service UDP 137
NetBIOS datemediservice UDP 138
NetBIOS session service tcp 139
137/udp -- NetBIOS name server. The NetBIOS Name Server (NBNS) protocol is part of the NetBIOS (netbt) protocol family on TCP/IP, it provides the Host Name and Address ing method on the network accessed Based on NetBIOS name.
138/udp -- NetBIOS datagram. NetBIOS datagram is part of the NetBIOS (netbt) protocol family on TCP/IP. It is used for network login and browsing.
139/tcp -- NetBIOS session service. NetBIOS session service is part of the NetBIOS (netbt) protocol family on TCP/IP. It is used for Server Message Block (SMB), file sharing, and printing.

11. Check whether the RPC, Plug and Play services are enabled, check the permissions of the corresponding system folder, and try to re-register the following Dynamic Link Library:
Regsvr32 netshell. dll
Regsvr32 netmask X. dll
Regsvr32 netman. dll

12. Set the account and password.
As the operating system of the WINNT kernel always tries to use the current local user name and password to access the remote computer first, which may cause access failure, add the user password here.

13. Access "network computers" in multiple ways ".
For example, to open a computer named "killer" on the network, its IP address is 192.168.1.8. If you do not know the IP address of another computer, you can use "Ping computer name" to obtain its IP address.
Use a computer name to access the services provided by NetBIOS. Click the "Start" menu, click "run", enter "// killer" in the address bar, and click "OK ".
Access with an IP address, enter "// 192.168.1.8" in the address input column, and click "OK ".
It takes time to update the computer list by searching for a computer. Searching for a computer can speed up updating the list. Right-click "search computer" in "Network Neighbor", enter the computer name, and click "Search now" to view the computer you want to access. Double-click the computer name on the right to open it.
Access by ing the drive, enter the DOS mode, enter "net view // killer", and press enter to view the shared folders on the computer killer, such as D. Enter net use Z: // killer // d to map the folder D shared by the computer's IBM-ZB to H: disk and type "Z:" at the command prompt :". You will find that you have connected to the killer computer.

 

 

 

Shared access report "no permission" SOLUTION

Access reports do not have permission solution:
1. Set the password of the local administrator account.
2. Set network access mode to Classic mode.
3. Set the user account (added to the guest group) that allows access to the computer from the network ).
4. Set a user account to prohibit access to the computer from the network (delete the guest group ).

Setting method:
Start -->
Run gpedit. msc -->
Computer Configuration -->
Windows Settings -->
Security Settings -->
Local Policies -->

1. user rights assignment --> Access this computer from the network --> Add a guest group.
2. user rights assignment --> Deny access to this computer from the network --> delete a guest group.
3. Security Options --> network access: Sharing and security model for local accounts --> change to Classic mode.

If you do not use the above method, Run regedit:
HKEY_LOCAL_MACHINE/system/CurrentControlSet/control/LSA: Set restrictanonymous to 0.
Change the value of restrictanonymoussam to 0.
The following is a description:
1. restrictanonymous registers settings that control the information of any user on the local machine. If restrictanonymous is set to 0 (default), any user can obtain the information of the local machine through the network, includes the user name, detailed account policy, and shared name. Attackers can exploit this information when attacking computers. With this information, attackers may be able to understand the system administrator account of the current computer, the path shared by the network, and the weak password. To modify the security level, run regedit.exe to edit the registry, go to Zijian HKEY_LOCAL_MACHINE/system/CurrentControlSet/control/LSA and change the value restrictanonymous in this Zijian from insecure 0 to a higher security level value of 1 or 2. Note: If this security level is increased, the computer may be inaccessible within the LAN.
2. When NetBIOS settings in wins in tip/IP advanced options are disabled, the LAN cannot be accessed.
3. If the virus is infected, it will not be able to access the LAN.
4. If the IP address is not set to a fixed IP address, the LAN function will be limited.

 

 

FAQs about network neighbors

I can see it on a network neighbor sometimes, but not on a single machine sometimes?
A: Microsoft Network customers must log on to view their network neighbors. If you do not log on but choose to cancel it when starting the system, the network neighbors will not be able to see any other machine. You can click Start-> log out, log on again, and everything will work.

I can only see my own machine in my network neighbor?
A: Generally, your network card is not set, or the network cable is faulty.

My network neighbor can only see some machines, and cannot access OA or access the Internet?
A: Your machine Nic may be disabled. If you set your own IP address, you deserve it. You can only write an apology letter to the network administrator.

I have installed network components as required, but can't I access my network neighbors?
A: Consider the netbui protocol. Sometimes netbui may be installed falsely. Delete the netbui protocol, confirm to exit, and then reinstall the netbui protocol.

I can access other people's machines, but I cannot see myself on the network as a neighbor?
A: You may not have installed Microsoft files and printer sharing. Microsoft Network customers allow you to access others, Microsoft files and printer sharing allow others to access you.

Network neighbors still don't work?
A: protocols are mutual, just like a language. If it still doesn't work, consider the other party. Everything will work normally only if both parties have set up the correct agreement.

F: Why does the prompt "no permission" appear when the peer accesses the network?
Q: Open the Guest account (Win2k/XP) for both machines ).

F: Why cannot I connect to the target machine after I click the target machine?
Q: Make sure that the IP address and machine name of the ping peer can return information normally.

F: Why can't the peer's machine be seen or accessed by a network neighbor?
Q: According to Microsoft's explanation, this phenomenon is sometimes normal. You need to understand the working principle of the network neighbor and the NetBIOS protocol used. For details, refer to the principles section below.

F: some machines start or shut down, so other machines won't be able to use their network neighbors?
Q: Same as above ..

F: Is there any other way to access other machines without using a network neighbor?
Q: You can search for the IP address or machine name of the other party without turning on the network neighbor. You can also enter ///// // X in the running status. x. x. X (IP address of the other party) or xxxx (machine name of the other party ). (NetBIOS protocol is also used)

F: Can I use a network neighbor if two machines are not in a working group?
Q: Yes.

F: Can I see the two machines connected by routers in the network neighbors and access them?
Q: No, because the vro does not forward broadcasts (UDP passthrough is configured). You can use faq2.6. to access each other, but only Win2k/XP.

F: Why can't Win9x/me be accessed or Win2k/XP be invisible, but in turn there is no problem?
Q: Check that Win2k/XP has opened the Guest account and enabled "Browse service". Win9x/me has installed "printer and file sharing". NetBIOS resolution is correct, both parties have no firewall blocking.

F: Why do I need a password for access?
Q: confirm that the other party has opened the Guest account, or the other party has not logged on to the domain mode. If you need to log on to the Win9x/me domain, do not press ESC to cancel entering the system.