Title: OT: VERY STRANGE ISSUE - Windows 95 and Long File Names

Oh,

 

And to add those finest little details:

 

Same users, same documents on Windows 98.. no problem.

 

Open a document with a long file name in the corresponding application, and ‘save as’ under another long name.. no problem either.

 

Yeah, time for more beer..

 

Regards,

 

Paul

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jorge de Almeida Pinto
Sent: Friday, February 25, 2005 7:04 PM
To: [email protected]
Subject: [ActiveDir] OT: VERY STRANGE ISSUE - Windows 95 and Long File Names

 

Hi,

During our Novell/NT4 to W2K3 migration we are experiencing a very very strange issue that we until now have not been able to solve.

The situation is:
* Homedirectory data was stored on Novell en users had a H-mapping to it
* Homedirectory data has been migrated to Windows
* Netlogon loginscript has been implemented in NT4 domain (clients/users are still in NT4 domain) and each user in NT4 has it loginscript attribute with LOGON.BAT

* The Netlogon loginscript makes a H-mapping for a user to its homedirectory on the windows file server
* The Netlogon loginscript makes a other mappings for a user to other locations on the windows file server

The issue:
* Users can create documents with WORD on H (new document in word and save in H) with long file names
* Users can create documents with WORD on other drives (new document in word and save in H) with long file names
* Users can rename documents in Explorer on other drives with long file names (document with some LFN gets another LFN)

The problem:
* SOME Users (NOT ALL)  CANNOT rename documents in Explorer on H-mapping with long file names (document with some LFN gets another LFN is not possible!) It only accepts 8.3 names!!!

The VERY STRANGE ISSUES:
* If we change the H-mapping for the home directory to some other mapping (lets say T:) then the problem does not occur --> ?????

* If we in the command prompt type "NET USE H: /DELETE" and after that "NET USE H: /HOME" (delete the H-mapping and create it again) the problem does not occur --> ?????

WTF is this???!!! I have tried everything, at least I think I have, and it's making me nuts.
Has any of you guys experienced this or do any of you what this is and/or how to solve this?

The workaround we have until now is that we've sent those users a batch file that recreates the H-mapping, but I would like to solve this by making it work in the loginscript

I'm going to get a beer and play some darts
Hope you guys can help. Thanks in advance....  Have a nice weekend!

Regards,
Jorge


This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

Reply via email to