[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ngw
Subject:    RE: GW 4.1 network ID not found problem
From:       "Philip Catelinet" <PCatelinet () proskauer ! com>
Date:       2000-05-12 20:17:53
Message-ID: s91c2ebf.032 () proskauer ! com
[Download RAW message or body]

Every server has bindery context enabled.  You wouldn't believe how bad our NDS tree \
looks.  You know how you're supposed to partition the tree?  All our users (1700+) \
are in one context, so we have no partitions and too many replicas.  It's great fun.

> > > "Laurie Baker" <BakerLJ@dhfs.state.wi.us> 5/12/00 3:51 PM >>>
You may need to set bindery context for their containers on their servers, I remember \
having to do that when we were at 4.1a.  There were also some switches we had to use \
since 4.1a isn't really NDS aware, I don't remember exactly how they went but we had \
to put in the fully distinguished name as a startup switch.  It might have been \
/la-username.ou.ou.o or something like that.  I pitched all my 4.1a docs, so don't \
have that info anymore.  I just remember it was a real pain until we got everyone \
over to 5.x.

> > > PCatelinet@proskauer.com 05/12/00 02:38PM >>>
In our environment, the network ID is already the common name, without the context.  \
Since we are a mixed 5.5/4.1 shop, we're managing everything thru NWadmin, and \
there's no way that I know of to change the network ID for the user.  Do you know of \
a way to do that?  That might help us out in trying to track down the problem.

Phil


> > > "Doug Miller" <domiller@ma.ultranet.com> 5/12/00 3:24 PM >>>
Phil,

Does the network ID for the users with the problem have the full NDS
context?  If it does, try removing it.  If it does not, try adding it.

In my experience, those using the MS client do not need to have the context
set, while users with the Novell client 32 do need to have full context set
in the network id.

I hope this helps.  Alas, we are still using 4.1a, so I don't need to
remember anything.

- Doug Miller



> -----Original Message-----
> From: ngw@lists.dotone.com [mailto:ngw@lists.dotone.com]On Behalf Of
> Philip Catelinet
> Sent: Friday, May 12, 2000 2:10 PM
> To: Multiple recipients of list NGW
> Subject: GW 4.1 network ID not found problem
> 
> 
> We have many users calling in with the error D101 Network ID not
> found.  These users are logging in with MS Client for NetWare in
> bindery mode.  Notify comes up with the correct user ID and beeps
> to let them know they have mail.  But when they try to start GW,
> they get the error.  To fix this, I've been running a
> synchronization process from NWAdmin which seems to alleviate the error.
> What I'd like to know is what's causing this.  Our network staff
> has been adding users to an NT domain via the NDS for NT snap-ins
> and that seems to be at the root of the problem, but I'm trying
> to understand what this might have to do with GroupWise 4.1 and
> network ID.  Does anyone remember back to the 4.1 days and what
> can cause the network ID not found error?  Obviously Novell's web
> site is thin on this matter, and calling them is of no use since
> 4.1 isn't supported anymore.
> 
> Thanks,
> Phil
> 
> 
> 


[prev in list] [next in list] [prev in thread] [next in thread]