And this morning is the first time I've seen it happen to multiple people at once.
S5fs disk map Offline#
The share itself doesn't appear to actually go offline or anything like that. It's only happening to drives that map to DFS folders in that namespace that point to shares on that 2012 server (no one has a drive that maps directly to the shares on that server).
S5fs disk map Pc#
My hunch is that something in the Windows 7 client PC is getting. I'm about to migrate about a share accessed by 500 users to this 2012 system, and I can't until I get this figured out. And it has been kinda rare (currently less than 75 users who could potentially experience it). It has only happened with the shares on the Server 2012 system. And like the share on the 2003 server, no user has experienced the issue with this share. Some of those users who have had this issue, also have an X: drive, which is mapped to:īut this is a CIFS share. I've seen a few other users outside the aforementioned office who had the issue, but this is the first opportunity I've had to get more information on it before the client PC was rebooted.
If they then went back into Computer, their T: drive would again be working, without having to re-create the mapping.Īlso, even though users couldn't browse directly to \\\namespace\OfficeShare1, without first browsing \\\namespace, they could browse directly to \\2012FileServer\OfficeShare1. From there, they could go to the \OfficeShare1 folder without any errors. Thus, re-creating the drive map would not work.Īfter trying that, a user could go to \\\namespace and that would work fine. Typing \\\namespace\OfficeShare1 in the address bar would cause the Computer window to hang before erroring-out. The T: drive appeared in the Computer window, but was showing as disconnected, and double-clicking it would throw an error about the path being unavailable. Going to Computer > Map network drive, I could see the label for \OfficeShare1 was still attached to T:, but the path was empty. They had no problems with accessing this, ever. We have other offices that have their own shares on the same server, and mapped to a DFS folder the same way, and those have been working OK (as far as I know). This share is only a few weeks old, and has been working fine for them until today. Which is a DFS folder that simply points to: Their T: drive, which is the one they had a problem with, is mapped via group policy to this: We had a problem this morning with every user (about a dozen) in one of our small branch offices being unable to access a certain network share.
0 kommentar(er)
