Long File Name error - but only occasionally

  • Thread starter Thread starter devin.brown
  • Start date Start date
D

devin.brown

I have a user who complains from time to time about getting long file
name errors when copying files to or renaming files on a mapped drive.
The problem will happen and then go away for several weeks and then
come back again.

I am somewhat familiar with long file names and I can tell you that the
entire path (including the filename) is well under 100 characters, let
alone 256. Nobody else on the network is having this problem.

The user is running Windows XP home edition whereas everyone else is
running XP Pro. All service packs and updates are current on all
machines. The server is running SBS 2003 with all current updates and
service packs.

Can anyone help me figure out what could be causing the long file name
issue? Everyone in the office uses files on the same path without any
problems and it's obviously not the number of characters.

Any help is appreciated.
 
I have a user who complains from time to time about getting long file
name errors when copying files to or renaming files on a mapped drive.
The problem will happen and then go away for several weeks and then
come back again.

I am somewhat familiar with long file names and I can tell you that the
entire path (including the filename) is well under 100 characters, let
alone 256. Nobody else on the network is having this problem.

The user is running Windows XP home edition whereas everyone else is
running XP Pro. All service packs and updates are current on all
machines. The server is running SBS 2003 with all current updates and
service packs.

Can anyone help me figure out what could be causing the long file name
issue? Everyone in the office uses files on the same path without any
problems and it's obviously not the number of characters.

Any help is appreciated.
Click to expand...

You need to tell us what exactly this "LFN error is" - when it happens
and what the user sees on the screen.
 
Back
Top