:2e_ and .AppleDouble files

[19FdSc69]

When Time Machine tries to backup files I've downloaded from the web onto our recentlly purchased GNAP network server, Time Machine issues a warning of ".....file which has an unsupported filename!". The filename is being amended with the additional characters of ":2e_" and/or ".AppleDouble/:2e_" at the front of the filename. As a result, Time Machine won't buckup thoses files. What's happening?

If this has any bearing on it, my Connect To Server Address begins with "afp" and my File Sharing has "Share files and folders using FTP" checked.

I'm using Snow Leopard v10.6.8 on a Mac Pro.

 

[wrldwzrd89]

When Time Machine tries to backup files I've downloaded from the web onto our recentlly purchased GNAP network server, Time Machine issues a warning of ".....file which has an unsupported filename!". The filename is being amended with the additional characters of ":2e_" and/or ".AppleDouble/:2e_" at the front of the filename. As a result, Time Machine won't buckup thoses files. What's happening?

If this has any bearing on it, my Connect To Server Address begins with "afp" and my File Sharing has "Share files and folders using FTP" checked.

I'm using Snow Leopard v10.6.8 on a Mac Pro.

Wow... that's odd, that shouldn't even be possible as Mac OS X normally forbids the colon character in file names. Are you by any chance downloading archives in the old AppleDouble format? That format is REALLY old... dating back to the 68k Mac days.

Also worth investigating is this: Is your downloads folder located on a disk (networked or external, doesn't really matter) that isn't in the HFS format? Failing that, if you move the files after download to such a folder, that matters too. You see, non-HFS file systems don't support resource forks - this leads to problems if you attempt to decompress a Mac-specific archive on such a file system. The recommended workaround is to decompress locally, THEN move/copy the contents.