Shared folders randomly inaccessbile

Hi All,

I have a user (Windows XP Pro, SP3) who is periodically having trouble accessing file shares on our Windows 2008 R2 server.  One minute he'll be able to open them all just fine only to find that when he tries again later, he can open all but maybe 1 share.  The error he gets is the one that's like "\\fileshare is not accessible.  You may not have permissions to access this folder.  Please check your permissions or contact your systems administrator...."

I've checked his permissions and he has full permissions to access all shares.  The weird thing is that this issue only happens half the time.  One thing:  the user is leaving the office and working from home, accessing the shares via VPN connection.  Again, same problem;  half the time he'll be able to open all the shares just fine through VPN, while the other half the time he'll be able to open all but 1.  That 1 changes for no apparent reason.  Sometimes it's shared folder A, sometimes it's shared folder rhyme or reason to it.

I've checked his event logs and the only error I see at the time he last tried to access a share and was unsuccessful was this one:

Error      4/18/2011      9:12:00 AM      Dhcp      None      1002      N/A      D9CGJTF1

Does anyone know what could be up?

Who is Participating?
rkenersonConnect With a Mentor Author Commented:
Just added the user to the domain and the problem cleared.  Accepting own solution.
I don't know if this applies, however, years ago I was told by an anti-virus vendor that the problem you are describing and one like my client had had was because of an anti-virus setting that was set on both the server and the workstation.  The setting was to scan files accessed and opened either locally or from a network share.  There were two antivirus programs locking the networked files so that the user could not read or write.

Another scenerio, years ago had shares disappear and reappear.  That was a result of a "faulty" combination of GPO settings.  After hours on the phone with Microsoft, a Microsoft patch became availble that fixed that problem.

Just a couple of thoughts...
rkenersonAuthor Commented:
Canon - Thanks for your comment.  I think we can rule out the Anti-Virus settings because a) nothing has changed; b) we would notice this issue with other users, most likely.  The problem only seems to be affecting 2 users, and it turns out they are brothers (so very similar names).   In fact, I checked the Event Logs on the server last night and found this error recorded around the time of the last incident:

Error      4/18/2011 9:50:53 AM      NetBT      4319      None
A duplicate name has been detected on the TCP network.  The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.

When I use nbtstat -n, I don't get anything helpful (I think because it's after the fact...)  but I really suspect this has to do with naming conflicts considering the affected parties are 2 brothers with similar AD names....
rkenersonAuthor Commented:
I figured it out on my own.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.