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
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
ASKER
For some reason this site is not allowing me to attach right now...
ASKER
Image
Network-Share.png
Network-Share.png
Are these DFS shares for a Namespace or just a mapped drive to a shared file?
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.
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.
ASKER
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
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
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.
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.
ASKER
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_{88286
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
The browser has forced an election on network \Device\NetBT_Tcpip_{88286
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
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??
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??
ASKER
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?
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?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER