English
Français

Troubleshooting Connection Errors

Question :

When I attempt to connect to my server, I receive an error message that reads "Connection Failed (10060) - WSA Timeout (WSATIMEOUT)".

Answer :

This error indicates that a timeout occurred before a connection could be made. There are several different situations in which this error can occur.

First, you will need to verify that you have entered the correct IP address or Hostname into TinyTERM. Once you have verified that, you will need to test the network connectivity between your PC and the server. You can do this by using the Windows utilities Ping and Telnet.

Test #1 : Ping your server

Click Start->Run
Type "ping IPaddress" and click OK

Example: ping 66.1.1.1

If you receive multiple timeout messages, this means that either your PC or the server has not been properly configured on your network. You will need to contact your network administrator for assistance in properly configuring your PC or the server.

If your server replies, proceed to the next test.

Test #2 : Telnet to your server using Windows Telnet

Click Start -> Run
Type "telnet IPaddress" and click OK

Example: telnet 66.1.1.1

If you receive an error message that reads "Connection Failed", this indicates that the Windows Telnet program is experiencing the same problem as your TinyTERM software. This also indicates that the problem is not related to the TinyTERM software, but rather to a connectivity problem with either the PC or the server. You will need to contact your network administrator for assistance.

If you are able to successfully connect to your server with Windows Telnet but not with TinyTERM, there is most likely a problem with the DNS on your network or with the DNS settings on your client PC. While we cannot provide you with information on how to fix your DNS problems, we can provide you with a workaround in which you can bypass your DNS by creating a local hosts file.

Creating a local hosts file on Windows 95, Windows 98 and Windows Me

Open an MS-DOS Prompt window.
Make sure that you are in the C:\Windows directory
Type "edit hosts" and press Enter

Example: edit hosts

Type in the IP address of your server, press the space bar, then type in an alias for your server. The alias can be any logical name that identifies your server.

Example: 66.1.1.1 Server

Select File | Save
Select File | Exit

Verify that you can ping the alias that you entered into your hosts file. For ping instructions, see Test #1 above, but use the alias hostname instead of the IP address. If you cannot ping the alias then please verify that you have followed the preceding instructions correctly.

Open TinyTERM and click Edit -> Session Properties

Change the "Hostname, IP address, or Phone number" field from the IP address to the alias name that you entered into your hosts file.

Click Apply and then OK
Click the Connect button

Creating a local hosts file on Windows NT, Windows 2000 and Windows XP

Open a Command Prompt window.
Make sure that you are in the C:\Winnt directory
Type edit hosts and press Enter

Example : edit hosts

Type in the IP address of your server, press the space bar, then type in an alias for your server. The alias can be any logical name that identifies your server.

Example : 66.1.1.1 Server

Select File | Save
Select File | Exit

Windows NT

Right click on the "Network Neighborhood" icon on your desktop and select Properties from the menu
Select the Protocols tab
Select TCP/IP from the list and click the Properties button
Click on the WINS Address tab

Windows 2000

Right click on the "My Network Places" icon on your desktop and select Properties from the menu.
Right click on the "Local Area Connection" icon and select Properties from the menu.
Select TCP/IP from the list of network components and click the Properties button
Click the Advanced button.
Select the WINS tab.

Windows XP

Click Start | Control Panel
Click the Network and Internet Connections link
Click the Network Connections link
Right-click on the Local Area Connection icon and select Properties from the menu
Select TCP/IP from the list of network components and then click the Properties button
Click the Advanced button
Select the WINS tab

Check "Enable LMHOSTS Lookup".
Click the "Import LMHOSTS" button.
Browse to and select your "hosts" file that you created.
Continue to click Apply or OK on each of the open dialog boxes until all of them are closed.

Verify that you can ping the alias that you entered into your hosts file. For ping instructions, see Test #1 above, but use the alias hostname instead of the IP address. If you cannot ping the alias then please verify that you have followed the preceding instructions correctly.

Open TinyTERM and click Edit->Session Properties

Change the Hostname, IP address, or Phone number field from the IP address to the alias name that you entered into your hosts file.

Click Apply and then OK
Click the Connect button

TechTip: Starts Minimized - TechTip: Change the Title Bar from the UNIX application - TechTip: Changing Screen Font Size - TechTip: Code Page Setup - TechTip: Configuring TinyTERM to act as a stand-alone file server for your home or office. - TechTip: Correcting License Problems - TechTip: Debug CScript Errors - TechTip: Determining a PC's Physical Location at Login - TechTip: DSL and Cable Modem Compatability - TechTip: Installing Desktop Shortcuts for TinyTERM - TechTip: Launch Another Windows-based Application From Within TinyTERM - TechTip: Map multiple CScript commands to a single key - TechTip: Mapping your Keyboard to Save Time and Money - TechTip: Missing lines, or misaligned characters using SCO ANSI emulation. - TechTip: Port Forwarding. What is it? - TechTip: Port Forwarding with Microsoft Internet Explorer - TechTip: Port Forwarding with Microsoft Outlook - TechTip: Port Forwarding with Microsoft Outlook Express - TechTip: Port Forwarding with the Opera Web Browser - TechTip: Programming the Mouse Button to Copy and Paste Text - TechTip: Resolving A Missing Application Window On TinyTERM Start - TechTip: Resolving an Error - 115 during a NetUtils Installation - TechTip: Resolving License errors from TinyTERM - TechTip: Scripting TinyTERM Events - TechTip: Setting The background color with CScript - TechTip: Stopping the CenLPD service so you can uninstall TinyTERM Plus - TechTip: Term for Linux / Unix Installation. - TechTip: TinyTERM closes after a connection error - TechTip: TinyTERM Support for Code Pages - TechTip: Transparent Printing in v4.2 - TechTip: Troubleshooting Connection Errors - TechTip: Troubleshooting Connection Failure (Error 10065) - TechTip: Troubleshooting Serial Connections - TechTip: Using TinyTERM's Micro Recorder. - TechTip: Wich version of TinyTERM should one use on a particular Microsoft Windows platform? - Terminal Emulation Competitive Analysis - Secure Shell the need for security - TinyTERM detail overview - TinyTERM Suite - TinyTERM Emulation versus TinyTERM Plus -