Kbase 16946: How to use telnet to troubleshoot network connection problems
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Verified
GOAL:
Using telnet to troubleshoot network error messages
GOAL:
How to use telnet to troubleshoot Client network connection problems
GOAL:
How to troubleshoot error 1432 using telnet
GOAL:
** Could not connect to server for database <DATABASE>, errno <ERRNO>. (1432)
GOAL:
How to troubleshoot error 704 using telnet
GOAL:
** There is no server active for database <database> on -H <hostname> -S <servicename>. (704)
FACT(s) (Environment):
All Supported Operating Systems
Products / Versions
FIX:
To troubleshoot error (1432) the following is required:
1. A UNIX telnet client or the telnet supplied by Microsoft for Windows Operating Systems.
2. The hostname value specified by the -H parameter being used to start the Progress database server.
3. The servicename value specified by the -S parameter used to start the Progress database server.
4. The IP address that hostname is mapping to.
5. The TCP port number that service is mapping to.
What does a successful connection look like?
Microsoft telnet - The block cursor on the top left of the telnet window, and an I-beam cursor. A failed connect will be shown as an alert box with "connect failed"
UNIX telnet - Connected to <hostname> when connection succeeds. telnet: Connect: {error message} when it fails.
Steps to troubleshoot:
1 - telnet {hostname} {servicename}
This should fail if error 1432 or 704 is being received.
2 - telnet {hostname} {port#}
If this fails, proceed to step 3.
If this works, the servicename to port number mapping is not working. The problem lies within the services file or service name provided on -S parameter. Ensure the correct services files has been modified and that the servicename being specified is mapping to the right {port#}. See your network administrator for help locating your services file.
3 - telnet {serverip} {service}
If this fails, proceed to step 4.
If this worked, the problem is the result of a hostname to IP translation problem.
Ping {serverip} should work, while ping {hostname} should fail, indicating that there is either a hosts file problem or a DNS problem. See your network administrator for help with this problem.
4 - telnet 127.0.0.1 {port#} (from the server machine)
If this fails, goto step 5
If this works the problem is not related to hosts, DNS or services files on the client. If the local telnet to the database server can connect the database server is up and listening to the correct port. The problem is that the remote connection is not getting through the network.
ping {serverip} (from the client machine)
or for more details on tracing the route to the serverip:
pathping {serverip} (from the client machine)
If this fails, then the TCP/IP packets are not getting through to the server or the wrong {serverip} value is being used.
if this works, a firewall or some other device that is not propagating the connection on that specific TCP/IP port (for instance a Proxy client) may be the problem. Try other port numbers to see another port will work. If another port cannot connect see your network administrator.
5 - The database is probably not up, or the wrong {port#} is being used. Ensure the database server is running, with the -N TCP parameter and a -S {servicename} parameter. Make sure the server services file maps {servicename} to {port#} correctly. If all the following have been configured correct contact PROGRESS technical support for assistance.