Unable to access file share

Hello,

We are having an interesting issue with one of our file shares.  On occasion while we are working we suddenly use access to our shared drive (personal drive) that is mapped from our user account.  This happens at random times throughout the day and does not seem to hold to any particular pattern.  You can see some images below.

We have our user accounts set to map a drive to a file server and to call that drive U: - We have setup Group Policy to redirect My Documents and the Desktop to this drive.  Due to legacy reasons users were previously informed to copy all of their critical documents to their U: drive manually but that is no longer the case as their My Docs and Desktop are done automatically.

When the access to the documents stops working it is only to the documents that are NOT stored in My Documents or in the Desktop folder.  This is happening only to the documents that were manually copied over to the U: drive. I have checked all of the logs on the client and the server and I do not see any messages that relate to this issue.

You can see from the picture below that we are finding little Xs on the documents.  When you try to open the documents you get a message This file is currently not available for use on this computer. (as seen below).

I have also included a picture of the user profile  screen. I have used a red marker to take out identifying system and user information.
If anyone has any ideas I could use some help.

Thanks,

Matt
LVL 4
brownmattcAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

brownmattcAuthor Commented:
Image 1
0
brownmattcAuthor Commented:
For some reason this site is not allowing me to attach right now...
0
brownmattcAuthor Commented:
0
Powerful Yet Easy-to-Use Network Monitoring

Identify excessive bandwidth utilization or unexpected application traffic with SolarWinds Bandwidth Analyzer Pack.

ChiefITCommented:
Are these DFS shares for a Namespace or just a mapped drive to a shared file?
0
ChiefITCommented:
Never mind, I already know the answer to that. They are DFS shares.

When setting up the namespace, you are told to pick the SHARE permission. The default setting is read only. So, the ONLY person that will have DELETE, READ and EXECUTE of that file is the OWNER/CREATOR of the file. That means if Joe.blow created the xcell spread sheet and saved it in HIS documents, he has total access to it, however, noone else will.

The way permissions works is this.
You have the share permissions and the NTFS permissions of a DFS share, (or DFSR share). It's the same with every share. It takes the most restrictive of the two permission sets, (NTFS and Share). So, if the SHARE permission is read only, unless you are the owner/creator of the file, others can not read this file deleted it or manipulate it. The creator owner will probably not be able to delete it, but will be able to read or execute the file.
0
brownmattcAuthor Commented:
Hello ChiefIT,
I am sorry but this is a simple mapped drive as shown in the User Profile portion of the picture.  At random points in the day the access to folders in the mapped drive cease to work and the documents are shown with the X on them as seen in the picture.

This behavior does not happen with the redirected documents folders (My Docs and Desktop).

If a user reboots their computer the issue goes away.  If they only log off and then log back in then the issue remains.

Thanks,
Matt
0
ChiefITCommented:
I see the unc path uses the Netbios name to map to the share. I am thinking the connection is a netbios problem where netbios isn't checking in like it should, only on startup does it broadcast out.

So, here's what we could do. Next time this happens, Do you see any discrepancies in "My network places", like missing shares. Also, can you do a netbios ping to the server carrying the shares. Example:
Ping Kaustfs1? what about ping Kaustfs1.domain.name? I am beginning to think you may have a netbios conflict.

If you can ping by FQDN and not by netbios name, then check your event logs for 8032 and 8021 eventst stating something like the browser service has been stopped and an election has been forced.
0
brownmattcAuthor Commented:
I am not seing either of those events but I am seeing 8033 on my clients:

The browser has forced an election on network \Device\NetBT_Tcpip_{88286459-84AB-49AE-9413-F05788B46303} because a master browser was stopped.


Other than that I do not seem to see anything common among the clients.  Do you know what that X on the documents mean?  Is that just that the share has stopped responding?

Thanks,
Matt
0
ChiefITCommented:
There it is:

The server doesn't seem to understand what NIC to bind to with netbios.

How many nics do you have? If not two or more nics, do you have a VPN connection??
0
brownmattcAuthor Commented:
Two nics that are teamed. They are both connected.  HP Proliant server.

I noticed in the TCP/IP settings of the team that theyre was an entry for a WINS server which I removed since we are not using WINS and WINS is not installed on the computer.

Could WINS be causing the NETBIOS issue?  Can you think of anything else that I should look at?
0
ChiefITCommented:
Could WINS be causing the NETBIOS issue?  

Absolutely.

Netbios resolution is to WINS  as a DNS reolution is to DNS.

This is the way it works. Netbios broadcasts use the browser service to populate a list of folders and computers within "My Network Places". WINS is used to take that browselist and transfer it from one site to another. WINS does this because netbios broadcasts are not routeable. This means it will not propogate over NAT, through a VPN tunnel, across a VLAN, or basicly route to a remote sites or subnet.
_______________________________________________________________
Can you think of anything else that I should look at?

You are on the right track. If you have a flat domain, with no subnets or VLANS, you do not need WINS. Netbios broadcasts will take care of you.

Another thing to conisider is the need for NIC teaming, I sometimes recommend against it because of the communications discrepancies that can come with teaming. Not always does teaming software work well. Also the switches need to be configured to allow multicasts to the server that is teamed. If  you have 250 nodes on the network, ONE NIC is sufficient. NIC teaming is a form of multihoming the server and multihomed servers don't often work very well unless configured exactly right.

IN SHORT:
Consider breaking the team or the need for teaming.
Consider the need for WINS to allow netbios broadcasts to be routeable
Then, set up your node type and allow netbios over TCP/IP as well as file and print sharing per nic.

These three steps are kind of generic in content because you have a few things to consider. Once you evaluate your needs, let's get to fixing the issue.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.