No that's wrong.  So far none of the solutions presented has given me the IP or 
hostname of the particular telnet clients involved.

As I mentioned before, you probably didn't read this one, when you start a 
telnet client it appears in the tasklist

In this case, it's tl_server.exe which is Rocket's special telnet server
However IF you do *not* login on that telnet server, then no corresponding 
entry is made in the netstat table, or perhaps one is made and then nulled out 

At the point you want to ask, well what are the ip numbers of these 
connections, you have 62 tl_server entries and 61 (repeat 61, not 62) netstat 
entries.  That one extra "zombie entry" in the tasklist, is not present in the 
netstat output.

So netstat is apparently only showing live or active connections or whatever 
you might call it, whereas the windows server is holding on to one or more 
*extra* zombies.

Yes you can kill those *extra* tl_server.exe sessions, but really it would be 
nice to know what activated them.

I killed all the zombies last week, and now I'm back up to about six extra 
tl_server sessions without corresponding netstat entries




-----Original Message-----
From: Tony Gravagno <>
To: u2-users <>
Sent: Mon, Sep 10, 2012 2:37 pm
Subject: Re: [U2] [Windows]

What's the real goal here? To get the hostname of any random telnet
client? You have the information you need to do that. If nothing else
you can get the IP address and someone can manually chase down who's
connecting in. Block rogue connections at the firewall.

I mean, at this point you're going around in circles and the detail
you're providing is irrelevant to the task. What still needs to be
resolved? You're right. It doesn't matter what client program is being
used as long as they come in via the standard telnet port and we don't
care what time of night someone is connecting in.

Why can't this thread be marked RESOLVED?


> From: Wjhonson 
> Oops I need to modify my message about these zombie tl_server.exe
> Windows sessions...

[huge snip of mostly group-generated footers]

U2-Users mailing list

U2-Users mailing list

Reply via email to