Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Drive map failing after switching to IP only.

Status
Not open for further replies.

marder

MIS
Sep 20, 2002
1
US
I am in the process of switching from an IPX/IP network to IP only and I have found a small problem with a drive mapping from the login script. When I login using the IP only client for Win2k I get an error 8804 on a group member drive mapping.

This the script:

write "Good %GREETING_TIME, %LAST_NAME"
write "Your password will expire in %PASSWORD_EXPIRES days"
map root n:=fs01/sys:map root o:=fs01/apps1:map root p:=fs01/apps2:
if member of "CAD" THEN BEGIN
MAP ROOT J:=fs01/design:end

and this is the result:

Your current context is OU.TREE
Your current tree is: TREE
You are attached to server FS01.
Good afternoon, admin
Your password will expire in 32767 days
Drive N: = FS01_SYS: Drive O: = FS01_APPS1: Drive P: = FS01_APPS2: LOGIN-4.21.15-430: The following drive mapping operation could not be completed.
[ROOT J:=FS01_DESIGN:\]
The error code was 8804.


Novell knowledgebase support wasn't much help. Anyone have any ideas?


 
Your problem is that the old map command syntex you have here uses IPX to make the mapping (don't know why, this is another tid bit from NCS). To do pure IP you need to map to the volume object in NDS.

Here is your login script rewritten for volume objects.

write "Good %GREETING_TIME, %LAST_NAME"
write "Your password will expire in %PASSWORD_EXPIRES days"
map root n:=fs01_sys: map root o:=fs01_apps1: map root p:=fs01_apps2:
if member of "CAD" THEN BEGIN
MAP ROOT J:=fs01_design: end


This should work for user in the same context as your FS01 server. If users are not in the same container, be sure to add context to the server volume object. Also verify the volume object name incase it is different than the norm.


Another posiblity (change your mapping to volume object anyway) would be a corrupt volume object in ds. Here is a tid that will help you on that (these are both 10 minute easy fixes).
Brent Schmidt CNE, Network +
Senior Network Engineer

Why do user go into a panic when a NetWare server goes down, but accept it as normal when a Windows server goes down?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top