Ok this has been bugging me for two days now. Computer was up and running fine, then noticed a glitch with folders not working properly all of a sudden, one or two folders that were on the DFS store. Still worked, could ping all the servers and use the internet. Ended up having to bring down all the servers for routine maintenance and brought them back up shortly there after. Then I had a major issue with one client. Normally the Network shows up as the domain, after the servers were brought up online, the machine was brought up on line. It asked for type of network (public, work, private) and named it Network3. I checked the IP address since it gets its address from DHCP, and the IP address was correct and the DNS Servers were correct, along with the gateway, but I had a yellow flag over the network icon. Limited access. So troubleshooting begins. 1. Ipconfig /release, then ipconfig /flushdns, then ipconfig /renew. I get a good address from the DHCP server. Still have the flag. 2. Ping both DNS servers using name, could not resolve name. Ping both DNS servers using IP address, request timed out (keep in mind the DHCP server and the second DNS server are one and the same). Ping the gateway by name and ip address, could not resolve name and request timed out respectively. Ping 127.0.0.1 with good results, ping client address from DHCP with good results. 3. Replace cable from client to switch, trying various ports in the switch and doing the above steps each time. Still the same result, tried 2 more cables, with the same result. 4. Ran Nslookup from the client; default server: UnKnown, Address: 192.168.0.1 (this address is correct for the DNS server). Type in server name request timed out. Type in various other clients and servers, request timed out. 5. Ran Nslookup from both DNS Servers. All clients and servers resolved using the opposite DNS server as the queried server. (This includes the troubled client). 6. Uninstalled DNS Server and DHCP server from the second server, rebooted. Reinstalled DHCP, redid the scope, rebooted. All other clients populated shortly there after. Reinstalled DNS Server and rebooted. Uninstalled primary DNS server and rebooted. Installed primary DNS server and rebooted. Turned on troubled client, it picked up the IP address from the DHCP server which showed the machine name in the DHCP address leases. 7. Ran steps 1, 2, and 4 again. Still does not work. Unjoin from Domain, go to rejoin, unable to rejoin. Still unable to ping any of the servers. 8. Ran pings from various clients on the DNS servers with no problems, pinged the gateway with no problems. 9. Beat my head against the wall a few times, and then came on here to ask questions. So anyone have any ideas on how to get this client machine to find the DNS servers? I even tried a static address and that dd not resolve the issue. Not sure what cause the name resolution issues all of a sudden. Also the firewall is off before anyone asks.Michael R. Mastro II

when you unjoin it from domain did you delete the computer out of AD before rejoining?

Yes I did. I always do that as a practice, after the first time I didn't do that and had errors getting the machine back into AD.Michael R. Mastro II

The IP Stack on the local PC may be to blame. Check out the link below to repair that. http://support.microsoft.com/kb/299357 Then try these comman line options as well to clear all DNS/Network info off the machine http://technet.microsoft.com/en-us/library/cc757819(v=ws.10).aspx Good Luck.

Ran the netsh ip reset with no luck, still the same issues. Ran all the possbile command lines steps with no luck. On an off chance ran a system restore to two weeks ago, a week before problems emerged. Guess what it works now. The restore checkpoint was for critical updates, I think one of them might be to blame. Just have to figure which one it is.Michael R. Mastro II

Ran the netsh ip reset with no luck, still the same issues. Ran all the possbile command lines steps with no luck. On an off chance ran a system restore to two weeks ago, a week before problems emerged. Guess what it works now. The restore checkpoint was for critical updates, I think one of them might be to blame. Just have to figure which one it is.Michael R. Mastro II

Hi, You may check the reliability monitor to see the updates you installed, this maybe give you a direction for this issue. Alex Zhao TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Alex Zhao TechNet Community Support

Hi, You may check the reliability monitor to see the updates you installed, this maybe give you a direction for this issue. Alex Zhao TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Alex Zhao TechNet Community Support