Running DOS/Windows TCP/IP Applications (like Netscape) under OS/2 Warp

and OS/2 Warp Connect.  



This information was copied from various emails captured by members of 

the Team OS/2 Cincinnati Users Group http://www.cincyteamos2.org/

=========================================================================

*** Make sure you have applied the latest TCP/IP patches available at 

http://www.cincyteamos2.org/masterupdate.html for the IAK or Warp Connect

and the IAK.

=========================================================================

 Here are some checks you can run to see if basic TCP/IP connectivity

 is working:

 1) Find some IP address and hostname that represent some other machine.

    If on a LAN, pick some other machine on your LAN nearby.  If using a

    SLIP/PPP connection over a phone line, use the target machine you

    connect to (should be visible during the dialup).

 2) From an OS/2 Window, try to PING that other machine, first by IP

    address, then by host name.

 3) From a DOS Window, try to PING that other machine, first by IP

    address, then by host name.

 4) From a WinOS2 Program Manager session, use FILE->RUN->WPING.EXE to try

    to reach that other machine, first by IP address, then by host name.



If (2) fails, then you do not have TCP/IP installed or activated.

If (2) works, but (3) and (4) do not (not even by IP address), then the

  WINSOCK emulation for DOS/WinOS2 is not working.  For this case, I

  would make sure that x:\TCPIP\DOS\BIN is in the PATH in AUTOEXEC.BAT

  used by OS/2 (on your OS/2 boot partition), that there is a WINSOCK.DLL

  in that directory, that there is no other WINSOCK.DLL in any other

  directory in AUTOEXEC.BAT's PATH, and also that there is no WINSOCK.DLL

  in your WINDOWS or WINDOWS\SYSTEM directories (if using Warp fullpack

  these directories will be \OS2\MDOS\WINOS2 or \OS2\MDOS\WINOS2\SYSTEM).

If pinging by IP address works, but by host name fails, then you have a

   name resolution problem.  Here are the relevant files to check out:

   \MPTN\ETC\HOSTS        if not using a DNS, lists host names for use

                          by OS/2 sessions

   \MPTN\ETC\RESOLV2      if using a DNS with LAN connection, points to

                          DNS to be used by OS/2 sessions

   \MPTN\ETC\RESOLV       if using a DNS with SLIP/PPP connection, points

                          to DNS to be used by OS/2 sessions

   \TCPIP\DOS\ETC\HOSTS   if not using a DNS, lists host names for use

                          by DOS sessions

   \TCPIP\DOS\ETC\RESOLV  if using a DNS, points to

                          DNS to be used by DOS sessions



If you get a "Call to undefined dynalink" error under WinOS2....



  The "Call to undefined dynalink" is a known Microsoft problem.

  This error message appears anytime an application tries to make a

  call to a .DLL file that is an older version than the .DLL that it

  needs. It is a generic WIndows error message that means that the

  application tired to register a .DLL that either does not exist or is

  incorrect. This error can also occur if the OLE .DLL files are not all

  the same version.

  (Curtesy: Mark T. Regan, Network Specialist, Nationwide Insurance)