Brendan,
My immediate question to you is if your usage of NetWorker Client for
Netware 4.21 is a new implementation of this software?
I remember when NetWorker 6 very first came out, there was an issue where
Novell clients could not be backed up if the NetWorker server was a
Microsoft box (NT or Win2K). Granted, this was with NetWorker for Netware
Client 4.15, but what the heck?
I am sure you have contacted Legato Tech Support about this problem you are
having. But have you asked them to inquire about someone else using Netware
4.21 clients on a different subnet and getting them to work?
Likewise, is there any chance you could try out a client of NetWorker 4.15
and see if it works for you on another subnet?
I am tapped out here, as I am not in a Novell environment anymore.
Good luck with this!
Tom
-----
From: Brendan Sandes <Brendan.Sandes AT DSE.VIC.GOV DOT AU>
Reply-To: Legato NetWorker discussion <NETWORKER AT LISTMAIL.TEMPLE DOT EDU>,
Brendan.Sandes AT DSE.VIC.GOV DOT AU
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] netware clients on different subnets
Date: Tue, 24 Jun 2003 11:03:31 +1000
Unfortunately, we are implementing a new solution so no, they've never
worked on this subnet. The only netware computers that they've worked on
are the ones on the subnet local the the backup server and they're
relatively new installations as well.
Networker Server: SUN E450 quad 450Mhz running solaris 2.8 (latest
cluster patch as or about may)
Backup Server: Version: Solstice Backup 6.1.3.Build.428 Network
Edition/80
Backup Client Version: 4.21. Netware version (both netware6 and netware
4 - Mostly 6)
So far, what we've tried is this
checked that the netware box has the SYS:NETWOKR.INI file. Also changed
the servername to the fully qualified domain name (as per Joaquin Camp's
suggestion)
Then as per sejca's suggeston, tried the following which all came backup
positive
ping server from client and client from server (both names and IP
addresses) - all happy
traceroute from server to client and client to server (also both names and
IP addresses) - all happy
Also tried putting the networker server into the hosts file on the netware
client (no joy - client still crashes)
Have to get the netware guys to check out the rpcnet file as per Tom
Pecock's suggestion.
I still cannot see why though, being on a different subnet causes the
client to flat out crash. This doesn't make any sense to me at all.
Surely the client should still stay running so I should be able to
configure it manually. I still cannot find anything except basic stuff
for troubleshooting why the client dies on either Legato's web site or
through google. The thing is, from what I understand, even if it can't
find a networker server at all, the client still shouldn't die like it
does. Shouldn't it go into the client and await further instructions?
Cheers!
Brendan
_________________________________________________________________
The new MSN 8: advanced junk mail protection and 2 months FREE*
http://join.msn.com/?page=features/junkmail
--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
