IPV6 interfering with external DNS resolution: Windows 2008, IPv6, SBS 2008

Page 1 of 6

Hello, Hello, cybera

Upgrade to Business Account

Help

About Us

My Account

Log Out

Search Experts Exchange

Experts Exchange > OS > Microsoft OS > MS Server OS > Windows Server 2008 > IPV6 Interfering With External DNS Resolution

or Go to Advanced Search

Workspace Workspace

Profile
0 6 1 1 1 0 0 0 0 0 0

IPV6 interfering with external DNS resolution

Asked by: hypercat Solved by: hypercat

My My Open Open Questions Questions My My Answered Answered Questions My My Monitored Monitored Questions Questions

I'm having a strange issue on a Windows SBS 2008 server. It's been installed and running fine for a couple of years. Just recently (about a week ago or so) some of the users started complaining about not being able to get to some websites. The websites were accessible using IP addresses but not names. Long story short, I discovered that the DNS server was listing its IPv6 IP address as the primary DNS server rather than the IPv4 address. This seemed odd to me, so I experimented by DISABLING IPv6 to see if it resolved the issue, and it did. So, I left IPv6 turned off, I thought permanently. However, now I'm seeing errors in the event lot related to the MSExchangeADAccess service. The Exchange Active Directory provider discovers the server (event ID 2080), but that is immediately following by Event 2114: Log Name: Application Source: MSExchange ADAccess Date: 2/7/2011 2:36:28 PM Event ID: 2114 Task Category: Topology Level: Error Keywords: Classic User: N/A Computer: CHROME.domain.com Description: Process STORE.EXE (PID=2796). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="MSExchange ADAccess" /> <EventID Qualifiers="49156">2114</EventID> <Level>2</Level> <Task>3</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-02-07T19:36:28.000Z" /> <EventRecordID>641550</EventRecordID> <Channel>Application</Channel> <Computer>CHROME.raynardpeirce.com</Computer> <Security /> </System> <EventData> <Data>STORE.EXE</Data> <Data>2796</Data>
Link Email

My My Participated Participated Questions My My Topics Topics My My Personal Personal Knowledgebase My My Articles Articles My My Blog Blog Entries Saved Saved Searches My My Projects Projects My My Participated Participated Projects Help Help

Top Windows Server 2008 Experts

Week Month Year Overall
Overall

1.

ve3ofa Wizard 0 points yesterday

362,196

2. 3. 4. 5. 6. 7. 8. 9.

hanccocka Rancy mkline71 Sembee2 takecoffe arnold Subsun Sandeshdubey

342,650 334,825 282,149 247,806 170,365 161,211 158,846 157,213 144,123 143,799 138,278 130,347 123,770 122,408 120,869 118,700 105,435 101,658 96,128
Print

10. footech 11. Jaihunt 12. sarang_tinguria 13. breadtan 14. leew 15. ArneLovius 16. Mutawadi 17. cgaliher 18. amitkulshrestha 19. Coralon 20. McKnife
Unmonitor

21. dvt_localboy

Save

95,537

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Window... 24/09/2013

IPV6 interfering with external DNS resolution: Windows 2008, IPv6, SBS 2008

Page 2 of 6

<Data>80040a02</Data> <Data>DSC_E_NO_SUITABLE_CDC</Data> </EventData> </Event> This is obviously not a good thing long-term. My preferred resolution would be to be able to re-enable IPv6 because I know that will resolve this issue. However, I also need to make sure the browsing issue doesn't come back. Does anyone know of a way to force DNS to use IPv4 over IPv6? I'm a newbie where IPv6 is concerned and have never delved into its secrets.

22. DrDave242 23. RobWill 24. Qlemo 25. npsingh123

82,698 82,562 82,187 81,606

Tags: Windows 2008, IPv6, SBS 2008 Topics: Windows Server 2008, SBS Small Business Server Participating Experts: 5 Points: 0 Comments: 18 2011-02-08 at 03:59:11 ID26804178

Answers
EXPERT COMMENT
by: HawyLem Posted on 2011-02-08 at 04:07:08 ID: 34835120

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tcpip6\Parameters\ create a DWORD named DisabledComponents and set it to 000000FF, this should disable ipv6 from all interfaces. Reboot to be effective. (http://4sysops.com/archives/why-and-how-to-disable-ipv6/)

EXPERT COMMENT
by: renazonse Posted on 2011-02-08 at 04:08:53 ID: 34835142

Completely disabling IPv6 requires a registry change: http://www.windowsreference.com/networking/disable-ipv6-in-windows-server-20008-full-coreinstallation/ Also, within your DNS management console go to the server properties and set DNS to only listen on the IPv4 address of the server. Flush the DNS cache and restart DNS...you may have to reboot the server for the IPv6 registry change to take effect.

EXPERT COMMENT
by: dariusg Posted on 2011-02-08 at 04:14:13 ID: 34835195

You should not completely disable IPv6 on a SBS server. Here is what you should do. The overall issue is that the network binding order is not setup properly. http://thebackroomtech.com/2009/01/15/howto-edit-network-card-bindings-in-windowsserver-2008/

EXPERT COMMENT
by: dariusg Posted on 2011-02-08 at 04:14:32 ID: 34835198

Make sure IPv4 is listed first in the network binding order

AUTHOR COMMENT
by: hypercat Posted on 2011-02-08 at 04:33:03 ID: 34835413

Thanks all for your ideas. IPv4 is first in the binding order. In fact, IPv6 is not even checked in the Advanced Settings dialog box.
Link Email Unmonitor Save Print

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Window... 24/09/2013

IPV6 interfering with external DNS resolution: Windows 2008, IPv6, SBS 2008

Page 3 of 6

EXPERT COMMENT
by: dariusg Posted on 2011-02-08 at 04:35:15 ID: 34835438

Check IPv6 then make sure that IPv4 is listed first

AUTHOR COMMENT
by: hypercat Posted on 2011-02-08 at 04:37:47 ID: 34835467

I'm leery of disabling IPv6 entirely, since this is SBS, but I'll try the regedit for disabling IPv6 and let you know how that does in terms of the SBS overall operation.

EXPERT COMMENT
by: dariusg Posted on 2011-02-08 at 04:45:51 ID: 34835555

Do not disable IPv6 this was cause issues with Exchange. Make sure IPv6 is not listed here or not being used. http://technet.microsoft.com/en-us/library/cc740071(WS.10).aspx

EXPERT COMMENT
by: renazonse Posted on 2011-02-08 at 04:50:22 ID: 34835603

It actually depends on which service pack level of Exchange you're running...earlier versions required IPv6 to be disabled because it conflicted with Outlook Anywhere. Microsoft actually recommends disabling if you're having issues: http://technet.microsoft.com/en-us/library/cc671176%28EXCHG.80%29.aspx http://technet.microsoft.com/en-us/library/bb629624%28EXCHG.80%29.aspx http://msexchangeteam.com/archive/2008/06/20/449053.aspx There's no harm in disabling it...it can be re-enabled if you decide you need it.

AUTHOR COMMENT
by: hypercat Posted on 2011-02-09 at 01:41:03 ID: 34844051

Unfortunately, disabling IPv6 completely caused some other serious problems with Exchange topology. The Microsoft Exchange info store service would not run properly and there were numerous errors in the event logs because the topology service could not connect to AD. So, that option is out. I'm puzzled why, even with the correct binding order, the IPv6 address still shows first when you do an ipconfig /all. However, I checked at another site that has a Windows 2008 DC with DNS and it shows the same thing. So, it appears to be normal that this happens. Anyone have any ideas then why this would interfere with name resolution for external hosts? Perhaps that's the way to approach this issue.

EXPERT COMMENT
by: dariusg Posted on 2011-02-09 at 01:43:38 ID: 34844089

ipconfig /all will show IPv6 first that is not a problem. When you ping a domian name you should get a IPv4 IP address

EXPERT COMMENT
by: renazonse Posted on 2011-02-09 at 01:46:49 ID: 34844135

What service pack level is Exchange? Also, read this: http://msmvps.com/blogs/acefekay/archive/2010/05/27/how-to-disable-rss-tcpchimney-feature-and-ipv6.aspx

Link Email Unmonitor Save Print

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Window... 24/09/2013

IPV6 interfering with external DNS resolution: Windows 2008, IPv6, SBS 2008

Page 4 of 6

And specifically this: http://blogs.technet.com/b/sbs/archive/2008/10/24/issues-after-disabling-ipv6on-your-nic-on-sbs-2008.aspx

EXPERT COMMENT
by: wylie_uk Posted on 2011-02-09 at 19:56:54 ID: 34851232

exchange relies on IP6 so do not disable it. do you have forwarders on your DNS server? if no.. there is a bug that sounds just as you are discribing and you can prove it is the bug by flushing your server dns cache, then if the websites are reachable is a caching issue on the server. (u may need to flush the local dns cache too) having forwarders on your dns server fixes this stupid bug.

AUTHOR COMMENT
by: hypercat Posted on 2011-02-10 at 05:48:35 ID: 34857080

@wylie_uk - I don't have forwarders on this server. I didn't try flushing the DNS cache entirely, but I did try removing the cached entries for one of the websites that wasn't browsable when the problem was happening, and it didn't resolve the issue. I was looking at the first article supplied by renazonse in post #34844135, so I ran the command to show the interfaces, and I noticed a very strange thing. The network card on this server is, in fact, getting TWO IPv6 addresses. There's only one physical NIC in the server, and RRAS is not configured, so I'm wondering if anyone has any idea why this would happen. Here are the ipconfig /all and netsh command results: Microsoft Windows [Version 6.0.6001] Copyright (c) 2006 Microsoft Corporation. All rights reserved. C:\Users\Administrator>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : CHROME Primary Dns Suffix . . . . . . . : domain.com Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : domain.com Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : HP NC373i Multifunction Gigabit Server Adapter Physical Address. . . . . . . . . : 00-25-B3-A5-A5-7E DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::e597:1cc9:b8ba:d557%10(Preferred) Link-local IPv6 Address . . . . . : fe80::eb80:78f2:8fae:9089%10(Preferred) IPv4 Address. . . . . . . . . . . : 10.0.0.1(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 10.0.0.5 DNS Servers . . . . . . . . . . . : fe80::eb80:78f2:8fae:9089%10 10.0.0.1 Primary WINS Server . . . . . . . : 10.0.0.1 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter Local Area Connection* 8: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : isatap.{7320D9AE-145C-4C32-B0FB-715E35A65154} Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes C:\Users\Administrator>netsh interface ipv6 show interfaces
Link Email Unmonitor Save Print

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Window... 24/09/2013

IPV6 interfering with external DNS resolution: Windows 2008, IPv6, SBS 2008

Page 5 of 6

Idx Met MTU State Name --- --- ----- ----------- ------------------ 1 50 4294967295 connected Loopback Pseudo-Interface 1 11 50 1280 disconnected Local Area Connection* 8 10 20 1500 connected Local Area Connection

EXPERT COMMENT
by: dariusg Posted on 2011-02-10 at 07:16:10 ID: 34857745

The Tunnel Adapter is normal with a IPv6 being enabled You can disable that inteface using this link. http://support.microsoft.com/kb/929852 Did you check your DNS to see what IP address it is listening on?

ACCEPTED SOLUTION
by: hypercat Posted on 2011-03-02 at 01:14:07 ID: 35009549

The tunnel adapter has nothing to do with it. What I was questioning was the fact that the Ethernet adapter has 2 IPv6 addresses - this seems odd and not quite right to me. I've not seen this elsewhere. At any rate, I had to re-enable IPv6 on the server in order to resolve the AD issues, and so far the original problem that started this question has not recurred. I am closing the question with thanks to all who tried to help on this.

AUTHOR CLOSING COMMENT

by: hypercat Posted on 2011-03-06 at 17:25:05 ID: 35045606

The ultimate solution was to disable then re-enable IPv6. After re-enabling it, the problem hasn't recurred. However, there was never any real explanation as to why it happened in the first place.

YOUR COMMENT
by: cybera Posted on 2013-09-24 at 14:33:19 ID: 39516961

I faced the similar issue. I am using SBS-2008, updated with the latest patches. One fine day my clients in their office are unable to resolve DNS addresses. However, all incoming connections including VPN-PPTP were working well. My usual solution was to restart the server, and that should fix it. Initially we thought it was due to the Antivirus software installed on the server. Actually the solution in the past was also relatively simple, disable network adapter, and re-enabling it will work. However, we couldn't do that as it will disconnect our remote support session. Restarting the server was a better choice for us. We ran nslookup on the server, it showed an ip v6 NS. It can resolve names properly. we ran nslookup on the workstations, it showed ip v4 NS, which is the correct and default NS, and we couldn't resolve the DNS. We could still maintain a connection via teamviewer, but simply not resolve any DNS when browsing sites. After disabling IPv6 on the network adapter on the server, we were able to resolve DNS entries fine on the server and the clients. In addition, we were also able to connect to the internet on both server and clients. I do realize that Exchange might encounter problems, so I turned IPv6 back on again in the server network adapter and problem was resolved. I believe this will come back again.. and I don't think the above is a real-solution yet. Can anyone give some thought and perhaps explain in depth? I am not a DNS expert, nor a Windows Server 2008r2 expert... So I hope we can get to the root of this issue.
Link Email Unmonitor Save Print

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Window... 24/09/2013

IPV6 interfering with external DNS resolution: Windows 2008, IPv6, SBS 2008

Page 6 of 6

Post a Comment
H2
Code

Attach File

Also Share On

Facebook

Twitter

LinkedIn

WHAT IS EXPERTS EXCHANGE?

Overview How it works Features View Topics Plans Plans & Pricing Our Customers

OUR COMMUNITY
Point Point System System Expert Benefits Benefits Expert Awards Awards Business Accounts Customer Support Job Board

GET SUPPORT SUPPORT

Site Help Help Terms of Use Use Privacy Privacy Policy Policy Site Map Map URL Shortener

THE COMPANY
About Us Contact Us Blog Tech Tech News Blog Blog EE Store

MAIN TOPICS
Microsoft Apple Internet Gamers Digital Digital Living Living Virus Virus & Spyware Hardware Hardware Software Software Security

Browse Browse All Topics Topics Developer Storage Storage OS Database Database

TRENDING TOPICS
iOS JavaScript MS Access Java MS MS SQL Server Android Visual Basic .NET MS MS Excel Exchange C# Outlook PHP WordPress Oracle Database Visual Basic Classic Classic .NET Programming

Programming Web Web Development Networking

1996-2013 Experts Exchange, Exchange, LLC. LLC. All All rights reserved. Covered by US Patent.

Asker Certified

Link

Email

Unmonitor

Save

Print

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Window... 24/09/2013