An error message indicates that ShareWay IP cannot run after the Start button is hit.

• A duplicate serial number was discovered on the network. You need to either find and stop the copy of ShareWay IP with the duplicate serial number, or obtain an additional serial number from Open Door Networks.

On a client Macintosh, when I select AppleShare in the Chooser, there is no "Server IP Address..." button.

• The "Server IP Address..." button will only appear if you are running AppleShare Client 3.7 or later.

On a client machine, I enter the IP address of ShareWay IP, but I get an error.

• Verify that there is TCP/IP connectivity between the client and ShareWay IP machines. Try pinging ShareWay IP from the client using a ping program.
• If there is a firewall between the client and ShareWay IP, or if DoorStop is running on the ShareWay machine, verify that it has made port 548 accessible.
• Verify that ShareWay IP is running and active.
• Make sure the client is connecting to the right port number, as indicated in the TCP Port Number dialog.

After ShareWay IP is started, the status window shows "IP Address: <not available>".

• The ShareWay IP machine's IP address is not available. Use the ShareWay IP machine's TCP/IP control panel to give that machine an IP Address.
• If TCP/IP is configured to use DHCP or MacIP, ShareWay IP may be obtaining the IP address dynamically from the DHCP or MacIP server. The status will update to show the IP address when it's obtained.
• If you are using PPP, ShareWay IP will only have a usable IP address if the PPP connection has been established.

When I try to connect to ShareWay, I get the message, "This file server will not allow any additional users to log on. Try again later."

• There may be too many users trying to connect to ShareWay IP. ShareWay IP Standard supports a maximum of 20 simultaneous users. If you need to support more, you should use ShareWay IP Professional Edition.
• There may be too many users trying to connect to the target server. For instance, personal file sharing only supports a maximum of 10 simultaneous users.

When I try to start ShareWay IP I get an error message that its port is already in use.

• You may be running more than one copy of ShareWay on the same machine, which is not supported.
• Some other service on the machine is using the port for which ShareWay IP has been configured. Either stop that service or change ShareWay's port number.

When I try to start ShareWay IP I get an error message that another copy of ShareWay IP is already running on the same machine.

• If you are running ShareWay under Mac OS 9, be sure that File Sharing over TCP/IP is disabled in the File Sharing Control Panel (see Using ShareWay IP Standard under Mac OS 9)
• Perhaps the background version of ShareWay IP is already running.

ShareWay IP displays an incorrect host name, or just an IP address, in the AFP URL field.

• There is no host (DNS) name assigned to the ShareWay IP machine.
• When a host name was assigned to the ShareWay IP machine, a "reverse DNS lookup" or "PTR" record was not assigned, or was assigned incorrectly. Contact your network administrator if you wish ShareWay IP to display the correct host name in the AFP URL.

When I enter my serial number to convert my eval copy to a full working copy, ShareWay says it's a duplicate serial number.

• Someone else on your network has already used the serial number you are attempting to use. Each copy of ShareWay IP on a given network must have a unique serial number.

When I enter my serial number to convert my eval copy to a full working copy, ShareWay says the serial number is invalid.

• ShareWay IP 3.0 will not accept serial numbers from previous versions. Be sure you are using the ShareWay IP 3.0 serial number you were supplied with.
• ShareWay IP Standard will not accept ShareWay IP Personal or Professional serial numbers.

I moved my full working copy of ShareWay IP to another machine.

OR

I reinstalled my System software, and it's now behaving like an eval copy again.

The ShareWay machine is not visible in AFP Engage!'s "Browse AFP Servers" window (or in Mac OS 9's Network Browser ot Navigation Services).

• Be sure that the ShareWay IP machine is running Mac OS 8.5 or later
• Be sure the SLP plug-in is enabled through the extensions manager
• Be sure you are running ShareWay IP 2.0 or later
• Double-check the name of the server in the File Sharing control panel on the server machine
• Consult the AFP Engage! User's Guide for limitations with SLP
• Be sure both the client and the server are running the same version of the SLP plug-in (either 1.0.1 or 1.1).
• If the ShareWay machine has an entry in the "Search domains" field of the TCP/IP Control Panel, it will not show up in AFP Engage!. The ShareWay machine will, however, show up in the OS 9 Network Browser and Navigation Services, under a neighborhood named with the value entered in the "Search domains" field.

I am not sure if the background version of ShareWay IP is running on a particular machine.

• Run the foreground version of ShareWay IP on that machine. If the background version is running, the foreground version will indicate that fact.

I get an error saying that logging could not be enabled.

• Check to make sure that another application does not have the log file open, and that your disk is not full.

A user logs on to a ShareWay server, but does nothing and logs off some time later. The total bytes transferred for that user, as shown in the log file, seem much too high.

• The BYTES_SENT field in the log file includes all bytes sent over a session, not just bytes read from or written to files. Bytes sent as part of AFP's periodic housekeeping functions are also included.

Online help isn't available through the Macintosh Help Center.

• The folder "ShareWay IP Help" must be in the System's Help folder.
• The ShareWay machine must be running OS 8.5 or later.

Online help isn't available, or doesn't work correctly, through ShareWay IP's Help menu.

• The folder "ShareWay IP Help" must be in the System's Help folder.
• The file "ShareWay IP Guide" must remain in the same folder as the ShareWay application.
• The ShareWay machine must be running OS 8.6 or later.

A user who has been configured into the target server cannot log in over IP.

• Be sure the user is not being excluded through ShareWay IP's security.

A user who has been configured for IP access through ShareWay IP's security cannot log in

• The user must also be configured through the target server's security features.

Guests cannot log in over IP.

• Be sure guest access is enabled through both ShareWay IP's security and the target server.

Back to Table of Contents
Back to How ShareWay IP Works