What problem are you having?
Cause: Through Automatic Private IP Addressing (APIPA), an IP address in the range 169.254.0.1 to 169.254.255.254 with a subnet mask of 255.255.0.0 is automatically assigned when TCP/IP is configured to obtain an IP address automatically, a Dynamic Host Configuration Protocol (DHCP) server is not available, and an alternate configuration is not specified. APIPA is designed to provide automatic IP addressing on single segment networks. Solution: Disable automatic address configuration, determine and fix the cause of the computer's inability to contact the DHCP server, or specify an alternate configuration. See also: New features; To configure TCP/IP for an alternate configuration; To disable automatic address configuration |
Host name resolution is failing. Cause: Host name resolution techniques are failing to resolve a host name to its IP address. Solution: The When you use TCP/IP tools such as the ping command, the Hosts file or a DNS server is used for name resolution. You can find the Hosts file in the IP address Friendly name
When you use a Hosts file for name resolution, the following steps occur:
The following problems can occur because of errors related to the Hosts file:
For DNS server host name resolution, verify that the correct DNS servers are configured and in the proper order. You can use the ipconfig If you use a DNS server for host name resolution, the name resolution steps are similar. Computer A sends a DNS name query to its configured DNS server. The DNS server resolves the host name of Computer B to an IP address and sends the results back to Computer A. See also: Host name resolution; Viewing configuration by using ipconfig /all; Ping; Nslookup; To verify DNS registration for domain controllers using the nslookup command; TCP/IP database files |
Unable to add a default gateway. Cause: The IP address of the default gateway is not on the same IP network ID as your IP address. Solution: Find out whether the default gateway is located on the same logical network as the network adapter of the computer by comparing the IP address of the default gateway with the network IDs of any of the network adapters of the computer. For example, a computer with a single network adapter that is configured with an IP address of 192.168.0.33 and a subnet mask of 255.255.0.0 requires that the default gateway be of the form 192.168.y.z because the network ID portion of the IP interface is 192.168.0.0. See also: IP addressing; Subnet masks; Default gateways |
Cause: System error 53 is returned if name resolution fails for a particular computer name when the net use command is used. Solution: If the computer is on the local subnet, confirm that the name is spelled correctly and that the target computer is running See also: To test a TCP/IP configuration by using the ping command; To test TCP/IP connections by using the ping and net view commands; Net use; Ping |
Cannot connect to a specific server. Cause: Either NetBIOS name resolution is failing to resolve the name or the wrong IP address is being resolved. Solution: Use the nbtstat If the name being used by a remote computer is the same as the name displayed by the nbtstat See also: NetBIOS name resolution; To test TCP/IP connections by using the ping and net view commands; Net use; TCP/IP database files; Nbtstat |
Long connect times when using Lmhosts for name resolution. Cause: The Lmhosts file is parsed sequentially to locate entries without the #PRE option. Solution: Place frequently used entries near the top of the file and place the #PRE entries near the bottom. If an entry is added to the end of a large Lmhosts file, mark the entry in Lmhosts as a preloaded entry by using the #PRE option. Then use the nbtstat See also: TCP/IP database files; Nbtstat; To view the NetBIOS name table by using the nbtstat command; To release and refresh NetBIOS names by using the nbtstat command |
TCP/IP connection to a host appears to have stopped. Cause: Either data is blocked in TCP and UDP queues or there are network or user-level software delay problems. Solution: Use the netstat The state of a good TCP connection is usually established with 0 bytes in the send and receive queues. If data is blocked in either queue, or if the state is irregular, there is probably a problem with the connection. If not, you are probably experiencing a network or user-level software delay. See also: Netstat; To view current TCP/IP protocol and connection statistics |
Cannot ping across a local router when using a dial-up connection. Cause: This problem occurs if the Use default gateway on remote network check box is selected on the General tab in the Advanced This feature adds a default route to the IP routing table that is used instead of the current default route for the duration of the connection. The new default route causes network traffic for IP addresses that are not resolved by other entries in the routing table to be sent across the dial-up connection. This new default route is needed when you dial an Internet service provider (ISP) and use Internet utilities, such as a Web browser or FTP, to access Internet resources. Solution: If you want to ping or otherwise connect to computers in a remote network segment across a local router while you are connected as a dial-up client to an ISP, then use the route add command to add the route of the network segment you are attempting to reach by specifying the destination network and subnet mask of the remote network segment and the IP address of the local router. See also: Route |
A "The registry subkey already exists" message is displayed. Cause: The registry keys for a component being installed already exist. Solution: Ensure that all the components of a given Caution
TCP/IP registry keysIf you removed TCP/IP and its related service components, you must also remove the following registry subkeys:
SNMP service registry keysIf you removed the SNMP service components, you must also remove the following registry subkeys:
TCP/IP Printing service registry keysIf you removed the TCP/IP Printing service components, you must also remove the following registry subkeys:
Simple TCP/IP Services registry keys
If you removed the Simple
DHCP service registry keysIf you removed the DHCP service components, you must also remove the following registry subkeys:
WINS service registry keysIf you removed the WINS service components, you must also remove the following registry subkeys:
DNS service registry keysIf you removed the DNS service components, you must also remove the following registry subkeys:
|
For more advanced TCP/IP troubleshooting information, see Resource Kit.