Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

My server: Windows Server 2003. Their server: probably the same thing... it's running active directory LDAP over there...

Problem is when attempting to connect to LDAPS over a secure port, it just times out. However it works totally fine on my QA server (server A) but on live production server (server B) it just times out. I have set everything up the same on both servers... They said they have allowed both of my servers through their firewall over the specific port, however it only works on one of them, thus I know it is not my code failing but some other issue... because like I said, it works fine on QA but fails on Live...

is there anything I can run to check why it would be timing out from the live server? I tried ping and tracert and the effects are the same on both servers, it responds fine... however when trying to add the port number to these commands i just get an error, is there a similar command that will test the port?


share|improve this question
up vote 3 down vote accepted

A very basic check you can try is to telnet to the port, if it times out then it's inaccessible, if you get a clear screen and flashing cursor (it may timeout with and error eventually or possibly even print some text), just type "TELNET {IP Address} {PORT}".

share|improve this answer

To add to Chopper3's answer, there is also a program called nmap that would come in handy for this. There is a nice windows version. You should be able to type nmap and then the IP address and it will scan for open ports on the given ip.

share|improve this answer
Not as a criticism of this answer, but as a warning: Some administrators view nmap scans as threatening, and some IDSes or firewalls view this activity as malicious and act to block all communication from the external host. You should let the admin of the remote host know before you start an nmap scan. – Slartibartfast Nov 16 '10 at 4:35

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.