Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Direct Access Server DNS Error

Răspuns Direct Access Server DNS Error

  • Tuesday, January 22, 2013 6:10 AM
     
     
    Sign In to Vote
    0

    Hi,

    I'm current trying to setup Direct Access(DA) but the "DNS" part of DA fails with the error "None of the enterprise DNS servers fdfd:fc72:a07f:7777::a0b:5d3 used by DirectAccess clients for name resolution are responding. This might affect DirectAccess client connectivity to corporate resources.". If I ping the address I get a reply. I've tried following multiple resolutions but most refer to Server 2008R2 and UAG installations. I can get clients to connect but with the DNS error but I'm unable to get a client to ping an internal resource either.

    Some "resolutions" mention about enabling ISATAP DNS responses on the DNS server since they are blocked by default. Some mention about having the AAAA record of the IP6 address of the DNS server but from my understanding of Server 2012 DA, everything going to the internal network should be IPv4 and not ISATAP or IPv6.

    I've googled and binged and yahood as much as I can.....   what am I missing?

    DA Server: 2012 STD (2 NIC setup, one external via NAT Firewall (443) and one internal (no firewall))

    DNS/AD/Internal Resources: Server 2008 R2

    Thanks in advance!

     

All Replies

  • Wednesday, January 23, 2013 8:22 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    Thank you for the post.

    I suggest to start from the procedures in the troubleshoot guide below and see if it any help :

    General Methodology for Troubleshooting DirectAccess Connections

    http://technet.microsoft.com/en-us/library/ee624058(WS.10).aspx

    Regards,

    Nick Gu - MSFT

     
  • Wednesday, January 23, 2013 11:26 PM
     
     
    Sign In to Vote
    0
    Thanks Nick but you have done exactly what I mentioned in my post.

    The document you linked is for Server 2008R2 and it reliant on IPv6 to work to internal servers.
     
  • Thursday, January 31, 2013 7:12 AM
     
     
    Sign In to Vote
    0

    Hi,

    I thought the whole idea of the 2012 DA server was so if you only had IPv4 internal network you could still use it?

    Anyway... the DNS server does have IPv6 enabled plus I have tested ISATAP connections. I have added management servers and that passes its tests. I can ping the DNS server fine via IPv6 (fd0d:4668:86e0:7777::a0b:51e) but DNS still shows as failed. What does the DA server do for its test to confirm if the DNS server is available?

     
  • Monday, February 04, 2013 7:13 PM
     
     
    Sign In to Vote
    0

    I am also facing the the same issue, Did this ever get a reply? 

    Thanks,

    Ryan

    Ryan Lewis

     
  • Monday, February 04, 2013 11:56 PM
     
     
    Sign In to Vote
    0

    Hi Ryan,

    No, no luck on this issue.

    I've started to try and source a local resource (contractor) to help with the issue. If I do find out the issue i'll post the answer.

    Regards,

    Adrian

     
  • Tuesday, February 12, 2013 6:24 AM
     
     Answered
    Sign In to Vote
    0

    To resolve my issue.. I had to put the DNS server address as the IP of the internal NIC. Once I did that it worked fine.

    I dont know why it works or why it resolved it as there is no DNS on the DA server.

    Regards,

    Adrian

    • Marked As Answer by Uglyb0b Tuesday, February 12, 2013 6:24 AM
    •