here it is
I assume that NDS can only be seen if the Client is Novell 32 Client. I
have some users at this firm who can not use Novell 32 client as it
conflicts with a Shiva modem share product. I dont have time to find the
work around for that if there is one plus the Shiva is going to be replaced
soon anyway. Anyway I have these users who must use MS Novell client
because of this. My big problem is I have organizational units where I
obviously want to have users for certaing OU's and have the login scripting
etc. I can not login with a user account that is under this OU as the
MSClient is not setup to do this. IS there any way around this or is the
solution to temporarly setup these few accounts so they are under the
organization container - server container not sure if that is the right
termonolgy but I hope you get my drift or is that the way I have to do it.
I will ask the question another way in case the above is confusing.
Can MS Netware client be used to access NDS to see a user who is under an
organizational unit of does the user account have to reside at the root
level?
thanks
joe
<snip>
> Can MS Netware client be used to access NDS to see a user who is under an
> organizational unit of does the user account have to reside at the root
> level?
I think you have two options:
1) Assuming your clients are running Windows 95, install MS Service for NDS
Networks (or words to that effect) on the client PC's; or
2) set one or more bindery contexts on your NetWare server so users can
login in bindery mode. To do this, load SERVMAN and look for the bindery
context settings. Help is provided there.
--
Regards,
Michiel Overweel
michiel_...@nospam.rad.nl (You know what to do)
>I will ask the question another way in case the above is confusing.
>Can MS Netware client be used to access NDS to see a user who is under an
>organizational unit of does the user account have to reside at the root
>level?
You can set the bindery context to up to 16 places. This is assuming
you have a replica there. But since this sounds like a single server
scenerio, I don't think you have anything to worry about. Take a look
at the SYS:SYSTEM\AUTOEXEC.NCF file. You'll see soemthing like:
SET BINDERY CONTEXT=.......
You can add your OU at the end. Your MS client people will not be able
to login. However, they will not utilze the NDS container login script.
You need to cut and paste the container logins cript (Richt Click on the
container, details, login script) to a file called NET$LOG.DAT. Put
this file in SYS:PUBLIC.
You'll need to take out any references to NDS stuff.
*********** Remove the REMOVE if emailing me directly **************
Hansang Bae Director of Network Operations, Eastern Region
Richey Systems Main Office: (800) 776-5145
hb...@richeysystems.com Reg. Office: (718) 352-9021
Specializing in Network Design/Troubleshooting and Protocol Analysis
********************************************************************
thanks
joe
Michiel Overweel <Michiel_...@nospam.rad.nl> wrote in message
news:80k799$fn6$1...@buty.wanadoo.nl...
> Joe K. Bales <joeb...@home.com> wrote in message
> news:mJfX3.146$RM2....@news.rdc1.va.home.com...
> > Setting up a 4.2 Server on Thursday and have a situaition that I am sure
> > many have run into but not myself since most of my installs are NT.
>
> <snip>
>
> > Can MS Netware client be used to access NDS to see a user who is under
an
> > organizational unit of does the user account have to reside at the root
> > level?
>
joe
http://support.microsoft.com/download/support/mslfiles/MSNDS.EXE
This is for Win 95. AFAIK, NDS support for Win 98 is built into the
Microsoft client for NetWare networks.