Solved

Shortcut targets in Win2K/Citrix interpreted as 8.3 - how to fix?

Posted on 2004-08-18
6
458 Views
Last Modified: 2011-09-20
There are file shortcuts that have been created in a server-based directory, that point to files on another server, so these specific files can be accessed by limited-access users.  These shortcuts were created using WinXP Pro.  

The shortcuts work fine from any WinXP workstation, but when accessed from a Win2K Citrix Metaframe session, they do not work.  Looking at properties of the shortcuts show that the paths and filenames are "long" - more than 8 char. to directories in path, more than 3 char. file extensions.  When you look at the shortcut properties from a Win2K Citrix session - the exact same shortcuts in the exact same network folder - the paths and filenames have been converted to 8.3 format.

This is not an issue with the NTFS registry entry for creating 8.3 filenames. I can't find any policy settings that have anything to do with this.  It has to be some other issue, but I can't find any tech docs that address this.   Does anyone have any ideas for me?  I have no compunctions against registry editing - I've been doing it for years.

TIA.
0
Comment
Question by:ShineOn
6 Comments
 
LVL 9

Expert Comment

by:BigC666
ID: 11833054
howdy,

be sure to backup your registry first

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\FileSystem]
Value Name: Win31FileSystem
Data Type: REG_DWORD (DWORD Value)
Value Data: (0 = long file names, 1 = 8.3 filenames)

hope that this helps
0
 
LVL 35

Author Comment

by:ShineOn
ID: 11834647
Unless that makes Win2K interpret long file names not stored on NTFS as 8.3 without physically changing the link target to 8.3, while WinXP does not make that same interpretation using the same setting, that's not it.  That setting is the same on both the Win2K/Citrix server and on the WinXP workstations.  Besides, the docs for that value that I've seen say it only affects creation of new files in your NTFS filesystem, and if set to 1, long filenames aren't supported.  Nothing about changing how existing shortcut links are read.

These values for that reg key are identical in the WinXP systems and in the Win2K/Citrix system:

NtfsDisable8dot3NameCreation (set to 0, the default)
Win31FileSystem (Set to 0, the default)
Win95TruncatedExtensions  (set to 1, the default)

I have also made the registry hack that is supposed to stop automatic link updates, just in case it's reinterpreting the target because of that.  No go.

To illustrate the issue. this is a representative example of the problem:

The .lnk file's target field is: R:\DETAILS\4416\441628.SLDDRW
The .lnk file's target field is interpreted on Win2K/Citrix as: R:\DETAILS\4416\441628~1.SLD but is not actually changed to that.

Before anyone suggests it, according to what I've found, Win95TruncatedExtensions only affects command-line utilities like DEL and COPY, and only "truncates" the extension when doing wildcard actions, i.e. "DEL *.HTM" will get both 1.HTM and 2.HTML, and it's not supposed to affect things like Explorer.  This is showing an 8.3 name for the "long" filename 441628.SLDDRW.

The only thing that comes close, that I can see, is if you have Mac compatibility services running and you open something that was named by a Mac system, it should read the file name using 8.3 notation.  I don't have Mac compatibility enabled.  That doesn't mean it never has been - this is an inherited system with no change log.
0
 
LVL 35

Author Comment

by:ShineOn
ID: 11834685
This server is Win2K SP3, in case anyone asks.  I'm wondering if there's an obscure bug that gets fixed in SP4.  Hard to say, because even the fixes for bugs that aren't so obscure aren't easy to find documentation for...
0
How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

 
LVL 10

Expert Comment

by:DSPoole
ID: 11835238
I'd get it up to SP4 before worrying about anything else.
0
 
LVL 35

Author Comment

by:ShineOn
ID: 11846369
Did some digging - it appears that it's a problem with WinXP that Microsoft hasn't addressed yet.  If you create a shortcut on a non-NTFS device that support s LONG names (like a NetWare server, for instance) using WinXP Pro, it appears to ALL Windows versions in 8.3 format EXCEPT on WinXP.  The shortcut looks and works fine on WinXP but not on Win2K.
0
 
LVL 1

Accepted Solution

by:
GhostMod earned 0 total points
ID: 11948764
PAQd with 500 points refunded - the asker posted their solution

GhostMod
CS Moderator
0

Featured Post

What Is Threat Intelligence?

Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

Join & Write a Comment

NTFS file system has been developed by Microsoft that is widely used by Windows NT operating system and its advanced versions. It is the mostly used over FAT file system as it provides superior features like reliability, security, storage, efficienc…
A procedure for exporting installed hotfix details of remote computers using powershell
This video discusses moving either the default database or any database to a new volume.
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now