Link to home
Start Free TrialLog in
Avatar of ctrunk514
ctrunk514Flag for United States of America

asked on

How to check if a port is open or not

I am a new administrator of a webserver that resides outside our cooperate firewall on the DMZ.  I have asked the network admin to open ports 9998, 9999 and 1433 (for the NetIQ agent) to/from the external webservers to our two NETIQ servers.  He is telling me that the ports are open, but the agent is not working.  I not 100 percent sure that he successfully opened the ports but do not have the access to the firewall to double check. In the mean time, he insists that they are open.  How can I prove or disprove that this ports are indeed open or not.
Avatar of TanLiHao
TanLiHao
Flag of Singapore image

Under a linux box :

nmap -p 9999 W.X.Y.Z

Avatar of ctrunk514

ASKER

how will this work, we are talking about an internal network.
both the webserver and the netiq servers on the inside are windows boxes.
Microsoft provide a nice tool ttcp.exe which runs as a client and server. You can set one to listen on one server and then the other to "transmit" from your test client.
 
More details here: http://blogs.isaserver.org/pouseele/2006/07/14/microsoft-tcp-udp-test-tool-ttcp/
I looked on my windows 2003 server disk and it does not seem to have a Valueadd\Msft\Net\Tools folder as suggested by this artical.  I did a quick search on google and the Microsoft download site and came up with nothing.  
If you have some scripting languages available on your webserver on the local network, try something like this (php version) :

<?php
$fp = fsockopen("W.X.Y.Z", 9999, $errno, $errstr, 30);
if (!$fp) {
    echo "$errstr ($errno)<br />\n";
}
else
{
    fclose($fp);
    echo "port 9999 opened";
}
?>

Open in new window

mmm, I've just checked one of mine and the folder / file are definately there.  I could post the exe, it's only 51KB but I dotn want to risk the wrath of copyright laws!
This seems to be a port of a similar tool, not tried it myself though:  http://www.pcausa.com/Utilities/pcattcp.htm
If you have windows access to the DMZ server, you can just try under command line :

telnet W.X.Y.Z 9999

You will get "connection refused" if the port is closed.
I tried the telnet command from the DMZ server and it brings back a blank prompt with no message.

telnet servername 9999

The servername does reslove by IP when pinged.
Well, if it doesnt resolve to an IP then the telnet is never going to work, try telnet'ing to the IP.
Blank prompt on telnet usually means that the port is opened and the server is awaiting command.

Try another dummy port with telnet to check. Ping does not always means anything, the server could block ICMP queries.
 
When I try to telnet to another port I get the error':

C:\>telnet vhhnqwms.hollandhart.com 9997
Connecting To vhhnqwms.hollandhart.com...Could not open connection to the host,
on port 9997: Connect failed

C:\>


When I telnet to 9999 I get the blank screen, but If I try to type something (anything) it errors with the following message:

HTTP/1.1 400 Bad Request
Content-Type: text/html
Date: Mon, 13 Jul 2009 16:01:48 G
Connection: close
Content-Length: 35

<h1>Bad Request (Invalid Verb)</h

Connection to host lost.


Maybe thats normal, I am not sure.


Another test I did was to setup a website using port 9999 on the inside server.  I verified that this worked on the internal network. But it DOES NOT WORK on the DMZ server.  It times out.

The other thing I found out is that these webserver have many different IP addresses.
ASKER CERTIFIED SOLUTION
Avatar of flob9
flob9
Flag of France image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Conclusion : the ports are opened, but the NetIQ agent cant connect.

Perhaps NetIQ agent check the server by ping before connexion, and the ping is disabled on the server. Ask the network admin if ICMP is closed, and open it if needed.

Once connected with telnet over port 9999 I type the command GET then hit enter and get kicked out with the following message:

HTTP/1.1 400 Bad Request
Content-Type: text/html
Date: Mon, 13 Jul 2009 16:11:00 GMT
Connection: close
Content-Length: 35

<h1>Bad Request (Invalid Verb)</h1>

Connection to host lost.


____________________________





That is correct ... also, IIS can not connect.

ICMP is open and works fine.
I think the problem might be with the different IP addresses that are tied to this address.  The netadmin is opening the traffic from the DMZ IP to the internal IP.  He is using the IPs that reslove in DNS but there are like 15 other addresses binded to this one NIC.

You need to input the "/" also.

Anyway you can try in a browser on your dmz box : http://servername:9999/
Check the other ports (9998 and 1433) via telnet or browser.

This does not seems to be a dns issue, since the server is responding (with http errors).
A closed port never send a response.