Domain-Wide Windows 7 Explorer and Network Discovery Issues

Yesterday we were told by one of the offices/networks we manage that client PCs were unable to see mapped drives when they browsed to "Computer" on their Windows 7 workstations. The office is running Windows Server 2012 R2 Standard with the Essentials role enabled. Clients affected were all running Windows 7 Pro. All clients were affected.

When we tested the issue, we noted that Group Policy and Login Scripts (some users are getting their mapping via GP and some via login scripts in AD) were mapping the drives correctly, When we'd browse to "Computer" or Explorer on the workstations,  the drives are initially there. But, if you wait long enough, the drives would disappear and neither local or network drives would be discoverable. If you restart the explorer process, everything came back. We could easily recreate the issue by browsing a network share and going around 4 folders deep and then back-out of the folders, returning to the root of "computer" ...where we should see all local and network drives. This would consistently "break" explorer and recreate the issue. Explorer would essentially spin and stop discovering any and all local or mapped drives until the Explorer process was restarted.

We examined the server and all expected services were running and the behavior was not manifesting itself on the console. Moreover, even when Explorer was not performing properly on the workstations, access to shares via UNC remained unbroken and quick. Likewise, users who had created shortcuts to mapped drives, were still able to browse server shares via their shortcuts. However, searches were either not working or painfully slow. No errors or issues noted on the LAN switches. Their VoIP phones also remained unaffected, as did their firewall.

We looked for commonalities on the workstations such as specific Antivirus definition files or Windows updates, but found no such correlations.

Out of ideas, we ran DCDIAG from an elevated command prompt on the Server 2012 R2 server and it passed all but one test related to a system log. It did not seem related. Later that day, we restarted the server and the issue subsided. The workstations were again able to browse mapped drives and shares without Explorer bombing out.

So... what happened here? Could this have potentially been some type of corrupt server "Network Discovery" service issue that the client workstations rely on? We knew it had to be top-down / domain-workstation based because of the way it was manifesting, but couldn't put our finger on what services to restart or begin to troubleshoot.

Nothing of consequence was logged in Event Viewer.
philodendrinAsked:
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.

JohnBusiness Consultant (Owner)Commented:
Domain-Wide Windows 7 Explorer and Network Discovery Issues  .. restarted the server and the issue subsided

We have had "widespread server" issues on occasion - not many to be sure. But a server restart is a normal corrective action.

It may not have started all possible services on the last restart (when you did updates, say). I have seen that happen as well - not often to be sure.
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
K_WilkeCommented:
I am assuming that you are running DNS on your server.
If so I wonder if DNS is having a struggle with old computers being on there.
If it is DNS here are the steps I would take to clean up DNS:

1)      Make the DNS point to the server itself.
2)      Under c:\windows\system32\config rename the netlogon files as old.
3)      Delete the old DNS zone
4)      Install a new zone
5)      Take all defaults except make secure insecure.  Also the name of the zone should be the name of the AD, such as nmpg.biz.
6)      Under command prompt type the following:  IPCONFIG /FLUSHDNS & NET STOP NETLOGON & NET STOP DNS & NET START DNS & NET START NETLOGON & IPCONFIG /REGISTERDNS
7)      Install the reverse lookup zone.  Take all defaults except for secure make unsecure and secure.
8)      Under New Pointer do the server IP and make it the server.
9)      Under command prompt type the following:  IPCONFIG /FLUSHDNS & NET STOP NETLOGON & NET STOP DNS & NET START DNS & NET START NETLOGON & IPCONFIG /REGISTERDNS

See if this works.
0
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
Network Operations

From novice to tech pro — start learning today.

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.