Difference between revisions of "Troubleshooting with telnet"
Jump to navigation
Jump to search
| (9 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | = Using Telnet to Troubleshoot Connection Issues | + | =Using Telnet to Troubleshoot Connection Issues= |
| − | |||
| − | |||
| − | |||
| + | ==Background== | ||
Sometimes when a vendor is unable to connect to an interface it is a networking issue between the client and vendor. A great way to troubleshoot this is by using telnet. | Sometimes when a vendor is unable to connect to an interface it is a networking issue between the client and vendor. A great way to troubleshoot this is by using telnet. | ||
| + | [[Image:wikiconnectr4.png]] | ||
| − | + | [[Image:wikiinterface1.png]] | |
| + | ==Process== | ||
*On the ConnectR server open the Command Prompt, and type in: telnet localhost "port number" | *On the ConnectR server open the Command Prompt, and type in: telnet localhost "port number" | ||
| − | + | *:[[File:telnet3.png]] | |
| − | [[File: | + | *Next on the vendors interface server telnet to the IP address and port |
| − | + | *:[[Image:wiki5.png]] | |
| − | *Next on the vendors interface server telnet to | ||
| − | |||
| − | [[ | ||
| − | |||
*Once you click enter the screen should go blank; this means you're connected. | *Once you click enter the screen should go blank; this means you're connected. | ||
| − | |||
*ConnectR status should change from Waiting to Connected | *ConnectR status should change from Waiting to Connected | ||
| − | + | ==Explanation== | |
| − | == Explanation == | ||
| − | |||
If it works from the ConnectR machine and not the vendor, then it's a networking or firewall issue. If it doesn't work on ConnectR, then most likely the source interface is turned off or misconfigured. | If it works from the ConnectR machine and not the vendor, then it's a networking or firewall issue. If it doesn't work on ConnectR, then most likely the source interface is turned off or misconfigured. | ||
Latest revision as of 20:26, 19 October 2011
Using Telnet to Troubleshoot Connection Issues
Background
Sometimes when a vendor is unable to connect to an interface it is a networking issue between the client and vendor. A great way to troubleshoot this is by using telnet.
Process
- On the ConnectR server open the Command Prompt, and type in: telnet localhost "port number"
- Next on the vendors interface server telnet to the IP address and port
- Once you click enter the screen should go blank; this means you're connected.
- ConnectR status should change from Waiting to Connected
Explanation
If it works from the ConnectR machine and not the vendor, then it's a networking or firewall issue. If it doesn't work on ConnectR, then most likely the source interface is turned off or misconfigured.