Can't close telnet windows

K

kenw

I use Windows command-line telnet frequently to administer remote
equipment. For the most part, it works well, but sometimes, when I end the
telnet session, I can't close the window. At the moment I have a fully
patched XP system with two such hung windows; one launched from command
prompt, the other via a desktop icon.

That hung, orphan windows are so persistent that I can't even log off or
reboot normally. I have to crash the system to get rid of them. I can
kill the processes that apparently created them, but the windows remain. If
I use Sysinternals' Process Explorer to identify the owner of a window
(either before or after I kill the process), it says it cannot locate such
a process.

This in intermittent problem I been encountering for years, and have never
found even an explanation for, or admission by Microsoft that the problem
exists. A bit of googling ("windows telnet command close|hang 2000|xp"),
however, shows I'm not the only person who has experienced it.

Is it known bug, am I doing something wrong, or...?

/kenw
Ken Wallewein
K&M Systems Integration
Phone (403)274-7848
Fax (403)275-4535
(e-mail address removed)
www.kmsi.net
 
P

Paul Knudsen

I use Windows command-line telnet frequently to administer remote
equipment. For the most part, it works well, but sometimes, when I end the
telnet session, I can't close the window. At the moment I have a fully
patched XP system with two such hung windows; one launched from command
prompt, the other via a desktop icon.

That hung, orphan windows are so persistent that I can't even log off or
reboot normally. I have to crash the system to get rid of them. I can
kill the processes that apparently created them, but the windows remain. If
I use Sysinternals' Process Explorer to identify the owner of a window
(either before or after I kill the process), it says it cannot locate such
a process.

This in intermittent problem I been encountering for years, and have never
found even an explanation for, or admission by Microsoft that the problem
exists. A bit of googling ("windows telnet command close|hang 2000|xp"),
however, shows I'm not the only person who has experienced it.

Is it known bug, am I doing something wrong, or...?

I tried WinXP Telnet once or twice, and then got Zoc. I suggest you
check it out. Don't have a link but Google is your friend.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top