CharlesH
asked on
Novell 6 search drive overwrites AD mapped drive when connected to wireless
We are slowly slowly moving things off of an ancient Novell 6.0 (05) server and on to Windows.
We have mapped a shared drive Z: (not my choice) to the windows share where we are moving the files and folders that were once on Novell.
We are mapping this drive through Group Policy (2008) and all is well unless a user connects to the wireless network, which does not allow you to authenticate to Novell upon login, then manually logs in to Novell.
When that happens, the first Novell search drive overwrites the link to Z: and adds its own path.
Oddly, the description of the Z: mapping remains the same "Server_name Shared (Z:)"
Is there any way to block Novell from mapping the first search drive to Z:?
the clients are mostly windows 7.
No, we cannot just move everything at once. there is a clean up process that is occurring concurrently.
We have mapped a shared drive Z: (not my choice) to the windows share where we are moving the files and folders that were once on Novell.
We are mapping this drive through Group Policy (2008) and all is well unless a user connects to the wireless network, which does not allow you to authenticate to Novell upon login, then manually logs in to Novell.
When that happens, the first Novell search drive overwrites the link to Z: and adds its own path.
Oddly, the description of the Z: mapping remains the same "Server_name Shared (Z:)"
Is there any way to block Novell from mapping the first search drive to Z:?
the clients are mostly windows 7.
No, we cannot just move everything at once. there is a clean up process that is occurring concurrently.
Have you thought about just modifying the Novell login script?
ASKER
Yes. but what do I do to block Z: from mapping via S16?
Post you login script for Netware.
ASKER
The problem comes from here:
Z: is getting pointed at \sys:\public.
MAP INS S16:=server_name\SYS:\PUBLIC
MAP INS S16:=server_name\VOL1:
the rest of the script is a mess and is mostly remarked out.
Z: is getting pointed at \sys:\public.
MAP INS S16:=server_name\SYS:\PUBLIC
MAP INS S16:=server_name\VOL1:
the rest of the script is a mess and is mostly remarked out.
ASKER
If I change these mappings to:
MAP INS S15:=server_name\SYS:\PUBL IC
MAP INS S14:=server_name\VOL1:
will it map to Y and X instead of Z and Y?
I can't really experiment with a production system
MAP INS S15:=server_name\SYS:\PUBL
MAP INS S14:=server_name\VOL1:
will it map to Y and X instead of Z and Y?
I can't really experiment with a production system
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Wait, why would I map a search drive to a letter? Wouldn't I just map the letter by itself?
E.g. MAP X:=server_name\SYS:\PUBLIC
or perhaps MAP ROOT X:=server_name\SYS:\PUBLIC (Which seems to be what has been done in the other static maps.)
It has been years since I was a Novell guy and most of that was 3.2. and 4.11.
E.g. MAP X:=server_name\SYS:\PUBLIC
or perhaps MAP ROOT X:=server_name\SYS:\PUBLIC
It has been years since I was a Novell guy and most of that was 3.2. and 4.11.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Points!
That makes sense. Thanks for your help.
Oh and I just noticed that my Novell utilities are pointing at \sys\public so I think I will map that as a search drive.
That makes sense. Thanks for your help.
Oh and I just noticed that my Novell utilities are pointing at \sys\public so I think I will map that as a search drive.