I have a small win 2003 domain that has 1 dns (pdc). The dns pdc server will provide nslookup queries to every computer, except for one windows 7 machine. This is the result of the nslookup : DNS request timed out. timeout was 2 seconds. Default Server: UnKnown Address: 192.168.15.1 > www.google.com Server: UnKnown Address: 192.168.15.1 DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. *** Request to UnKnown timed-out This is the ipconfig: Connection-specific DNS Suffix . : xxxxxxx Description . . . . . . . . . . . : Marvell Yukon 88E8053 PCI-E Gigabit Ether net Controller Physical Address. . . . . . . . . : 00-xx-xx-xx-xx-xx DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 192.168.15.50(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Tuesday, March 08, 2011 3:02:46 AM Lease Expires . . . . . . . . . . : Wednesday, March 16, 2011 3:02:47 AM Default Gateway . . . . . . . . . : 192.168.15.1 DHCP Server . . . . . . . . . . . : 192.168.15.1 DNS Servers . . . . . . . . . . . : 192.168.15.1 Primary WINS Server . . . . . . . : 192.168.15.1 NetBIOS over Tcpip. . . . . . . . : Enabled This is tracert: Tracing route to zeus.xxxxxxxxx [192.168.15.1] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms zeus.xxxxxxxxx [192.168.15.1] Trace complete. As you can see, the nslookup fails, but the trace does not. DNS is working on everything, except nslookup. Any ideas?

As I see, 192.168.15.1 is your default gateway, your DHCP server, your DNS server and your WINS server. Is it your 2003 server? Is your 2003 server used as a router? Please make sure that you are using the correct DNS server and the correct default gateway IP Address. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

Mr X, thanks. I've tried it every way, up and down, forwards and backwards. The pdc is the gateway, yes. It does not run to a router, if that's what you were thinking. Like I said, everything works, except for nslookup. All ip addresses are assigned through dhcp and all the other computers on the network use nslookup, just fine. This is the only one that is windows 7. I wouldn't be able to browse here or use tracert, if dns, itself wasn't working. I can't find anything online about this, either.

Please try to disable your client computer firewall and all security softwares and check if this solve your problem. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

I tried that, as well. Disabled ms firewall and uninstalled the virus scanner.

theonlytalkinggoat wrote: I have a small win 2003 domain that has 1 dns (pdc). The dns pdc server will provide nslookup queries to every computer, except for one windows 7 machine.  This is the result of the nslookup : DNS request timed out.     timeout was 2 seconds. Default Server:  UnKnown Address:  192.168.15.1 www.google.com Server:  UnKnown Address:  192.168.15.1 DNS request timed out.     timeout was 2 seconds. DNS request timed out.     timeout was 2 seconds. DNS request timed out.     timeout was 2 seconds. DNS request timed out.     timeout was 2 seconds. * Request to UnKnown timed-out This is the ipconfig:    Connection-specific DNS Suffix  . : xxxxxxx    Description . . . . . . . . . . . : Marvell Yukon 88E8053 PCI-E Gigabit Ether net Controller    Physical Address. . . . . . . . . : 00-xx-xx-xx-xx-xx    DHCP Enabled. . . . . . . . . . . : Yes    Autoconfiguration Enabled . . . . : Yes    IPv4 Address. . . . . . . . . . . : 192.168.15.50(Preferred)    Subnet Mask . . . . . . . . . . . : 255.255.255.0    Lease Obtained. . . . . . . . . . : Tuesday, March 08, 2011 3:02:46 AM    Lease Expires . . . . . . . . . . : Wednesday, March 16, 2011 3:02:47 AM    Default Gateway . . . . . . . . . : 192.168.15.1    DHCP Server . . . . . . . . . . . : 192.168.15.1    DNS Servers . . . . . . . . . . . : 192.168.15.1    Primary WINS Server . . . . . . . : 192.168.15.1    NetBIOS over Tcpip. . . . . . . . : Enabled This is tracert: Tracing route to zeus.xxxxxxxxx [192.168.15.1] over a maximum of 30 hops:   1    <1 ms    <1 ms    <1 ms  zeus.xxxxxxxxx [192.168.15.1] Trace complete. As you can see, the nslookup fails, but the trace does not. DNS is working on everything, except nslookup. Any ideas? Can you post the output of ipconfig from a working computer. And what are the firewall settings on the 192.168.15.1 server? Wolfgang

I think you may try to connect the PC to the Internet directly. Do the nslookup again, ensure the issue is coursed by client or sever