Last Updated: 07-28-98
The OS/2 Warp dialer is an interface over the built in TCP/IP software provided with Warp. The following guide should be used for any problems connecting to the service. Some of these steps may be specific to Warp, Warp Connect or Warp 4 (the beta name was Merlin).
There are two distinct versions of the OS/2 Dialer v1.67 or lower and v1.68 and higher. The setup sections below are based on your dialer:
Note: This dialer version is usually available in separate Internet or intranet versions. If you are using the intranet dialer you may need to specify DNS servers in OS/2 TCPCFG. Contact your SA or local support for the DNS settings you should use.
Note: This dialer version allows you to specify an Internet and/or intranet connection. If you are using an intranet connection you may need to specify DNS servers in OS/2 TCPCFG. Contact your SA or local support for the DNS settings you should use.
Before troubleshooting a connection problem you should run a Ping test to confirm the problem is with the dialer and not your network software (i.e. Netscape). Ping can be run in an OS/2 Window. To Ping, connect to the network, start an OS/2 Window and type "ping server.name" (without quotes and where server.name is the server you would like to ping). All users can ping their DNS server(s) and Internet users can ping www.attbusiness.net. If you are unable to ping any server, you have a connection problem so troubleshoot the dialer. If you can ping it is probably a problem with the network application that is failing. Here is an example of a ping of www.attbusiness.net (let your process go about 10 lines before hitting control C to stop the ping process):
C:\>ping www.attbusiness.net PING www.attbusiness.net: 56 data bytes 64 bytes from 204.146.17.5: icmp_seq=0. time=344. ms 64 bytes from 204.146.17.5: icmp_seq=1. time=344. ms 64 bytes from 204.146.17.5: icmp_seq=2. time=344. ms 64 bytes from 204.146.17.5: icmp_seq=3. time=281. ms 64 bytes from 204.146.17.5: icmp_seq=4. time=344. ms ----www.attbusiness.net PING Statistics---- 5 packets transmitted, 5 packets received, 0% packet loss round-trip (ms) min/avg/max = 281/331/344
The various OS/2 Dialer versions are quite old. The telephone numbers and modem commands may be out of date if you are using the older dialer versions. Usually adding the correct number and modem commands will resolve most connection problems:
Note: For those upgrading Warp Fix Packs you may have a COM.SYS larger than 16888 bytes, i.e. 16912. It may give problems so download the four fix files. Warp Connect is loaded with the correct com.sys.
Note: Be sure to make a backup of these files before replacing. Warp 4 (Merlin) users should only concern themselves with the dialer.
Most problems with Warp 4 are related to Modems and/or the Built in TCP/IP from IBM. Verify you have the latest dialer version. Test dial into another gateway to verify the problem is not with the local access gateway. You may have problems if you are using Socks support in OS/2 TCPCFG (this can be run from an OS/2 Window). Check the other troubleshooting in this document as well. If you receive any TCP/IP errors you can contact Warp support or consult help information on your TCP/IP settings. Also try dialing in using Dial Other Internet Providers and if that fails the problem is probably not related to the OS/2 Dialer.
Obtain the PPP setup guide for Dial Other Internet Providers and try a PPP connection. If you fail to connect, the problem is probably with the modem or IBM TCP/IP.
If you have an External modem your modem is connected to a Serial port UART chip which can cause connection problems unless it is a 16550. To determine if you have an adequate UART chip type MODE COMx (where x equals the com port) in an OS/2 Window. If the BUFFER field is Auto then you have the 16550 UART, if not the BUFFER field is N/A.
SIO drivers are not supported by the helpdesk and can cause various connection problems. These drivers are sometimes used to allow 115200 connections (most versions of com.sys only allow 57600). Your throughput rarely increases when changing between 115200 and 57600.
This is a common error in Warp Connect and it occurs because the config.sys has errors. Contact Warp Connect for assistance with this error or compare the config.sys file of a machine that is working.
OS/2 Warp does not automatically recognize COM3 or 4 but you can point to COM3 or 4 by editing the config.sys. Edit the config.sys and search for com.sys. You should find this line: DEVICE=X:\OS2\BOOT\COM.SYS Simply add (n,addr,irq,s) after the com.sys where:
The OS/2 Warp Dialer is not tested to be used with a Lan or modem pool. It may work for a time but will usually stop working. You should contact your Lan administrator for assistance with Lan/Dial conflicts.
Most other connection problems will be related to your modem and/or local phone lines. Obtain the appropriate help documents for help.
Related Documents that may Assist you:
Additional Contacts: