Test TCP/IP connections by using the ping and net view commands
Updated: January 21, 2005
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
To test TCP/IP connections by using the ping and net view commands
To test TCP/IP connectivity by using the Ping command, use the display of the ipconfig command to ensure that your network adapter is not in a Media disconnected state. For more information, see Notes.
Open Command Prompt, and then ping the desired host using its IP address.
If the ping command fails with a "Request timed out" message, verify that the host IP address is correct, that the host is operational, and that all of the gateways (routers) between this computer and the host are operational.
To test host name resolution by using the ping command, ping the desired host using its host name.
If the ping command fails with an "Unable to resolve target system name" message, verify that the host name is correct and that the host name can be resolved by your DNS server.
To test TCP/IP connectivity by using the net view command, open Command Prompt, and then type net view \\ComputerName. The net view command lists the file and print shares by establishing a temporary connection. If there are no file or print shares on the specified computer, the net view command displays a "There are no entries in the list" message.
If the net view command fails with a "System error 53 has occurred" message, verify that ComputerName is correct, that the computer is operational, and that all of the gateways (routers) between this computer and the computer are operational.
If the net view command fails with a "System error 5 has occurred. Access is denied." message, verify that you are logged on using an account that has permission to view the shares on the remote computer.
To further troubleshoot this connectivity problem, do the following:
Use the ping command to ping ComputerName.
If the ping command fails with an "Unable to resolve target system name" message, then ComputerName cannot be resolved to its IP address.
Use the net view command and the IP address of the computer, as follows:
net view \\IPAddress
If the net view command succeeds, then ComputerName is being resolved to the wrong IP address.
If the net view command fails with a "System error 53 has occurred" message, the remote computer might not be running the File and Printer Sharing for Microsoft Networks service.
- Use the ping command to ping ComputerName.
To open a command prompt, click Start, point to All programs, point to Accessories, and then click Command prompt.
The ipconfig command is the command-line equivalent to the winipcfg command, which is available in Windows 95, Windows 98, and Windows Millennium Edition. Computers running Windows XP or a Windows Server 2003 operating system do not include a graphical equivalent of the winipcfg command, however, you can get equivalent functionality for viewing and renewing an IP address by opening Network Connections, right-clicking a network connection, clicking Status, and then clicking the Support tab.
If the ipconfig command displays Media disconnected, the network cable is not plugged in to the network adapter.
If the ipconfig command only yields the message Windows IP Configuration, and then returns you to the command prompt, you should check to see if your network adapter has been disabled. For more information, see To make a local area connection in Related Topics
If the ping command is not found or the command fails, you can use Event Viewer to check the system log and look for problems reported by Setup or the Internet Protocol (TCP/IP) service.
The ping command uses Internet Control Message Protocol (ICMP) Echo Request and Echo Reply messages. Packet filtering policies on routers, firewalls, or other types of security gateways might prevent the forwarding of this traffic.
The procedure for testing TCP/IP connections using the net view command assumes that you are using only the TCP/IP protocol suite. If additional protocols are installed, such as the NWLink IPX/SPX/NetBIOS Compatible Transport Protocol, net view might work correctly when there are problems resolving names and making connections with TCP/IP because net view attempts a connection using all installed protocols. Even if the net view connection with TCP/IP fails, net view might successfully connect to the NWLink IPX/SPX/NetBIOS Compatible Transport Protocol.
The IPX/SPX protocol is not available on Windows XP 64-bit Edition (Itanium) and the 64-bit versions of the Windows Server 2003 family.
Information about functional differences
Your server might function differently based on the version and edition of the operating system that is installed, your account permissions, and your menu settings. For more information, see Viewing Help on the Web.