TITLE
    Mac OS X Server: Troubleshooting Apple File Services Remote Administration
Article ID:
Created:
Modified: 		60066
3/4/99
7/11/00
TOPIC

    This article describes how to troubleshoot Apple File Services Remote Administration under Mac OS X Server.

DISCUSSION

    If you don't know the host name of the Web server:

    On the server computer, open the Apple menu and choose Computer Settings, then choose Network. In the Network settings panel, click the Services tab. The server name should be listed here. You can also log into the server using its numeric IP address.

    If Remote Administration does not recognize the user name and password you enter:

    Be sure you have entered the user name and password for a user with administrator (root) privileges. If the user name and password continue to fail, you can log in by typing "Administrator" and the password for the Administrator user (root) of the server computer. Passwords are case sensitive.

    If you're unable to connect to or log in to Remote Administration:

    Make sure your computer is connected to the network properly. Try logging in to Remote Administration using the TCP/IP address for the server.

    If you are able to log in using the TCP/IP address, then you may have entered the URL incorrectly. The URL should be similar to this:

    http://server.domain.com:311

    The "server.domain.com" is the host name of the Web server plus the domain of the organization.

    If you are logging in to Remote Administration from the Internet, be sure the name is the Internet DNS name for your Web server and not the local domain name.

    If you are logging in to Remote Administration from the Internet, be sure the DNS server is available, or use the IP address.

    If you receive a "504" or proxy time-out error message, ask your proxy server administrator to allow write access for the Web server on port 311.

    If this is not possible, turn off any proxies set up in your web browser and select the option to connect directly to the Internet. Then, try again.

    You can also make sure Apple file services is turned on and connected to the network:
      1. Make sure you can reach the other computer over the network (try pinging the other computer)
      2. Log in to your server computer as Administrator.
      3. Open the Apple menu and choose Server Administration, then choose Assistant.
      4. In the panel, select Setup Assistant and follow the onscreen instructions to turn on Apple file services.
      5. Restart the server computer.

    If you have other network services running on the server computer, you may want to notify users first.

    If you're sure Apple file services is turned on but you are unable to log in to Remote Administration:

    Two different processes are required for Remote Administration to work: RemoteAdminServer and AdminWebServer. To find RemoteAdminServer, open the ProcessViewer (located in "Server Administration" under the Apple Menu). You should see RemoteAdminServer listed in the Process Listing.

    The AdminWebServer shows up as "apache" in the ProcessViewer, but not all processes named "apache" function as the AdminWebServer. To make sure that the correct apache processes are running, follow these steps:

      1. Click the triangle at the bottom of the ProcessViewer to view More Info.
      2. Click the "Path & Arguments" tab in that section.
      3. Type 'apache' (without quotes) in the Find box at the top of the window. This should display only those processes whose name contains "apache".
      4. Three of the listed processes should have "/usr/libexec/AdminWebServer" in the "Full Path" section of the "Path and Arguments" tab.

    Alternatively, you can type the following into the command line (Terminal.app):

    ps aux | grep Web

    This gives you a long display of all the processes running on the server whose name contains "Web". Look for /usr/libexec/AdminWebServer.

    There should be three instances (copies) of this.

    If you are unable to find either AdminWebServer or RemoteAdminServer, try restarting Apple File Services using the Setup Assistant

    If they both appear in the list, you can use ProcessViewer to stop the processes, then restart Apple File Services using the Setup Assistant.

    If users say the server is slow:
    • Make sure it's not a network-wide issue. Log onto another server to test performance
    • Have Admin check histogram in Remote Admin to see what user level is at versus connected user activity for possible culprits.

Document Information
Product Area: Mac OS System Software
Category: Mac OS X Server
Sub Category: Apple File Services; Troubleshooting

Copyright © 2000 Apple Computer, Inc. All rights reserved.