Contents Index Previous Chapter Next Chapter


Troubleshooting and Error Messages

This chapter tells how to troubleshoot an Internet Protocol (IP) network. It also lists and explains error messages. Consult with your network administrator for further information.

To Top Troubleshooting an IP Network

Follow these guidelines while troubleshooting an IP network:

To troubleshoot an IP network

Note   If you are unable to resolve a problem, you may need to use an IP analyzer (such as Microsoft Network Monitor) to view network activity at each layer.

The first goal in troubleshooting is to make sure you can successfully ping an IP address. Ping a host with its host name only after you can successfully ping the host with its IP address.

To troubleshoot the network interface and internet layers by using the Ping command

After you can successfully ping the IP address, ping the host name to verify that the name is configured correctly in the HOSTS file.

Verifying TCP/IP Session Communications

The next goal in troubleshooting is to successfully establish a session. Use one of the following methods to verify communications between the network interface layer and the application layer.

To establish a session with a Windows NT–based computer or other RFC-compliant NetBIOS-based host, make a connect with the Net use or Net view command. If this step is unsuccessful:

To establish a session with a non-RFC-compliant NetBIOS-based host, use the Telnet or FTP utility to make a connection. If this step is unsuccessful:

To Top Error Messages

A home directory already exists for this service. Creating a new home directory will cause the existing directory to no longer be a home directory. An alias will be created for the existing home directory.

Invalid Server Name

More than 1 home directory was found. An automatic alias will be generated instead.

No administerable services found.

The alias you have given is invalid for a non-home directory.

The connection attempt failed because there’s a version conflict between the server and client software.

The service configuration DLL ‘filename’ failed to load correctly.

Unable to connect to target machine.

Unable to create directory.

Contents Index Previous Chapter To Top Next Chapter

© 1996 by Microsoft Corporation. All rights reserved.