Hello. Not sure if this is best posted in the Win7 client area or Server 2008 area. Anyway, here's the issue. A couple of weeks ago, one of my Windows 7 pro systems lost it's ability to connect to a printer share on a Server (Server 2008 R2 domain conntroller at site B). After some troubleshooting, I determined this computer could not access any domain resources (shares) regardless of which user account I was using. Interestingly, I could ping whatever I wanted on my network by name without a problem. So, I tried resetting the computer account in AD with no luck and then I tried to disjoin and rejoin the computer to the domain. When I tried to do this, the computer was not able to find the domain controller. I ended up re-imaging this system and all was fine. This week the same thing happened to another Windows 7 pro system. This time the symptom is the inability to connect to a printer share hosted on server 2008 domain controller at site A. Again this system can't access any shares specified by UNC, but can ping every host I can think of. This system is located at my site so I can do more troublshooting and I plan on scouring the logs as a next step. Any ideas on this at this point? I'm worried this is going to happen to all of my systems. I've seen this happne when computer accounts have been deleted from AD or the computer account is bad for some reason. We are running all Windows 7 Pro and have 2 sites. Each site has a Server 2008 domain controller ( one is standard and the other is R2).

Update: Tried accessing UNC path with fqdn and IP and neither worked. Ran Netdom on DC and verfied there is a secure channel between affected client and DC I'm able to UNC to affected client from the DC (\\computername\c$) and this works fine. nslookup returns correct domain controller/dns server name. I'm not seeing any interesting errors in the logs of the domain controller. I'm seeing these errors in the log on the client. The first and 3rd errors repeate over and over and the 2nd error occurred once. Any assistance would be greatly appreciated. thank you. ______________________________________________________ Log Name: System Source: Microsoft-Windows-DNS-Client Date: 5/4/2011 7:26:12 PM Event ID: 1014 Task Category: None Level: Warning Keywords: User: NETWORK SERVICE Computer: computername.corp.domain.com Description: Name resolution for the name domain.com timed out after none of the configured DNS servers responded. ______________________________________________________________ Log Name: System Source: Microsoft-Windows-DNS-Client Date: 5/5/2011 9:33:10 AM Event ID: 1006 Task Category: None Level: Warning Keywords: User: LOCAL SERVICE Computer: computername.corp.domain.com Description: The client was unable to validate the following as active DNS server(s) that can service this client. The server(s) may be temporarily unavailable, or may be incorrectly configured. 10.1.1.20 _________________________________________________ Log Name: System Source: Microsoft-Windows-GroupPolicy Date: 5/5/2011 9:22:47 AM Event ID: 1058 Task Category: None Level: Error Keywords: User: domain\computername Computer: computername.corp.domain.com Description: The processing of Group Policy failed. Windows attempted to read the file \\corp.domain.com\sysvol\corp.domain.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: a) Name Resolution/Network Connectivity to the current domain controller. b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). c) The Distributed File System (DFS) client has been disabled. __________________________________________________________________________________

Hi, If you cannot ping by name, but can by IP address, you have a DNS problem, but now you cannot access via IP address. I suspect this also is related to network connection. Currently, you could try to boot into Safe Mode with networking to check how it works. Regarding the DNS issue, please kindly refer to the following article: Troubleshooting DNS Hope it helps. Alex ZhaoPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Alex, I tried Safe mode with networking and this results in the same problem. By "network connection" do you mean a physical layer issue or something above that? I updated drivers and this did not help. Reset the TCP/IP stack and this did not help either. Systems using the same switching infrastructure and port do not experience the same issue. I will run through the DNS troubleshooting link you sent me.