Document # 103 OS/2 Dialer Connection Help

Last Updated: 07-28-98

Table of Contents

  1. Introduction (Please Read First)
  2. Setting up the Dialer
  3. Ping to Test your Dial Connection
  4. Use the Latest Access Number and Modem Commands
  5. Four Fix Files (the dialer, com.sys, vcom.sys and slip.exe)
  6. Warp 4 Information
  7. Test Dial with Dial Other Internet Providers
  8. Miscellaneous Connection Issues
  9. Related Documents and Contact Information

A. Introduction (Please Read First)

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).


B. Setting up the Dialer

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:

  1. Setup for Dialers v1.67 and lower:

    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.

    1. Start the dialer application.
    2. Click the Settings button on the main dialer window.
    3. Under the Phone tab you will need choose or type a local access number to access the network. You should remove the area code if needed, choose tone or pulse and add any necessary dial prefix.
    4. Under the Modem tab you should choose your modem brand/model. Since the dialer modem commands may be old you may need to manually add modem commands. The Default modem command, which should work, is:
      • First: AT&F
      • Second: AT&D2&C1X4V1Q0S7=70
      Choose the modem speed (it is best to choose 57600) and Com port.
    5. All other settings are preferences.

  2. Setup for Dialers v1.68 and higher:

    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.

    1. Start the dialer application.
    2. Click the Settings button on the main dialer window.
    3. Under the Identity tab you should choose or specify the dialer profile you would like to update. Verify your login account and userid are typed into the appropriate fields.
    4. Under the Phone tab click Change next to the primary access number. Under Change choose your Country, State and local access number. Remove the area code or add a dial prefix if necessary. Choose the connection type of PPP or SLIP (switch these if you have any problems connecting). The Location settings can be used to add dial prefixes or choosing Tone or Pulse.
    5. Under the Service tab you will need to choose the dial service you are authorized to use. If you choose an incorrect service you may receive the Error 25 You are not Authorized... Consumer Internet users should choose the Internet option.
    6. Under the Modem tab you should choose your modem brand/model. Choose the modem speed (it is best to choose 57600) and Com port. Click Details/Customize to add or change the modem commands.
    7. All other settings are preferences.

C. Ping to Test your Dial Connection

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


D. Use the Latest Access Number and Modem Commands

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:

  1. The latest text list of Internet access numbers is available from: ftp.attbusiness.net/pub/ibm/phone.lst

  2. The latest text list of modem commands is available from: ftp.attbusiness.net/pub/ibm/phone.lst
    The current default string that should allow you to connect is:
    Default: AT&F AT&D2&C1X4V1Q0S7=70
    Most of the new modem commands are in the same format.


E. Four Fix Files (the dialer, com.sys, vcom.sys and slip.exe)

  1. Check your dialer version by clicking the help button on the dialer. The version should read v1.67, if not, it needs to be updated. You can use the dialer v1.67 or the new dialer series v1.68 and higher. You may find the dialer v1.67 has less connection problems and you can have both dialer versions installed on your machine.

  2. Com.sys, Vcom.sys and Slip.exe (for Warp and Warp Connect users only): Check your Com.sys size by opening an OS/2 window. Type "CD\OS2\BOOT", then type "dir com.sys". The file name and size should be listed and the size of the file should be 16888 bytes. If not it needs to be changed along with the files vcom.sys and slip.exe.

    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.

  3. Obtaining the four fix files:

    Note: Be sure to make a backup of these files before replacing. Warp 4 (Merlin) users should only concern themselves with the dialer.

    1. Downloading the four fixes using anonymous FTP:
      • FTP to ftp.attglobal.net.
      • The files can be found in the directory pub/ibm/OS2_Client (make sure you download these files as binary if using FTP-PM).
      • Download the file com.sys, vcom.sys, slip.exe and the dialer itself (inst167.exe is the dialer v1.67 and install.exe will be the latest version of the newer dialer version). You should download and try both dialer versions.

    2. Where to replace the files on your PC:
      • COM.SYS goes in the OS2\BOOT directory.
      • VCOM.SYS goes in the OS2\MDOS directory.
      • SLIP.EXE goes in the TCPIP\BIN directory.
      • The dialer(s) go in a Temp directory, i.e. TCPIP\TMP.

    3. A final step if you downloaded the dialer(s):
      • Run the dialer install program(s) and reboot.


F. Warp 4 Information

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.


G. Test Dial with Dial Other Internet Providers

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.


H. Miscellaneous Connection Issues

  1. Check your UART chip if your modem is External:

    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.

  2. The replacement SIO com drivers can cause problems:

    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.

  3. Slip Ended Unexpectedly (config.sys problem usually in Warp Connect):

    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.

  4. Cannot Initialize your modem on COM3 or COM4:

    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:

    It should look something like this (if using COM3) when finished: DEVICE=X:\OS2\BOOT\COM.SYS (3,3e8,4,s)

  5. Cannot connect on a Modem Pool or with a Lan connection:

    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.

  6. Other general connection issues:

    Most other connection problems will be related to your modem and/or local phone lines. Obtain the appropriate help documents for help.


I. Related Documents and Contact Information

Related Documents that may Assist you:

Document # 121 Modem Listing Document
Document # 122 Modem Help Guide
Document # 120 Line Noise (Phone line testing procedures)
Document # 124 Dial Access Phone Number List
Document # 208 PPP setup guide for Dial Other Internet Providers

Additional Contacts:

Your Internet Helpdesk is your Network and Dialer Support.
Your TCPIP support is provided through IBM.
IBM OS/2 WARP Software Support (US/CA)
Consumer Support (60 day complementary): 800-772-2227
Enterprise Support (extended contract): 800-992-4777
Warp CONNECT Support: 512-339-5000