Networker

Re: [Networker] netware clients on different subnets

2003-06-23 21:02:51
Subject: Re: [Networker] netware clients on different subnets
From: Brendan Sandes <Brendan.Sandes AT DSE.VIC.GOV DOT AU>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
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



loxley99 AT hotmail DOT com
Sent by: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
21/06/2003 01:28 AM
Please respond to
NETWORKER AT LISTMAIL.TEMPLE DOT EDU; Please respond to
loxley99 AT hotmail DOT com


To
NETWORKER AT LISTMAIL.TEMPLE DOT EDU
cc

Subject
Re: [Networker] netware clients on different subnets






Brendan,

First off..  Have these Netware clients "ever" worked on this subnet?, or
is
this a new configuration?
which version of NetWorker software are you using on the Netware clients?
which NetWorker version on the server?
what platform is your backup server?
I am thinking for you to gather that information to share with the rest of
us (including Legato Tech Support). Perhaps there is another NetWorker
user
out there who has this working in a similar kind of environment that you
have, separate subnet and all ... ??

There are several useful diagnostics out there for checking connectivity -
like ping, traceroute, rpcinfo (from Legato); not to mention what various
forms of shareware are out there for this too.
I agree that your network is probably clean, but something in the Legato
software is causing this.

Are you finding anything obscure in the port statistics on this subnet?
Has
anything been changed since the last time this worked (if it ever did)?
Also, what kind of NIC cards are you using in these Netware systems? Are
they standard across the board or is it a mix?

Enough babble from me!   ;)
Good luck compadre!

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: Fri, 20 Jun 2003 12:37:39 +1000
>
>
>Hi All.
>
>Thanks for the suggestions.  I finally got to be able to try this last
>night with one of our netware people..  Unfortunately, it didn't work.  I
>can traceroute to the backup server from the netware client.  I can ping
>the backup server from netware computer, I can ping the netware client
>from the server, and can traceroute to the netware computer from the
>backup server.  There are NT and unix boxes in the same subnet that do
>work with no problems.
>
>I don't believe it is network related at all though.  The client does die
>after giving the error message "cannot find a networker server.  Press
>enter to continue".  I.e. we don't then get the opportunity to go into
the
>client and configure it manually.  The client terminates in the same
>fashion on ALL netware servers that we've tried (about 4) in two
different
>subnets (3 if you count the actual production LAN).  All servers on the
>production LAN work.  Any of our netware computer in other subnets that
>we've tried do not.  Both of the two different subnets that we've tried
>are connected to the production network via a 1GB connection so it's
>
>Has anyone got any debugging suggestions as to why the legato client on
>netware dies?  I cannot find any documentation on the netware client at
>all even after literally hours of searching on the internet and a couple
>of queries to the archives of this list.
>
>Cheers!
>Brendan
>
>
>
>julian.waltham AT ekht.nhs DOT uk
>Sent by: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
>16/06/2003 08:24 PM
>Please respond to
>julian.waltham AT ekht.nhs DOT uk
>
>
>To
>NETWORKER AT LISTMAIL.TEMPLE DOT EDU
>cc
>
>Subject
>Re: [Networker] netware clients on different subnets
>
>
>
>
>
>
>as long as your hosts file or resolv.cfg are setup to resolve the ip
>addr of the networker hostname then you can edit the networkr.ncf and
>add on the end of the line reading load networkr
>-s <my-networker-server-name>
>eg
>load networkr -s networker1
>or
>load networkr -s networker1.somedomain.com
>
>julian waltham
>east kent hospitals nhs trust
>
>On Mon, 2003-06-16 at 10:49, Brendan Sandes wrote:
> > Hi all again.
> >
> > A quick question:
> >
> > We have some of our netware clients on different subnets
> > I checked with our networking people
> > The only thing that is blocked between the subnets is broadcasts
(which
>is
> > how it should be)
> >
> > However, any of our netware clients on different subnets show this
> > behaviour.
> > we start the client
> > it waits for a time
> > comes up with the followin message
> > "cannot find a networker server.  Press enter to continue"
> > At this point the client dies.  We do not get the opportunity to
>configure
> > it manually, it terminates immediately
> >
> > The netware team assure me that all of the servers are set up the same
>(in
> > this case I tend to believe them) with a standard build
> >
> > I can backup NT servers or UNIX servers in the same subnet
> >
> > There is, of course, no usefull documentation on the netware legato
>client
> > that I can find on the internet anywhere.  Even google failed me this
> > time.
> >
> > Any suggestions?
> >
> > Cheers!
> > Brendan
> >
> > --
>
>**********************************************************************

_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=