Test for ports listening for an application on w2k3 server

[UnknownEntity]

Hi all,

Trying to resolve a query related to an application for open ports on a server.

Server = 10.25.0.90 Ports required TCP 5767 UDP 6766

I am trying to establish whether this server is blocking these port numbers. At CMD I haave entered;

c:\netstat -an |find /i "5767"
>TCP 0.0.0.0:5767 0.0.0.0 Listening
>UDP 0.0.0.0:15767 *.*

Does this mean that these ports are closed on this server on does this mean that the application is simply not LISTENING on these ports and the ports are open????

I need to find out out if this server is blocking this port locally, if it is I need to open it, I have no firewall on the server and firewall service is disabled. Thanks

Drakul.

 

[itsp1965]

All this shows is that your machine is listening on port TCP 5767 but not UDP 6766. Where are these ports defined in your application or is it set by default? Blocked at a firewall would not allow traffic flowing inbound/outbound, it wouldn't affect what your machine is actually listening to

 

[UnknownEntity]

Hi itsp1965,

These are set by default as far as I am aware, I just need confirmation that this port is actually open? The fact that it is listening, does this mean that the port is open?

Also I have entered netstat -ano to see the corresponding PIDs and matched them in Task Manager, there are other image names associated with the application with different PID values that have no listing after the output of netstat -ano. Does this mean that the programmers need to configure the application for ports listening to these corresponding image names?

Thanks.

Drakul

 

[UnknownEntity]

Sorry I forgot to add >

In my first output I had *.* on the second line. Does this mean that the connection is closed?

Thanks.

D.

 

[itsp1965]

Well it all comes down to your netstat output doesn't show any entries for the secondary port (ie UDP 6766)in LISTENING/CLOSED or any state whatsoever, therefore either it's not activated by default as you indicated, or 6766 is used for establishing sessions against the app. Either way I would contact the application vendor for more guidance.

 

[Roadki11]

Well his netstat query was specific to 5767 so udp 6766 is not going to show in the results even if it listening. Looks like TCP 5767 is listening but I am not sure why its showing 0.0.0.0, that seems strange to me, should show the local host name and or foreign address that is connected. Any chance this app is bound to a secondary adapter that doesnt have an IP? You can at least test the TCP port from a foreign machine with the following command from a command line, that will tell you if its listening and answering on TCP 5767. Its a little harder to test UDP ports because they are connectionless/stateless, there are 3rd party apps that can test UDP ports, just google test UDP port and pick one.

telnet 10.25.0.90 5767



RoadKi11

"This apparent fear reaction is typical, rather than try to solve technical problems technically, policy solutions are often chosen." - Fred Cohen