RE: Sockets problem (what is)

[Evan Harris <spanner@xxxxxxxxxx>]

Of course you could also do this from your AS/400...

depending on what end of the connection you are this might show you what
your sockets program is trying to connect on. If you are using unique Ip
addresses or user IDs you may be able to find it in there.

Of course depending on which end your are on in relatin to the firewall it
would show a server listening but no connections being made, or might show
a client connection waiting for the server to accept and timing out.

Hope this helps


>In windows do a DOS window and type NETSTAT -an
>
>This is best done from a HTTP server to show what is going on.
>
>For each connection you will see the IP of the local server and port, and
>the remote client and port.  The server will see it on port :80, but the
>client will be on some obscure port.  Here is an example from our own IIS
>server:
>
>   TCP    192.0.0.8:80           63.220.237.194:2623    ESTABLISHED
>   TCP    192.0.0.8:80           63.220.237.194:2624    ESTABLISHED
>   TCP    192.0.0.8:80           64.242.2.37:29903      ESTABLISHED
>   TCP    192.0.0.8:80           64.242.2.37:29908      ESTABLISHED
>   TCP    192.0.0.8:80           65.29.109.59:1266      ESTABLISHED
>   TCP    192.0.0.8:80           66.76.46.228:2166      ESTABLISHED
>
>for like 63.220.237.194 it has moved the request from port 80 to port 2623
>internal to the server, but the remote computer's client still sees it as
>port 80.  This is HTTP port 80 instead of Telnet port 23, but same
>difference.