 |
| |
|
Problems with network connections
If you cannot connect to a server over a network, check whether:
• your settings file is incorrectly configured
For example, the server domain name is wrong.
• the appropriate .fcp file is missing from FirstClass's FCP folder
• the server is not running
• all sessions on the server are in use
The server is set up to handle a limited number of simultaneous connections. Try again later.
• your network interface card (NIC) is configured incorrectly, or it or the cable is defective.
For information on configuring your NIC, see the documentation provided with it.
Problems with modem connections
To test your modem configuration, connect to another modem using a terminal emulation package (for example, Windows Terminal for Windows systems). For more information, see your modem documentation.
Certain problems are reported by FirstClass. In this case, they have a FirstClass error number. Make of note of this number in case you need to contact your administrator.
No response from the server's modem
You may get this error because:
• the modem at the other end is not connected to a FirstClass system
Make sure you are specifying the correct modem phone number, with any necessary dialing prefixes, in your service setup information.
• your modem is incompatible with the server's modem
This is especially common for modems that offer high speeds or advanced protocols. Try lowering the baud rate in your connection information.
• a poor phone connection is causing line noise
This is common for long distance calls. Try the call again.
• you specified the wrong modem type for your modem when you configured connection information
• the value of the connect timeout register (S7) is too short.
Use a text editor to open the modem (.mdm) file you are using and change the MLTO value. This value is in 60ths of a second. Try 90 seconds (MLTO=5400). Your value here will map to the S7 register. For more information on the S7 register, see your modem documentation.
Host does not appear to be a FirstClass server
You may get this error because:
• the two modems negotiated, but the system at the other end did not respond to the FirstClass login request
Make sure you are specifying the correct modem phone number, with any necessary dialing prefixes, in your server setup information.
• there are hardware handshaking problems (Mac OS only)
Make sure you have a cable that supports hardware handshaking.
Communication failed while connected
When a modem connection fails while a call is in progress, the cause can be difficult to identify. Possible reasons are:
• a poor phone connection is causing line noise
This is common for long distance calls. Try the call again.
• another application, such as a screen saver, graphics application, or file compression utility, running on your computer is using up available system resources
Quit other applications and try again.
• the network packets may be interfering with the serial port, if you have a high-speed modem and are also connected to a network
Disable the network connection and try again.
• the baud rate that was specified when you configured connection information is too high.
FirstClass trace information
Trace information tells you how the connection between your FirstClass client and a server is operating. You can use this information to help you solve your problem on your own, or with the help of your administrator.
Trace information can be logged for various connection events. This information is added to the standard logging information in the FirstClass client log file FCIC.log (Windows) or FirstClass®.log (Mac OS, Mac OS X). In Windows, you specify debug=1 as described below to generate the log file. On Mac OS and Mac OS X, press Command Option as you start FirstClass. You will see a console window, which is an online version of the log that is being generated.
In Windows, the log file is saved with an extension of .old the next time you start FirstClass (if debug=1 is still set). If you need to save several log files, rename each one with a unique name before you next start FirstClass.
On Mac OS and Mac OS X, FirstClass overwrites the log file each time you start the client. To save log information permanently, rename the log file before you next start FirstClass.
When you supply connection information as part of configuring your connection, you can specify the events for which you want trace information logged.
To specify the trace information to log
1 Open the FirstClass Login form.
2 Make sure a settings file is selected at "Address" that uses the type of connection (for example, LOCAL NETWORK) for which you want to log trace information.
Note
Trace information will be logged for every settings file that uses this type of connection.
3 Click Setup to open the Service Setup form.
You can verify that you are configuring the correct connection type by looking at the value in "Connect via". For example, to log trace information for a modem connection, this field should say MODEM.FCP.
4 Click Configure.
5 Click the Advanced tab on the configuration form.
6 Select the events for which you want trace information at "Trace options".
7 Add the following line in the [FCSetup] section of the FCIC.ini file in your Windows folder, if you are using Windows:
debug=1
This causes FirstClass to generate the FCIC.log file.
|