Solved

Domain-Wide Windows 7 Explorer and Network Discovery Issues

Posted on 2016-09-02
3
27 Views
Last Modified: 2016-09-22
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.
0
Comment
Question by:philodendrin
3 Comments
 
LVL 93

Accepted Solution

by:
John Hurst earned 250 total points (awarded by participants)
ID: 41782220
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
 
LVL 6

Assisted Solution

by:K_Wilke
K_Wilke earned 250 total points (awarded by participants)
ID: 41782495
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

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
How to scan rdp  ''only'' open port 3333? 5 116
HP Laser Jet Errors 10 93
Password managers 1 31
Cisco Policy based routing 2 39
This is the first one of a series of articles I’ll be writing to address technical issues that are always referred to as network problems. The network boundaries have changed, therefore having an understanding of how each piece in the network  puzzl…
An article on effective troubleshooting
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

776 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question