Subject: | |
From: | |
Reply To: | Paveza, Gary |
Date: | Wed, 19 Aug 1998 10:50:57 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Try the program SOCKINFO.NET.SYS
Gary L. Paveza, Jr.
Technical Support Specialist
All opinions are mine and not those of my employer
-----Original Message-----
From: Tony Furnivall [SMTP:[log in to unmask]]
Sent: Wednesday, August 19, 1998 10:32 AM
To: [log in to unmask]
Subject: Listing 'in-use' sockets
One of the benefits of being technogically naive is that sometimes
you ask
questions that may be dumb, but that may be usefuo... So here goes.
Is there any way of getting a list of the sockets in use on a
machine? We
had a runaway client/server process just like the one that Bob
Sorenson
recently described. We were not able to identify the "other" end of
the
connection, and the user had creatively described themselves as
TEMP. Since
we knew this was a Client/Server situation, the question naturally
arose,
"How can we find out who this person is" (At which point the Execute
on
Login" option would have been very attractive!). Icould find no such
capability.
Core question - does anyone know of any utility that will report out
the
in-use sockets, and identify the remote end-points. (Sort of like
NSCONTROL
STATUS=USERS, but for socket connections)
Tony "sitting here half asleep after a late-night trouble shooting
session"
Furnivall
|
|
|