Windows 7 Pro x64 in domain w/ Windows 2003 Standard, 32 bit, single DC. There are 34 total workstations. I have three Windows 7 PC's that are getting DNS timeouts. These are DHCP from the service on the DC. All other stations are successful. Even with static definitions, DNS timesout occurs. With DNS definition of a public server, Windows 7 PC's surf 'net flawlessly. Back to internal DNS, same used by all other stations; no Internet resolution, and DNS timeouts occur. All updates applied to workstations and DC. Latest NIC drivers applied. No viruses to be found, no corruption detected. Most posts I've found on this issue point to basic points of misconfiguration . . . I've checked all the basics, and applied updates, so I am confident this is not a simple misconfiguration.

A lot of people have posted about this issue. MS haven't done anything about it as yet. We have the same issues in just our Windows 7 laptops. Our workaround is we manually set the DNS, it works until the next restart, next restart you have to do the reverse, that is set DNS to automatically assign... our users does this way! waiting for MS to give an update on this!!! We have done all, checked the configurations, rechecked the configurations, reconfigured the wireless device, naah! Everyone said Vista was crap, they never knew Windoes 7 was coming.....

I was seeing a problem similar to yours. So similar, it may have even been the same problem. On my network, I have around 30 Windows 7 (x32) and 10 Windows XP machines. All are DHCP clients, served by a Windows 2000 DHCP server. This server is a DC. It started with a single Win7 client and the DNS timeout issues you describe. I changed that client's NIC and my problem went away. I put the NIC in another machine, and the problem appeared there. Strange, I'm thinking, because the problem didn't feel like hardware to me. So, the problem NIC is kept offline, when lo and behold, a second Win7 client starts up with the DNS timeouts. This is on a different NIC. I thought this over for awhile, and it occurred to me, the "problem" NIC was asking for it's lease back! Once the lease expired, the second machine came along and got that IP! So, my problem seems to be related to the DHCP server, and specifically a single IP. For now, I have marked this IP as "excluded" but I imagine there is some sort of DHCP maintenance to straighten it out.