• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL

Lesson 9. Accessing Network Services > Troubleshooting Network Services

Troubleshooting Network Services

When troubleshooting network service problems, try the following strategies:

  • If you are unable to locate other services, such as printers or file servers, on the network:

    1. Verify that Network preferences are correctly configured.

    2. Make sure that you have a working network connection.

    3. Use the network troubleshooting techniques covered in Lesson 8, “Networking Configuration and Troubleshooting,” to verify that you have network connectivity from the computer to the server.

  • Examine the log files located in /Library/Logs/DirectoryService. The two log files, DirectoryService.error.log and DirectoryService.server.log, will list which plug-ins loaded successfully and which ones failed.

  • If you are able to browse AFP file services, but cannot connect, make sure TCP/IP is enabled on the primary network interface. AppleTalk is not supported for AFP networking in Mac OS X 10.4.

  • If you are unable to browse for a Windows server, remember that you can only browse SMB servers that are on the same subnet. To connect to SMB servers outside the subnet, you need to provide the address of the server. Also, if an SMB server just started, it can take 10 minutes or more for it to be located on the network.


    Refer to Microsoft's Knowledge Base document 188001, “Description of the Microsoft Computer Browser Service” (http://support.microsoft.com).

  • When using the Finder's Connect to Server command to browse for SMB servers on a network where DNS provides reverse-lookups, the domain name will be displayed instead of the computer name.


    Refer to Knowledge Base document 107085, “Mac OS X 10.2: Expected, User-Defined Windows (SMB) Computer Name Does Not Appear in Connect to Server Dialog.”

  • When Connect to Server cannot connect to a server, a dialog may appear with an error code and no explanation (viewing logs with Console may provide more helpful information). Common error codes include:

    –36 Error in URL

    –43 Error in URL, probably the volume name

    –47 Already connected to this server as the same user

    –5000 Access denied

    –5019 Volume does not exist

    –5023 Bad password



Not a subscriber?

Start A Free Trial

  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint