Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

My setup: Windows 7 Pro (locale: Polish) and a NAS drive (D-Link DNS-323) attached via a router. Just recently upgraded from XP to 7. The NAS drive reports an NTFS partition.

The problem I've just discovered: when copying files to the NAS drive, if a filename contains certain characters, such as curly quotes, angle quotes, bullet characters, subscript characters, em-dash etc., only the short 8.3 filename gets copied to the NAS drive. So a file named Abc „def” – ghi « jklm.htm on the Win7 system becomes Abcde~6h.HTM on the NAS drive.

(I would not sweat it if the troublesome characters just got dropped, but what happens is that meaningful filenames are replaced with gibberish as above.)

I use the NAS drive as a backup/mirror location for the local drives, so this is a big issue, since my backups are now severely clobbered. I discovered the problem while testing my backup regime, then found out the filename change occurs no matter how the files are copied - whether it's the backup application, a file manager or just Windows Explorer.

And (of course) the problem did not occur when I was running XP, and nothing on the NAS drive changed since I installed 7 a week ago. Files that were previously copied onto the NAS drive (under XP) still show up fine, which tells me that 7 is actively interfering with the copy operations.

Does anyone know why this happens or if there is a workaround? Thanks a lot in advance for any suggestions.

share|improve this question
up vote 1 down vote accepted

Updating the firmware in the NAS device and reformatting it seems to have solved the problem.

I would still love to know exactly what Win7 does with respect to the NAS drive handling, since I the problem was not present under XP SP3, which I was previously using, so the OS must be affecting it in some way.

share|improve this answer
1  
I would guess that the SMB updates in Windows 7 changed some things, maybe the NAS wasn't seen as able to handle long filenames. Glad to know that you were able to fix your own problem though. – Alan Pearce Aug 26 '10 at 20:39
1  
The NAS was probably running a buggy version of SAMBA. Corrupted FAT32 long filenames might result, and then, you would have the 8.3 original FAT filenames, but not any valid long filenames. Such a problem seems likely to have caused other corruption too, I'd be wary of that NAS vendor. – Warren P Dec 18 '11 at 21:42

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .