(sorry for a long post, wanted to include any relevant details)
Synapsis of the problem:
Local Group Policy settings hindering using and viewing Novell mapped drives in Explorer (but they are still visible in other programs, like Word XP). Also, error with allowable file name length of Novell mapped drives.
The Environment:
P3 996Mhz Dell (generic Dimension setup), XP Pro SP1, Netware 5.1 server, Novell 4.86 32 bit client, Local Group Policy (gpedit.msc), all drive mappings done via server-side login script
I am trying to lock down a lab machine model for ghosting, and have hit a snag with the Group Policy hindering Novell drives. I have double-checked, and the all the options dealing with hiding drives of any kind are disabled in the Policy. All options dealing with the timing and handling of scripts in the Group Policy are set to 'not configured' in both machine and user sections.
Here's the deal...
If I log on to the machine using the standard Novell NDS login, then locally with an account with 'User' rights, all is well, no problems with mapped drives or file names.
BUT...If I do a 'workstation only' login to the local machine using either the same account with 'User' rights, or 'Administrator', THEN login to Novell from the desktop using the same 32 bit Novel client and server-side scripts, none of my mapped drives appear in Explorer. Oddly enough, the drive letter assignment works...you can type f: in the address bar and it goes to the correct mapped drive.
So I type f: and get to one of my mapped drives...at this point, if I try to create or move any files to the mapped drive, I get an error that says the drive 'does not support long file names' (as in 'New - Folder' gets you a dir called 'fldr' that cannot be changed to anything longer than 7 characters) Again, this doesn't happen unless you login using 'workstation only' first, then the Novell client login at the desktop, and it does not affect the local drives
This is a (locked down)lab machine I am setting up, and I know it is a problem in the Group Policy, because I also have a secondary account set up on there as an Admin that has no read rights to the Group Policy folder (using NTFS file permissions)...therefore, if you login using that account, since you have no read rights to the group policy, XP operates unhindered by the group policy settings. This works great, but if you try it, I suggest being cautious and doing this with a secondary account with Admin rights, not the "Administrator" account...you could lose the ability to edit the policy otherwise.
Anyway, I can logon to 'workstation only' as this secondary (unhindered by the policy) account, then logon to Novell from the desktop using the 32 bit client and it works as it should. Mapped drives are added and are visible in Explorer with no problems with file names.
That's why I say it is a policy setting. I have went through the local policy (gpedit.msc)settings 4 times one by one, but I do not see what could be causing this. (again, the 'hide drives' policy options are disabled)
Anyone know how to fix it, or have any suggestions please?
Thanks in advance...
Synapsis of the problem:
Local Group Policy settings hindering using and viewing Novell mapped drives in Explorer (but they are still visible in other programs, like Word XP). Also, error with allowable file name length of Novell mapped drives.
The Environment:
P3 996Mhz Dell (generic Dimension setup), XP Pro SP1, Netware 5.1 server, Novell 4.86 32 bit client, Local Group Policy (gpedit.msc), all drive mappings done via server-side login script
I am trying to lock down a lab machine model for ghosting, and have hit a snag with the Group Policy hindering Novell drives. I have double-checked, and the all the options dealing with hiding drives of any kind are disabled in the Policy. All options dealing with the timing and handling of scripts in the Group Policy are set to 'not configured' in both machine and user sections.
Here's the deal...
If I log on to the machine using the standard Novell NDS login, then locally with an account with 'User' rights, all is well, no problems with mapped drives or file names.
BUT...If I do a 'workstation only' login to the local machine using either the same account with 'User' rights, or 'Administrator', THEN login to Novell from the desktop using the same 32 bit Novel client and server-side scripts, none of my mapped drives appear in Explorer. Oddly enough, the drive letter assignment works...you can type f: in the address bar and it goes to the correct mapped drive.
So I type f: and get to one of my mapped drives...at this point, if I try to create or move any files to the mapped drive, I get an error that says the drive 'does not support long file names' (as in 'New - Folder' gets you a dir called 'fldr' that cannot be changed to anything longer than 7 characters) Again, this doesn't happen unless you login using 'workstation only' first, then the Novell client login at the desktop, and it does not affect the local drives
This is a (locked down)lab machine I am setting up, and I know it is a problem in the Group Policy, because I also have a secondary account set up on there as an Admin that has no read rights to the Group Policy folder (using NTFS file permissions)...therefore, if you login using that account, since you have no read rights to the group policy, XP operates unhindered by the group policy settings. This works great, but if you try it, I suggest being cautious and doing this with a secondary account with Admin rights, not the "Administrator" account...you could lose the ability to edit the policy otherwise.
Anyway, I can logon to 'workstation only' as this secondary (unhindered by the policy) account, then logon to Novell from the desktop using the 32 bit client and it works as it should. Mapped drives are added and are visible in Explorer with no problems with file names.
That's why I say it is a policy setting. I have went through the local policy (gpedit.msc)settings 4 times one by one, but I do not see what could be causing this. (again, the 'hide drives' policy options are disabled)
Anyone know how to fix it, or have any suggestions please?
Thanks in advance...