When using XP for the first time, you should create a new network connection in the properties of My Network Places in the Network Installation Wizard.
1, check the physical connection between computers.
Network card is the basic equipment for network connection. In a desktop computer, the indicator light behind each network card should be on, which means that the connection is normal. If not, please check whether the hub or switch is turned on and whether the indicator light of each client connection is on, indicating that the link is normal. Next, check whether the crystal head of the network cable is in good contact.
2. Make sure that TCP/IP is installed on all computers and works normally.
By default, TCP/IP is installed in Windows XP. However, if there is a network problem, it is not easy to uninstall and reinstall TCP/IP: click the Internet Protocol (TCP/IP) item in the following list of items for this connection displayed in the local connection properties, and you will find that the uninstall button is not available (disabled).
This is because the Transmission Control Protocol/Internet Protocol (TCP/IP) stack is the core component of Microsoft XP/ 2003 and cannot be deleted. In this case, if you need to reinstall TCP/IP to restore the TCP/IP stack to its original state. You can use the NetShell utility to reset the TCP/IP stack to its state when the operating system was first installed. The method is: type the following command at the command prompt, and then press enter: netsh int ip reset c:\Resetlog.txt, where the log file Resetlog.txt for recording the command results must be specified, and the log file Resetlog.txt and the full path must be specified here. Running this command has the same effect as removing and reinstalling the TCP/IP protocol.
3. Use the ping command to test the connection between two computers in the network:
Ping the IP address of another computer. At the command prompt, type ping x.x.x.x (where x.x.x is the IP address of another computer), and then press ENTER. You should see several replies from another computer, such as:
X.x.x.x reply: bytes = 32 time & lt 1 millisecond TTL= 128.
If you don't see these replies, or if you see "request timed out", there may be a problem with the local computer. If the ping command is executed successfully, you can be sure that the computer can be connected correctly and you can skip the next step. If you don't see these replies, or if you see "request timed out", there may be a problem with the local computer. PING local IP. If you see "Request Timeout", there may be a problem with the local computer.
4. Use the ping command to test whether the name resolution in the network is normal.
Ping computername, where computername is the name of the remote computer. Use the ping command to test the computer connection by name. The way to determine the computer name is to enter SYSTEMINFO at the command prompt. Or right-click My Computer-Properties on the desktop, and then click the Computer Name tab. If you see a successful reply to this command, you have the basic connection and name resolution between computers. Name resolution is closely related to NETBIOS. Please refer to the following steps.
5. Install network components correctly.
First, right-click on Online Neighborhood-Properties and select the network card you want to enjoy. Set IP on the same network segment of LAN. For example, 192. 168. 1. X network segment. Then check the advanced properties of TCP/IP to see if NETBIOS is turned on.
In the network system built by WINNT4.0, the unique identification information of each host is its NetBIOS name. The system uses WINS service, information broadcasting mode and Lmhost file to resolve NetBIOS names into corresponding IP addresses, thus realizing information communication.
In the internal network system (that is, what we usually call local area network), it is very convenient and fast to use NetBIOS name to realize information communication. However, the only identification information of a host on the Internet is its domain name in FQDN format (163.com). On the Internet, DNS standards are used to resolve domain names into corresponding IP addresses, WIN2K supports dynamic DNS, and machines running active directory services can dynamically update DNS tables.
WINS service is no longer needed in WIN2K network, but WIN2K still supports WINS because of backward compatibility. At present, most networks are mixed networks, including Win98, WINXP/WIN2K and other systems, so it is necessary to bind NETBIOS to TCP/IP protocol to resolve computer names.
Check whether the file and print service components are selected. If unchecked, the browsing service will not be bound to the NetBIOS interface. Windows-based computers that have become backup browsers and have not enabled File and Print Sharing * * * cannot share browse lists with clients * * *. Any computer that will be included in the browse list must also have file and print * * * enabled.
6. Enable printing and file sharing.
In the properties of My Network Places and Local Connection, you can see whether a printer is installed and whether files are shared. Verification: If you can't see your machine in your online neighborhood, it means that you don't have a printer and file sharing.
7. Start the "Computer Browser" service
The computer browser service maintains an updated list of computers on the network and provides the list to computers designated as browsers. If this service is stopped, the list will neither be updated nor maintained.
WIN2K/XP should ensure that the computer browsing service starts normally. Open Computer Management-> Services and Applications-> Services, and make sure that "Computer Browser" is not stopped or disabled in the window on the right.
8. Run the Network Identification Wizard.
Select "Properties" for my computer, and then click the "Computer Name" tab, click the "Network ID" button to start the "Network Identification Wizard": click "Next" and select "This computer is part of a commercial network and uses it to connect to other working computers"; Click "Next" and select "The company uses a domain-free network"; Click "Next" button, then enter the workgroup name of your local area network, click "Next" button again, and finally click "Finish" button to complete the setup.
9.Win2k installs NetBEUI protocol.
NetBEUI protocol is an efficient protocol in Win2k, so you must install:
My network places-> properties-> local connection-> properties-> installation-> protocol -> NetBEUI protocol.
10, activate the guest account.
Guest accounts in Windows XP allow others to use your computer, but they are not allowed to access specific files or install software. All network access to Windows XP Home Edition computers or Windows XP Professional computers in the workgroup uses the guest account. Use net user guest to ensure that the guest account is set up for network access. If the account is active, a line similar to the following will appear in the command output: Account active Yes；; If the account is not active, use the following command to grant the guest account network access:
Network User Guests/Activities: Yes
Or open the control panel->; User account or in administrative tools->; Computer management->; Open guest accounts in local users and groups.
1 1. Allow guest accounts to access from the network.
Enter gpedit.msc during operation, and the Group Policy Manager will pop up. In "Computer Configuration -Windows Settings-Local Policy-User Rights Assignment", there is a policy of "Deny access to this computer from the network" to prevent access to this computer from the network. If there is a GUEST account, the solution is to delete the GUEST account that is denied access.
12, firewall:
Make sure that the firewall attached to WINXP is not turned on, and turn on Local Connection Properties-> Advanced, and turn off the Internet connection firewall. If you use a third-party firewall product, please refer to its user manual to ensure that the firewall will not block the communication of 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 ICF and is more powerful. ICF has its own settings. After installing SP2, ICF firewall is enabled by default, and external active connections are not allowed. Even local applications need to be set in the permission list if they want to access the network.
However, the firewall blocks the normal network browsing service communication, and as a result, others can't see your computer in the online neighborhood. Is there a way to kill two birds with one stone and allow browsing services on the premise of opening the firewall?
The solution is, if ICF is open, open the property and select Add in the service column. The dialog box for adding service * * * has four edit boxes, the top one is to describe the service name for easy memory, and the second one from top to bottom is the IP address or name of the application service. Enter 127.0.0. 1 to indicate the machine.
Below are the internal and external port numbers, and the tcp/udp next to it indicates whether this port is a udp connection or a tcp connection.
Enter 3 services according to the table below.
Name protocol port
NetBIOS name service UDP 137
NetBIOS datagram service UDP 138
NetBIOS session service TCP 139
137/UDP-NetBIOS name server, Network Basic Input/Output System (NetBIOS) name server (NBNS) protocol is a part of NetBIOS (NetBT) protocol family over TCP/IP, which provides a method for mapping host names and addresses on the network based on NetBIOS name access.
138/UDP-NetBIOS datagram is a part of NetBIOS (NetBT) protocol family on TCP/IP, which is used for network login and browsing.
139/TCP-NetBIOS session service is a part of NetBIOS (NetBT) protocol family on TCP/IP, which is used for server message block (SMB) and file * * * sharing and printing.
13. Check whether RPC and plug-and-play services have been started, check the permissions of corresponding system folders, and re-register the following dynamic link libraries:
Registrar of netshell.dll 32
Registrar of netcfgx.dll 32
Registrar of netman.dll 32
14. Set the account and password.
Because of the operating system of WinNT kernel, it seems that when accessing a remote computer, it always tries to use the local current user name and password first, which may lead to inaccessible. Just add the user password here.
15, multiple ways to access "network computer"
For example, open a computer named Heizai in the network, and its IP address is192.168.1.8. If you don't know the IP address of another machine, you can use "PING computer name" to get its IP address.
Access the services provided by NETBIOS through the computer name. Click the Start menu, click Run, enter \ Black Boy \ in the address bar and click OK.
Use IP address to access, enter "2. 168. 1.8" in the address input box, and click OK.
It takes time to update the list by searching for computers, and searching for computers can speed up the update of the list. Right-click "Search Computer" in "My Online Neighborhood", enter the computer name, and click "Search Now" to see the computer you want to visit. Double-click the computer name on the right to open it.
Enter through the mapped drive, enter DOS mode, enter "NET VIEW \killer" and press enter? This is to see what * * * folders are on Blackboy's computer, such as D, and then type NET USE Z:\ Blackboy \D? Map the folder D shared by the computer IBM-ZB*** to an H: disk, and type "Z:" at the command prompt. You will find that you are connected to Blackboy's computer.
Common Online Neighborhood Access Problem Set
Basic conditions for window neighbors to exchange visits;
1) Both computers are turned on and network resources are set up;
2) The "Microsoft Network File and Print * * *" service has been added to both computers;
3) Both parties have correctly set the IP addresses in the network, and they must be in a network segment;
4) Both computers have turned off the firewall, or there is no policy in the firewall policy to prevent online neighbors from accessing.
User authentication of Windows 98/2000/XP/2003 accessing XP
First of all, why can't I access an enabled guest?
1. By default, XP disables guest accounts.
2. By default, XP's local security policy prohibits guest users from accessing the network.
3. By default, the local security policy of XP-- >; In the security option, "account: users with blank passwords can only log in to the console" is enabled, that is to say, any account with blank passwords can not be accessed from the network, and can only log in locally, and the default password for guests is blank. ......
Therefore, if you need to use the Guest user to access XP, you should make the above three settings: enable the Guest, modify the security policy to allow the Guest to access from the network, disable the security policy in 3 or add a password to the Guest.
Sometimes you will encounter another situation: when accessing XP, the user name in the login dialog box is gray, and it has always been a Guest user, so you can't access other user accounts.
The reason is that this security policy is at work (administrative tools->; Local security policy->; Security options-> "Network Access: Access and Security Mode of Local Accounts"). By default, XP's access mode is "Guest only", so if you visit, you can't enter other user accounts as a Guest.
Therefore, the easiest way to access XP is to change the above security policy to "classic" without enabling Guest. Other systems can enter their own account information when accessing XP.
As for access to 2003, by default, visitors are forbidden in 2003, but XP is not enjoyed, that is, the annoying default and contradictory visitor mode, where you can directly enter your user name and password to access.
A small office LAN, all of which are winxp systems, can access the external network and see the other party's computer, but not seeing the computer shared by the other party means that the network path is incorrect, or you don't have permission to use the network. That's probably what it means. I can't remember clearly! ! I also enabled the guest account! The firewall of winxp is also closed, and there is no problem with the ip address! ! I hope everyone will analyze it! ! Thank you very much.
Reason: There are security policy restrictions in Win2000/XP.
Sometimes, Win2000/XP is too smart. Although we have enabled the Guest account, we still can't access Win2000/XP from Win98. For example, if we use a firewall vulnerability patch like Rising, it will modify the policy of "denying network access to this computer", and the modification method is as follows:
Start-> Run-> gpedit . MSC-& gt； Computer configuration-> Windows settings-> Local policy-> User rights assignment-> Delete the guest user in "Deny access to this computer from the network".
Exchange visits between Win2000/XP and Win98
If both computers use Win2000/XP operating system, it is very easy to set up a local area network. When the hardware connection is completed, you can see each other in the "Online Neighborhood" immediately under normal circumstances. However, if the computers in the LAN use Win98, the situation is not necessarily the case. We often find that although the Ping command can be passed, it is still impossible for "online neighbors" to exchange visits. What should we do at this time?
Countermeasure 1: Enable the Guest user in Win2000/XP. After Win2000/XP system is installed, two user accounts will be established by default, namely Administrator (System Administrator) and Guest (Guest Account). By default, all users who are not assigned to the local computer account will use the guest account, and the account has no password. However, by default, this guest account is not enabled. We can find the "Guest" account in Control Panel | Administrative Tools | Computer Management | Local Users and Groups | Users, right-click to open the "Guest Properties" dialog box, and remove the check mark of the "Disable Account" check box here, so that we can access Win2000/XP from Win98 after exiting.
In fact, after the Guest account is enabled, the biggest advantage is that you don't need to enter a user name and password when accessing Win2000/XP from Win98. This method is more suitable for local area networks with uncertain users and large visits, but not suitable for home users.
-
Countermeasure 2: Check whether there are security policy restrictions in Win2000/XP. Sometimes, Win2000/XP is too smart. Although we have enabled the Guest account, we still can't access Win2000/XP from Win98. At this point, we should find "Access this computer from the network" or "Access this computer from the network is denied" from "Control Panel | Administrative Tools | Local Security Policy | Local Policy | User Rights Assignment", and then check whether it appears.
-
Countermeasure 3: Disable the firewall for local connection. Firewall is a kind of security system, which acts as the boundary between the network and the outside world. Microsoft provides users with a built-in Internet Connection Firewall (ICF) in WinXP, which can prevent some unsafe information from entering the intranet from the outside. However, if this firewall is enabled on the local connection, mutual access between workgroups will be prevented, and similar prompts will appear, such as "XXX cannot access", "You may not have permission to use network resources", "Please contact the administrator of this server to find out whether you have access permission" and "The network path cannot be found". Please disable firewall shielding for local connection at this time.
-
Countermeasure 4: add NetBEUI protocol to WinXP. In fact, it is sometimes easier to solve the problem of mutual access by directly adding NetBEUI protocol, and it can also solve the problem of enabling firewall mentioned above. NetBEUI protocol will be automatically installed when Win98 is installed, but it can only be added manually because WinXP no longer provides technical support for NetBEUI protocol.
Find out the installation CD of WinXP and enter the folder "ValueaddMsftNetNetbeui", which contains three files: Nbf.sys, Netbeui.txt, netnbf.inf * * *. Copy the Nbf.sys file to the "WindowsSystem32Drivers" folder of this computer (here, this computer refers to the computer with WinXP installed), and then copy the Netnbf.inf file to the "WindowsINF" folder of this computer. The Netbeui.txt file is optional. However, the INF folder has hidden properties, and users need to select "Show File" in the "Tools | Properties" window under WinXP to see the directory.
-
Countermeasure 5: Enable File and Printer Sharing in Win98. This is a very simple but often overlooked problem, that is, a machine with Win2000/XP can find a machine with Win98 from "My Network Neighborhood", but because Win98 has not enabled "Allow other users to access my files", it cannot be accessed. Enabling this option can solve this problem.
Of course, in addition to the reasons mentioned above, there are two computers that are not in the same workgroup, or the IP addresses of the two computers conflict, even including hub failure and line failure.
Microsoft knowledge base article, Microsoft knowledge base article -3 18030.
You can't access * * * shared files and folders, and you can't browse computers in your workgroup.
; 3 18030
Problem: When the client's online neighbors access the server, "Server has no transaction set" appears, so they cannot access the server's * * * resources. The same is true for directly entering the IP address.
Possible situation: IPC$ is not turned on or caused by a virus.
Solution:
Method 1: run the Net Share IPC$ command, or directly add the Net Share IPC$ to the registry running startup item.
Method 2: There is a WUAMGRE.EXE file under %Systemroot%SYSTEM32, and delete it.
Method 3: Install a Trojan buster to kill the virus.
Solve the problem of slow exchange of visits between neighbors on Win2000 and WinXP.
At present, many people are using Win2000 and WinXP to connect to the Internet, but in practice, many netizens report that browsing online neighbors in Win2000 and WinXP is very slow, especially when there are Win9x and WinMe workstations in the network. Sometimes it takes more than 10 minutes to open the online neighborhood, and errors are often reported. So what is the reason for the slow network speed? According to the author, there are two main reasons.
Network protocol configuration problem,
The problem of WinXP planning tasks.
However, if other Windows computers don't see WinXP at all in their online neighborhood, it may be that the user lock and security policy are set incorrectly. At this time, we need to start from the following aspects. I have encountered similar problems before, but I have summed up a set of effective solutions in a large number of networking experiments, and I will teach you now.
I. Installation and setting of network protocols
1. Install NetBEUI protocol in WinXP.
Yes, you are right, that is, installing NetBEUI protocol in WinXP. Microsoft only supports TCP/IP protocol and NWLink IPX/SPX/NetBIOS compatible protocol in WinXP, and officially announced that it no longer supports NetBEUI protocol. However, in the practical use of establishing a small LAN, it is not satisfactory to use two protocols supported by Microsoft. For example, in the process of solving the problem of slow online neighbors, the author adopts many methods. The speed of online neighbors is better, but it is still as slow as a snail; In addition, when setting the protocol, client and service binding of multiple network cards, there are still bugs in these two protocols. Multiple network cards must bind all protocols (except NWLink NetBIOS), clients and services at the same time. Even if you cancel some binding and restart, the system will automatically add them, which obviously cannot meet the actual needs in network construction. When the author installed NetBEUI protocol in WinXP, the above two problems were solved satisfactorily.
There are three files in the "\valueADD\MSFT\NET\NETBEUI" directory of the WinXP installation CD, among which "NETBEUI". TXT "is the installation instructions, and the other two are the files needed to install Netbeui protocol. The specific steps of installation are as follows:
Copy "NBF. SYS' is copied to the' %SYSTEMROOT%\SYSTEM32\DRIVERS' directory;
Copy "NETNBF. To the "%SYSTEMROOT%\INF" directory;
Click the "Install" button in the network connection properties to install NetBEUI protocol (Figure 1).
Note: %SYSTEMROOT% is the installation directory of WinXP. For example, if my WinXP is installed in the F:\Windows directory, you should replace %SYSTEMROOT% with F:\Windows.
2. Set other network protocols in WinXP.
I suggest that if your LAN doesn't use the Internet, you just need to install NetBEUI protocol. NetBEUI is the fastest protocol in a small LAN (a network with about 200 computers) and occupies the least memory. The compatible protocols of NWLink IPX/SPX/NetBIOS should be deleted.
If your local area network wants to access the Internet, you must install TCP/IP protocol. However, in order to access the network quickly, it is recommended to specify the IP address of each workstation (unless there is a DHCP server in the network), otherwise the workstation will always look for a DHCP server to slow down the network speed.
Of course, if only TCP/IP protocol is installed in the network, mutual access in the local area network can be realized. However, it is difficult to see other machines directly in the online neighborhood, and it is very inconvenient in many practical network applications to search for a machine to access it.
3. Settings of other Windows computer network protocols
Careful users may have found that there is a wizard of "setting up home or small office network" in WinXP's online neighborhood, which can be used to set up local area network, Internet connection and small local area network conveniently. The wizard also provides network installation floppy disks for other Windows computers connected to WinXP.
However, the author does not advocate using this network to install floppy disks. On other Windows computers connected with WinXP, you only need to install NetBEUI protocol and set the network logo. To connect to the Internet, you only need to install the TCP/IP protocol and specify the IP address. This is exactly the same as the traditional LAN setting, so it is recommended to use IPX/SPX compatible protocols less (Figure 2).
Second, completely disable the scheduled tasks of WinXP.
When browsing online neighbors in WinXP and Win2000, the system will be delayed for 30 seconds by default, and Windows will use this time to search whether the remote computer has a specified scheduled task (even online search). If the network doesn't respond when searching, it will fall into infinite waiting, so it is not surprising that there is a delay or even an error exceeding 10 minutes. Here are the specific solutions.
1. Close the task scheduler of WinXP.
You can open the properties dialog box of the task scheduler in the control panel/administrative tools/services, click the stop button to stop the service, and then set the startup type to manual, so that the service will not be started automatically next time (Figure 3).
2. Delete two subkeys in the registry.
Look up the primary key'' in the registry.
HKEY _ LOCAL _ MACHINE \ SOFTWARE \ Microsoft \ Windows \ current version \ Explorer \ remote computer \ NameSpace "
Delete the following two subitems.
Among them, the first subkey determines whether online neighbors should search for printers on the Internet (even on the Internet). If there is no printer on the network, you can delete this key. The second sub-health determines whether it is necessary to find the designated planned task, which is the chief culprit of the slow neighbors of online games, and this sub-health must be deleted.
Third, solve the problem that other Windows computers can't access WinXP computers.
After installing the network, some netizens found that computers with Win9x or WinMe operating systems could not access WinXP computers, and even could not see each other among online neighbors. If you have this kind of trouble, you can check the following.
1. Check whether the guest user is enabled.
By default, the Guest user in Win2000 and WinXP is disabled. To enable guest users, you can go to Control Panel/Administrative Tools/Computer Management/Local Users and Groups/Users, and delete the small checkmark before "Account Disabled" (Figure 4). This user had better not set a password, and check "User can't change password" and "Password never expires" to facilitate user access and reduce the possibility of trouble. However, the premise is that the permissions and groups of guest users must be set well, otherwise it will be endless trouble.
2. Check whether guest users are denied access to this computer from the network.
In WinXP, guest users are denied access to this computer from the network by default. You can go to Control Panel/Administrative Tools/Local Security Policy/Local Policy/User Rights Assignment/Deny Access to this Computer from the Network and delete it if it includes guest users (Figure 5). If it is a Win2000 server or a WinXP.net server with a domain, you must also delete the Guest user in the project corresponding to the Domain Security Policy. It should be noted that it will take several minutes to take effect after deletion.
3. Set the password of the guest user
If the guest user has a password, other Windows workstations will be prompted to enter the password when accessing the WinXP computer. At this time, you can also enter the WinXP computer by entering the password of the Guest user. When entering a password, you can select the following item "Please save the password in the password list", and you will not be prompted to enter the password next time (unless the password of the user has been changed, Figure 6). Of course, if it has been set as a login domain on a Windows workstation and a domain user logs in the domain, it will not be affected by the password of the Guest user.
Understand and solve the common problems of online neighbors
1. Online neighbors are unstable and often inaccessible.
Reason: Due to the fragility of the system, the computer playing the role of the main browser is likely to crash, or there will be illegal operations, which will make it impossible for the client to obtain the computer list from the main browser and make it inaccessible to online neighbors.
Solution: Designate a trusted computer as the main browser, or let the main browser be served by some designated computers.
Method 1: Set up a machine with Win2000 Server system in the workgroup without installing a domain controller (this can reduce the hardware requirements for the machine). Name the computer server 1, and the computer browser service in "Services" must be "automatically started" (Figure 1). Stop the computer browser in the Services of computers with other Win2000 systems in the workgroup, and change the startup type to Manual or Disabled. This ensures that the main browser is always served by server 1 (unless the computer is turned off). How to confirm that the main browser has been used by the computer you set up? This paper introduces the tool software browstat.exe under Win2000. This software can be obtained from the SUPPORT\TOOLS compressed package support.cab in the root directory of Win2000 installation CD. Run browstat dn directly at the command prompt of Win2000 to show how many protocols are bound to the current browser.
Then use the command browstat gm 1 workgroup to see which computer is the main browser in the workgroup, and find that the main browser is the computer LIN in the workgroup.
When browstat gb 1 is run, the workgroup can view the name of the computer that acts as the backup browser. Run browstat wfw workgroup to view the computers in the workgroup that have started the computer browsing service, that is, the computers that may become the main browsers.
Browstat.exe can not only finish the viewing work, but also force the main browser in the workgroup to re-elect. You can enter browstat directly at the command prompt to view help information.
Method 2: If there are no Win2000 computers in the workgroup, only a few trusted Win98 computers can be designated as the main browsers. The network card driver is installed in Win98 system by default. After "Allow files and printers to enjoy * * *" is enabled, every computer may become the main browser, so most computer browsing services in Win98 system must be stopped. You can set the value of "Browse Home Server" under "My Network Places → Properties → Files and Printers on →Microsoft Network * * *" to be disabled (default is automatic,).