Les Yaw wrote:

Hi Stan,

First off - in our opinion, Tech Support from Cyclades bites a big one when
you're attempting to get it set up. More than once I was told by their tech
support staff to "keep fiddling with the settings... you'll eventually get
it to work."  Once I did strike up the correct config, it's been flawless.

If you're maintaining a network between the remote location where your
NetWorker server will be, and where your office is at, consider VNC, if
applicable.

We use VNC to give us remote control of servers and work stations away from
our offices.  I'm not sure if there's a VNC product for your OS - but
they're free.  We configure ours with password protection to shield it from
unwanted access.

There is a bit of screen latency.  However, I use VNC on a Citrix client
with only minor discomfort.

That's my two-cents worth, and after buying Christmas presents, this is all
I can afford to share with you right now.

I don't think VNC is what he needs. Although VNC is a superb product
(even better on Unix than on Windows), it's not the right fit here. A
Unix server already has lots of ways of accessing remotely, in a much
more flexible way than Windows, but what is needed is access to the low
level stuff that goes on when the Unix server is booting. It needs to be
accessible even when the system is down. A serial terminal server fits
the bill perfectly, but that's what Stan was asking for anyway.

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=