troysnf
asked on
8804 errors in Netware Login Script
I have a single server running netware 5. There are no ou's under the organisation. All users and the server object itself sit directly under the organisation container. I have created an ou called users below the organisation. I have copied the login script for the organisation and put it into the new container. I have also moved one test user into the new OU and attempted to login. I receive many 8804 errors when the script is attempting the drive mappings so I have stripped back the users container script to just attempt a single drive mapping, which is
NO_DEFAULT
MAP root F:=ANF_SERVER_DATA:\
I then receive the output from the login script
Your current context is ANF
User: Ben Context: Users.ANF
Your current tree is: ANF
You are attached to server ANF_SERVER.
LOGIN-4.22.00-430: The following drive mapping operation could not be completed.
[ROOT F:=ANF_SERVER_DATA:\]
The error code was 8804.
The only thing which has come close is an article I found on the organisation name being the same as the server name. While close 0=anf , and cn=anf_server , I would not think that should matter.
Having said that there is quite possibly just something stupid that I have missed here. Any help would be appreciated.
NO_DEFAULT
MAP root F:=ANF_SERVER_DATA:\
I then receive the output from the login script
Your current context is ANF
User: Ben Context: Users.ANF
Your current tree is: ANF
You are attached to server ANF_SERVER.
LOGIN-4.22.00-430: The following drive mapping operation could not be completed.
[ROOT F:=ANF_SERVER_DATA:\]
The error code was 8804.
The only thing which has come close is an article I found on the organisation name being the same as the server name. While close 0=anf , and cn=anf_server , I would not think that should matter.
Having said that there is quite possibly just something stupid that I have missed here. Any help would be appreciated.
Also, is the DATA the name of the volume? If so, there's no reason to use the MAP ROOT command for that. You can simply use the MAP command instead, and leave ROOT out of it - it's not necessary.
At any rate, I'd recommend cleaning up the way you write your script if that's the kind of syntaxing you are using.
At any rate, I'd recommend cleaning up the way you write your script if that's the kind of syntaxing you are using.
ASKER
The system has been running in its current configuration for the last 6 years. The only change made was to add the ou called users, copy the script from the organisation script and move a user into it. There is a single server and the name of the volume is data. Have also tried not using map root , but it has the same result.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Brilliant, thanks Ghost. Referencing in full context has done the trick
There's quite a few causes for an 8804 error so more details may be help.
Personally I try to map via "NDS" names instead of short DNS names or IP's...Take this, as an example:
MAP ROOT R:=.MIDDLES1_VOL1.Middle.H
So if you did something like that, it would help if your syntax was wrong, but did it ever work?