Re: Command Prompt stuck open


Hi All,

Like Dan and Yonder, I too have had this issue for over 3 years now.

This is not a graphics, driver, memory, safemode, yada blah and etc
issue (not to be disrespectful) but is rather an issue on how a telnet
session termination is handled.

I am an experienced and professional IT person and have used a few
different latops and desktop systems in the last 3 years - all of which
show the same problem when it does 'by chance' happen. These systems
differ in make and configuration (note: even my colleague has had this
happen in his WinXP vmware guest). What we need is a 'Microsoft' IT
expert to track this down.

I work with networking gear and as such have several 'cmd.exe' windows
open with a telnet session established to remote devices. And this is
when the issue 'can' occur. The issue is not reproducible all the time
but happens when a user (in this case me) is logged in to a remote
device via telnet.

If the telnet session is terminated via a remote device timeout (as is
the case with cisco gear for security reasons) the 'cmd.exe has a good
chance of hanging - not always - no way to predict when. Then the only
way to close the window (and subsequently turn off the computer b/c as
mentioned it won't shut down) is to power off the machine via holding
the power button. The machine operated fine aside from not being able to
close the window or shutdown the machine. (so to summarize, open cmd.exe
window, issue a telnet to remote device. Login. Do some work, turn and
talk to someone wanting to discuss how they painted the deck on the
weekend, turn back to the computer to find the session has expired do to
a lack of activity. type exit.. nothing.. click the 'x' and nothing.
Cllick start shutdown.. processes start to close but no full shutdown
happens.)

I have tired waiting for MS to release a hotfix as I just don't see it
coming. I find it hard to beleive that this hasn't been called into MS
or fixed yet. Strange!!!

Any MS experts out there that can shed some light on why this session
termination is not handled properly and is causing this to happen?

Cheers!


.