Ok, so the only "oddity" in the IPv6 settings I saw was "::1" in the DNS server field, I've removed this, IPv6 is still showing in IPCONFIG on the server? I've added the reverse lookup zone for 10.10.10.X and everything looks ok on the clients, IPCONFIG and NSLOOKUP-wise anyway! Below is the IPCONFIG from the server, anything look out of place or have we cracked it? Windows IP Configuration Host Name . . . . . . . . . . . . : CORE Primary Dns Suffix . . . . . . . : intranet.sqn Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : intranet.sqn Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet Physical Address. . . . . . . . . : 00-9C-02-A0-3C-5B DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::b8b7:f543:33a7:13e2%11(Preferred) IPv4 Address. . . . . . . . . . . : 10.10.10.10(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 10.10.10.5 DHCPv6 IAID . . . . . . . . . . . : 234920962 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-D7-41-82-00-9C-02-A0-3C-5B DNS Servers . . . . . . . . . . . : 10.10.10.10 127.0.0.1 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.{B0518717-B957-43D6-93CD-AE32A62C2286}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Teredo Tunneling Pseudo-Interface: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes

Also seen the following error under DHCP server: This computer has at least one dynamically assigned IPv6 address.For reliable DHCPv6 server operation, you should use only static IPv6 addresses.

Yes, looks good to me. I think you might have got it with the reverse lookup. The error about dynamic ipv6 can be ignored if you're not using ipv6 address space as yet. Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows] Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Thanks Dave, you've been a great help.

You're welcome. Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows] Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Ok, sounds good. Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows] Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

hi, This will need a whole IPconf of your network to verify where the problem is. Thanks,akshay vithalkar

Ok, I've added 127.0.0.1 as the secondary on the server and added the OpenDNS servers (208.67.222.222 and 208.67.220.200) in the forwarders and everything seems ok. Is there a way I can double check that queries are actually going through the OpenDNS servers?

Hi, I'm trying to set up Server 2008 R2 on a small network but I'm having a few problems! The server has been set-up as a DC and has AD, DHCP and DNS running. I've tried adding it to the network but I'm getting issues with a few of my client machines (Couple of XP and a vista machine, these will be changed soon!) The server is connected to a Netgear Router/Modem and I have disabled the DHCP server mode on this which then connects to my ISP. 1 Machine connects via ethernet the others via Wi-Fi. No machines are have been registered to the domain as I believe this should work regardless. The PC connected via ethernet appears to be working OK, no issues that I could see.The other PCs struggled to connect to the Wi-Fi, taking ages to receive a valid IP, get external connection etcWhen connected, some sites load fine, some very slowly and some do not load at all. www.google.com will work fine but then I tried www.hotmail.com and it refused to load.When I turned the server off and turned the Netgear's DHCP mode back on everything started working 100% I know that's not a lot to go on, but hopefully someone will have an idea! I'm willing to try anything!

Hi Dave, When I run nslookup on the server I get the following result. C:\Users\dt>nslookup 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa primary name server = localhost responsible mail addr = nobody.invalid serial = 1 refresh = 600 (10 mins) retry = 1200 (20 mins) expire = 604800 (7 days) default TTL = 10800 (3 hours) Default Server: UnKnown Address: ::1 When I run it on a client I get the following: 10.10.10.10.in-addr.arpa primary name server = localhost responsible mail addr = nobody.invalid serial = 1 refresh = 600 (10 mins) retry = 1200 (20 mins) expire = 604800 (7 days) default TTL = 10800 (3 hours) *** Can't find server name for address 10.10.10.10: No information *** Default servers are not available Default Server: UnKnown Address: 10.10.10.10 On a side note, I'm concerned it's showing "ip6" on the server's nslookup as the whole network should be IPv4...

Posting unedited ipconfig /all of DNS server and problem client may help. Generally make sure local DNS server has own address as primary and other DNS server address as secondary (127.0.0.1 if single DNS server) in network connection properties and is not multi-homed. Also put public DNS addresses as forwarders only on local DNS server. Client should have local DNS address only so client can find and logon to domain. Forwarders are so clients can find and resolve internet queries. Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows] Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Make sure you didn't add the ipv4 addresses on the ipv6 properties. Also check the reverse lookup is correct. http://technet.microsoft.com/en-us/library/cc961414.aspx Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows] Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

You can use nslookup http://support.microsoft.com/kb/200525 Also Steve Gibson's tool here. http://www.grc.com/dns/benchmark.htm Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows] Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Thank you Dave, I will double check all of those and get back to you.