Troubleshooting TCP/IP Network Connections in LapLink Applications - Search Again

 

SUMMARY

I’m having trouble connecting over a TCP/IP network using a LapLink application in Windows 95, 98 or NT. Is there anything you can suggest to help me?

 

SOLUTION

LapLink contains a tool for troubleshooting network and other methods of connection within LapLink Troubleshooter. Click on Help Topics from the Help menu and choosing Start Troubleshooters activates it. If you continue to have trouble connecting over TCP/IP network after using the LapLink Troubleshooter, then follow the suggestions in this document.

  • If you receive the following error message
    The TCP/IP network is currently unavailable. You cannot connect over the TCP/IP network until it is correctly configured. Please refer to Technical Document: TCP/IP Port Shows as Unavailable within LapLink.

  • Check the properties of WINSOCK.DLL
    1. From Windows Start menu, point to Find, Files/Folders to locate WINSOCK.DLL
    2. Right-click on the file name and click on Properties
    3. Under the Version tab, check that the Company Name is Microsoft.
    4. If the Company Name is not Microsoft, uninstall TCP/IP and reinstall from your original operating system media. If the Operating system is Windows 98, refer to Technical Document: How to restore WINSOCK.DLL on a Windows 98 Machine
      Note: Make sure that you copy down the TCP/IP Property settings before uninstalling. If you use TCP/IP only for connecting to the Internet, check with your ISP for any special settings.


  • Verify the IP Address and Subnet Mask for each of the computers.
    1. For Windows 95 or 98: From the Windows Start menu, point to Run Type winipcfg.exe
    2. From Windows NT: From the Windows Start menu, point to Programs, MS-DOS Prompt. At the MS-DOS prompt, type ipconfig.exe and run.


    The IP address is a series of 4 octets in the format of www.xxx.yyy.zzz. The Subnet Mask is also four octets such as 255.255.255.0. Write down these numbers.
    • Use PING to see if the target machine can be seen by the source.
      1. From the Windows Start menu, point to Programs, MS-DOS Prompt.
      2. At the prompt, type ping www.xxx.yyy.zzz where www.xxx.yyy.zzz is the IP address of the other machine.
        • A correct response should be Reply received by www.xxx.yyy.zzz followed by some additional statistics.
        • A response of Request timed out or Destination host unreachable indicates that the machines do not see each other. Possible causes include:
          • A piece of hardware between the two systems may not be working properly
          • There may be a problem with the IP addressing on either computer. Verify the proper IP address is being used.
          • The Subnet Mask are not set properly on the computers. On networks where the computers do not have a router between then, the Subnet Mask must be set the same on both machines.
          • If connecting over the Internet, an Internet Service Provider may be routing traffic inefficiently.



  • Run TRACERT to determine how many 'hops' or connections are between computers.
    1. From the Windows Start menu, point to Programs, MS-DOS Prompt.
    2. At the prompt, type tracert www.xxx.yyy.zzz where WWW.XXX.YYY.ZZZ is the IP address of the other machine. It returns the ‘route’ of each location your network connection touches before connecting to the final destination. If the TRACERT response shows more than 30 hops, LapLink may not be able to see the connection and will likely time-out.
      NOTE: Environmental internet issues, such as heavy internet traffic during peak usage times, can cause a response of greater than 450ms. Try your internet connection again when internet traffic is reduced. To view current internet traffic conditions, point your web browser to http://www.internettrafficreport.com .


  • Check to see if there is a hardware or software firewall installed. If a firewall application, hardware device, or a proxy server is in use, port 1547 (registered exclusively for LapLink) must be opened in order to permit LapLink network connections. If you are unsure about this, consult your ISP or Network/System Administrator for additional help.


  • Free up system resources by closing out of any open items or applications before initiating a connection.

    1. Close other open applications on the taskbar.
    2. Bring up the Close Program window by pressing CTRL-ALT-DEL keys simultaneously one time.
    3. End-task on other items that are running. However, do not end-task or close Explorer or Systray.

  • If convinced that all of the hardware is working and the IP addressing is correct, try removing all installed network components. Consult your network/system administrator for additional help.

    1. Right-click on the Network Neighborhood icon and click on Properties.

    2. Click on the Configuration tab.

    3. In the dialog box, highlight all network components and select Remove. Make note of what is removed.

    4. Click on OK and reboot the computer when prompted to.

    5. When the system has finished rebooting, right click on the Network
      Neighborhood icon and click on Properties

    6. Click on the Configuration tab.

    7. Click on Add.

    8. Reinstall the network adapters and protocols you deleted earlier. Ensure the IP Addresses are set properly within the TCP/IP protocol.


    In following the steps listed above, the files related to TCP/IP are not removed or replaced on the hard drive. If you wish to completely replace these files, consult Microsoft's Knowledge base article Q181599. Copy and paste this URL into your browser: http://support.microsoft.com/support/kb/articles/Q181/5/99.asp


     

     Related Articles

      Error Message: LapLink Reports the TCP/IP Port as Unavailable
      How to Determine the IP Address on a Computer
      How to Install and Configure LapLink for Your First Local Area Network (LAN) Connection
      How to Restore WINSOCK.DLL on a Windows 98 Machine
      IP Address Fails to Resolve During a LapLink TCP/IP Connection
      Using PCsync 1.x to Connect Over a Local Area Network

     

    Last updated: Tuesday, May 29, 2001

    Article #132

    Legacy Article #5838