Use ping and net view commands to test TCP/IP connection
1. To use the Ping command to test the connectivity of TCP/IP, use the ipconfig command to make sure that the network adapter is not in the "Media disconnected" status. For more information, see "NOTE ".
2. Open a command prompt and use the IP address to ping the host.
If the ping command fails and the "Request timed out" message is displayed, verify that the Host IP address is correct, whether the host is running, and all the gateway routers between the computer and the host) whether it is running.
3. To use the ping command to test the host name resolution function, use the host name to ping the required host.
If the ping command fails, the message "Unable to resolve target system name" appears. Verify that the host name is correct and that the host name can be resolved by the DNS server.
4. Run the net view command to test the TCP/IP connection. Open a command prompt and enter net view \ ComputerName. . Net view command to list file and printer sharing by creating a temporary connection. If There is no file or print share on the specified computer, the net view command displays the message "There are no entries in the list.
If the net view command fails, the message "system error 53" is displayed. Verify that ComputerName is correct and that the computer in use is running, and whether all the gateway routers between the computer and the computer in use are running.
If the net view command fails, "system error 5 occurs. Access denied ." Message. Verify that you have the permission to view the shared account on the remote computer to log on to the computer.
To further resolve the connectivity problem, perform the following operations:
Ping ComputerName using the ping command.
If the ping command fails and the message "Unable to resolve target system name" appears, ComputerName cannot be resolved to an IP address.
Use the net view command and the IP address of the computer, as shown below:
Net view \ IPAddress
If the net view command is successful, ComputerName is resolved to an incorrect IP address.
If the net view command fails and the message "system error 53" is displayed, the remote computer may not share files and printers running Microsoft network services.
Note:
The ipconfig command is equivalent to the command line command of the winipcfg command and is available in Windows 95, Windows 98, and Windows Millennium Edition. A computer running Windows XP or Windows Server 2003 does not include a graphical tool equivalent to the winipcfg command. However, by opening a network connection, right-click a network connection, and click "status ", click the "support" tab to view and update the same IP address.
If the ipconfig command displays "Media disconnected", this indicates that the network cable is not inserted into the network adapter.
If the ipconfig command only generates the Windows IP Configuration message and then returns to the command prompt, check whether the network adapter is disabled. For more information, see "Create local connection" in "related topics ".
If the ping command cannot be found or the command execution fails, you can use Event Viewer to check system logs and find the problems reported by the installer or Internet Protocol (TCP/IP) service.
The ping command uses the Internet to control the Message Protocol (ICMP) echo request and echo response message. Packet filtering policies on routers, firewalls, or other types of security gateways may block the forwarding of this communication.
The process of using the net view command to test the TCP/IP connection is assumed that you only use the TCP/IP protocol group. If other protocols, such as NWLink IPX, SPX, and NetBIOS, are installed, the net view may work normally when a name resolution or TCP/IP creation failure occurs, because net view tries to use connections with all installed protocols. Net view may be successfully connected to NWLink IPX/SPX/NetBIOS compatible transfer protocol even if the TCP/IP connection attempt fails.
IPX/SPX is not supported in Windows XP 64-bit Edition (Itanium) and 64-bit Windows Server 2003 families.
Original article address
View more articles