Re: Novell Netware, ADSM, and inability to establish a session.
1997-04-29 07:04:08
Subject: |
Re: Novell Netware, ADSM, and inability to establish a session. |
From: |
"Pittson, Timothy ,HiServ/NA" <tpittson AT HIMAIL.HCC DOT COM> |
Date: |
Tue, 29 Apr 1997 07:04:08 -0400 |
Dwight,
When 'logging in' to a Netware server, ADSM requires either a fully
distinguished name
.cn=<adsmid>.ou=aaa.ou=bbb.o=ccc
or a bindery emulation name used in the proper context. So, if the
bindery context is set to
.ou=aaa.ou=bbb.o=ccc
you could just type in the ADSM id.
Tim Pittson
tpittson AT himail.hcc DOT com
>----------
>From: Dwight E. Cook[SMTP:decook AT AMOCO DOT COM]
>Sent: Monday, April 28, 1997 5:52 PM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Novell Netware, ADSM, and inability to establish a session.
>
> Yes, once again I feel "special"...
>
> OK, I have an isolated cluster of Novell Netware 4.1 servers (more
> than 3) The bindery is replicated on the first three of these
> servers. The fourth server has no local bindery or bindery emulation
> via NDS. ADSM can NOT establish a session with this 4th server.
>
> I have not found anything in the manuals that says it is required to
> have a bindery in the environment! (am I just blind?)
>
> and I'll be the first to admit I'M NOT a novell expert...
>
> but naturally since I do administer ADSM I do ( OR SHOULD BY GOD )
> know everything about every client platform (sigh)
>
> anymore I feel lucky if I find the floor getting out of bed in the
> morning ;-)
>
> So as usual I will be forever in debt to anyone who can shed some
> light on this for me.
>
> later
> Dwight
> calling it a day
> Cook
>
>
|
|
|