NetWorker Admin slow to connect (<server>: Cancelled)

[wmg]

We are running Legato NetWorker 6.0.2 on an Windows NT 4 erver (Dual PIII 933, 1Gb RAM, Raid5 etc). Lately, it has been taking longer and longer to connect to the server using the NetWorker Administrator program - even if run on the box itself (which seems to rule out network problems).

I have checked the NIC settings - they're 100/full, we've stopped and started the services (around 183 clients and takes less than a minute to stop/start the services). I have performed nsrck -L 6. The CPUs are almost completely idle, there's heaps of RAM free and there does not appear to be any packet loss due to network errors.

Has anybody had a situation like this before? Does anybody know how to slow my imminent hair-loss?

Thanks

 

[rgzimmer]

My was bad at first after upgrading from 5.7 to 6.1, but has since come down to a resonable time frame. Wish I could tell you why it got better.

 

[wmg]

Thanks rgzimmer - it's good to know others have had a similar experience at least!

Some more information though, all other parts of the Legato server are functioning as expected. Scheduled backups are running, tapes mounting from 100 slot changer automatically etc etc.

One thing we tried this morning (which seemed like a long shot - but seems to have worked!) was to remove all the specifically listed admins from the server set up. Now, instead of about five or six entries, there are just the following two:

administrator@<server>.<fqdn>
*@*

Now starting the administrator program is a snap - it starts quickly and responds fairly quickly to requests for information, logs, starting save sets etc etc.

Weird huh?

 

[rgzimmer]

You should remove the *@*. It gives literally ANYONE with Networker installed full access to your server. A better method, though still far from secure, would be to use (Administrator's name)@* so that you can access it from wherever you need to.

 

[wmg]

Yes - we did have that but it seemed to be causing problems - though I think (from some other information we've found) that that was just coincidental.

The problem appears to be related to reverse lookups in the DNS for the Legato admin workstations - if they are not there or are wrong then it makes everything run slowly.