interesting port/host issue

[Red Squirrel]

I've never seen anything like this before. I'm troubleshooting a time issue on a server, so first thing I tried is to see if the time server is accessable (ex: firewall) so I do telnet time.windows.com 123 as that is the info I got. Won't connect. Then to not jump on the gun so quick, I try that from a network which has no inbound blocks, still can't connect. Baffled, I try a port scan, and the port scan shows tcp port 123 opened/filtered.

Why would a port scan work, but not telnet? And what exactly does filtered refer to?

From a win2k srv box, any way to check if its accessible, other then telnet (which is not working)

 

[n0cmonkey]

Did you try connecting to udp/123?

What were you using to scan it with? Does the documentation mention open/filtered?

 

[spidey07]

depending on the time protocol used it could be UDP.

 

[Red Squirrel]

It was TCP. I used nmap and it said TCP/filtered 123. thats why I found it odd that telnet would not connect to it.