My fault....I meant the remote hostname.
-----Original Message----- From: Timothy Johnson [mailto:[EMAIL PROTECTED]] Sent: Friday, June 07, 2002 4:38 PM To: 'drieux'; begin begin Subject: RE: IP address Maybe I misunderstood what he was asking. I thought he wanted to find out what the local IP of the clients that were connected were. This would work only if you can have the client run it. -----Original Message----- From: drieux [mailto:[EMAIL PROTECTED]] Sent: Friday, June 07, 2002 1:08 PM To: begin begin Subject: Re: IP address On Friday, June 7, 2002, at 12:45 , Timothy Johnson wrote: > For the Win32 command, something like > > `ipconfig` =~ /(\d+\.\d+\.\d+\.\d+)/; > > would work if you just want the ip address, providing you can have the > client run it... I thought that merely showed where the 'connections' were coming from... much that same as vladimir: 57:] netstat -naf inet | grep "513.*ESTABLISHED" 199.108.16.3.513 199.108.16.6.1020 8760 0 8760 0 ESTABLISHED 199.108.16.3.513 199.108.16.11.709 33304 1 10136 0 ESTABLISHED vladimir: 58:] but the problem then is associating the actual 'connected port' to the 'sessions'... or is there a flag I am missing here about ipconfig??? cf: http://www.computerhope.com/ipconfig.htm ciao drieux http://www.wetware.com/drieux/pbl/ -------------- This space left intentionally blank. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
