up vote 0 down vote favorite
1
share [g+] share [fb]

I've already shut down the firewall.

Is there a way to check what is actually blocking telnet?

link|improve this question
Do you mean outgoing or incoming? Are there any error messages? Have you tried using Nmap on the port (default 23) to make sure it's open on the server? – amphetamachine Jan 27 '10 at 6:28
Yes,I can telnet the port from a remote machine. – unknown Jan 27 '10 at 6:34
feedback

2 Answers

up vote 0 down vote

if you have access to the destination server do the following, what results do you get on
netstat -an | findstr /i ":23"

if you get nothing then telnet is not running on the destination server.

if it is running and you have the firewall turned off then there is another firewall in place somewhere. Contact your network dudes to find out whats going on.

link|improve this answer
thanks for the edit, port was wrong right? – user33788 Jun 8 '10 at 15:50
@smokenheap - ya, port 25 is SMTP – MDMarra Jul 15 '10 at 23:34
feedback
up vote -1 down vote

Yes, you can check it.I have no idea have you tried network monitor before, it is a very useful tool for network troubleshooting.

link|improve this answer
How can that tool check what is blocking telnet?Is there a screenshot for this? – unknown Jan 27 '10 at 7:37
Take wireshark for example, you need to capture the packets for several minutes when the problems appear,filter the unnecessary packets and diagnose it. – John Jan 27 '10 at 8:37
No,the problem here is that the telnet action itself is blocked,nothing about packets. – unknown Jan 27 '10 at 8:38
You can diagnose the application by packet sniffing.You can view the process and find out where it is blocked. – John Jan 27 '10 at 9:07
I can check the network information by netstat -ban,but it won't help me find where it is blocked.Could you upload a screenshot showing how it can be used to see what's doing the blocking job? – unknown Jan 27 '10 at 9:17
show 1 more comment
feedback

Your Answer

 
or
required, but never shown
discard