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



**********************************************************************
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
Any views or opinions presented are solely those of the author and do
not necessarily represent those of East Kent Hospitals NHS Trust.  If
you are not the intended recipient, be advised that you have received
this email in error and that any use, dissemination, forwarding, printing
or copying of this email is strictly prohibited.

If you have received this email in error please notify the system
manager at the following email address: root.postmaster AT ekht.nhs DOT uk

www.kentandmedway.nhs.uk

This footnote also confirms that although this email message has been
swept by MIMEsweeper for the presence of computer viruses, it is strongly
recommended that you carry out your own virus scan of this
message and any attachments.

www.mimesweeper.com
**********************************************************************

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