Re: PuTTY 0.54 hangs intermittently on Windows 2000

From: Bruce (bel_at_gal.co.za)
Date: 02/20/04 

Date: 20 Feb 2004 06:58:00 -0800

bel@gal.co.za (Bruce) wrote in message news:<e3374ad6.0402180556.5beeae98@posting.google.com>...
> Owen Dunn <owend@chiark.greenend.org.uk> wrote in message news:<838yj1d7dk.fsf@chiark.greenend.org.uk>...
> > bel@gal.co.za (Bruce) writes:
> >
> > > ... except that after a random amount of time (from 10 minutes to over
> > > 24 hours), _all_ the PuTTY sessions (each to a different server)
> > > simultaneously hang with no error message. Once this happens, the PuTTY
> > > tasks are unkillable. If you repeatedly try to end one of the tasks,
> > > Windows responds with:
> > > "This program cannot be closed. If it is being debugged,
> > > please resume it or close the debugger first."
> > > Even with only one PuTTY session open the same thing happens.
> > >
> > > Oddly enough, once PuTTY has hung, all new PuTTY sessions hang
> > > immediately with no login prompt. Windows has to be rebooted to run
> > > PuTTY again. Telnet sessions (not PuTTY) connected to other servers
>
> > > This has been happening for a while now with PuTTY 0.53b, so I was
> > > hoping PuTTY 0.54 would fix it, but no such luck.
> >
> > I don't recall anyone reporting the problem to us, so it's hardly
> > surprising that we've not fixed it. PuTTY works fine on Windows 2000
> > for us.
> >
> > Is there any chance you could debug one of the hanging PuTTY processes
> > to find out where it's stuck?
> >
> > Do other network programs still work when PuTTY is in this hanging
> > state? What about the other PuTTY tools like plink, pscp, and psftp?
> > Are there any interesting messages about sshd in the logs on the
> > Solaris machine? Are you using pageant? Is there any NAT or
> > firewalling between you and the SSH server? Have you been able to
> > reproduce this on any other Windows 2000 machine?
> >
> > (S) (PuTTY team member)
>
> Of course now that I want PuTTY to hang, it won't!
>
> But what I can give you for now is:
>
> Other network programs (including Telnet) continue working fine after
> PuTTY has crashed. But no new PuTTY sessions can be started until
> Windows is rebooted.
>
> I am not using pageant. There is no NAT or firewalling between me and
> the SSH servers, except for ZoneAlarm on the Windows 2000 machine, but
> I have checked the ZA logs.
>
> The only sshd message I can see on the servers is:
> sshd[25934]: [ID 800047 auth.crit] fatal: Timeout before
> authentication for <Win2K ip_addr>
> but this only occurs when a new PuTTY session is attempted while
> previous PuTTY sessions are still in a hung state.
>
> When PuTTY crashes again I should have more information for you.
>
> Thanks
> Bruce

PuTTY still hasn't crashed - but I'm starting to wonder whether it
isn't a network issue, perhaps noise on port 22 (remember no other
network applications are affected). I could try using another port for
SSH. Any thoughts?

Thanks
Bruce

Relevant Pages

  • Re: funky data corruption putty .57
    ... > PuTTY tools at all? ... corruption over putty. ... **This was a rough one, I had two PuTTy sessions on XP, with WinSCP ... throughputs) with Cisco VPN active (has Winscp and putty sessions over ...
    (comp.security.ssh)
  • Re: Unix problems need help
    ... > (powerful, but slow, and it sometimes crashes, while NCSA never ... PuTTY is a SSH client (and perhaps also a telnet client). ...
    (comp.unix.questions)
  • Re: Unix problems need help
    ... > (powerful, but slow, and it sometimes crashes, while NCSA never ... PuTTY is a SSH client (and perhaps also a telnet client). ...
    (comp.unix.misc)
  • Re: PuTTY 0.54 hangs intermittently on Windows 2000
    ... >> simultaneously hang with no error message. ... Once this happens, the PuTTY ... Windows has to be rebooted to run ... But no new PuTTY sessions can be started until ...
    (comp.security.ssh)
  • starting putty from perl!
    ... I want to write a perl script that starts up a bunch of putty sessions. ... I'd have thought running the 'putty system -l user -pw password' should do it but after starting the session, control doesn't return to my script until the putty window closes which makes no sense to me because if I run that same command from a dos window control does return. ...
    (comp.terminals)