PuTTY suppress pop-ups.

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View
I'm running putty on a Server 2003 box.  Every now and then putty
loses the connection and creates a pop-up to notify me.
Problem is I need the session putty is providing to run 24/7.  I'm
using Firedaemon to monitor things and keep putty running but while
that pop-up is there, Firedaemon thinks everything is fine.

Is there a way to suppress pop-ups?  Or have putty re-connect when the
connection fails?

Re: PuTTY suppress pop-ups.

Quoted text here. Click to load it

Use CygWin's ssh for now? Or use VNC to keep your terminal sessions
alive? Putty is a wonderful graphical tool, but it's not clear why you
need the 24x7 operation here.

Re: PuTTY suppress pop-ups.

Quoted text here. Click to load it

Auto reconnect in putty is apparently on the wish list and at low

VanDyke's vastly superior SecureCRT product (for which you do have to
pay, but has a free trial) does have auto reconnect, as well as a
tabbed interface, integrated file transfer features, and many other niceties:

However, I suspect you may be interested in knowing about Gnu screen
if you don't already.  Just type "screen" in your ssh session
(assuming it's installed on the ssh server box).  Then, when you
reconnect via ssh after a network hiccup, you can then reconnect to
the virtual tty as you left it when the connection terminated (using
screen -r).  Think of it as VNC for text mode terminal connections.

This way you don't have to be so obsessive about a connected ssh
session being persistent--with screen always running, all you need to
care about it reestablishing an ssh connection if your eyeballs need
to actually see what's going on there.  Screen can maintain the
scrollback and history on the server side and such so you can see what
you missed in whatever you're monitoring on the server.

Using openssh with cygwin as suggested by another poster would be a
useful way around any putty annoyances you have, however, using a
watcher to keep an ssh client awake and alive seems to be the wrong
tool for the ultimate job here.

Site Timeline