locked
IPV6 slowing thins down RRS feed

  • Question

  • Our company uses Direct Access. For this IPV6 has to be enabled. Everything works fine for users in our main site who have local access to our servers. The problem is with users in remote offices who connect over an IPV4 VPN. Most of the problem is with Exchange connections. It seems that when they start Outlook, it tries to connect over IPV6, fails then tries IPV4. This causes a delay in Outlook connecting to Exchange. It also frequently disconnects or doesn't update mail from the server. If I add an IPV4 entry to the host file, everything works great, but this is not the best solution. Any ideas?
    Mike Pietrorazio
    Friday, November 18, 2011 8:06 PM

Answers

All replies

  • Hi,

     

    There may be conflicting between Exchange and IPV6, I think it is better to post in Exchange Forum.

    http://social.technet.microsoft.com/Forums/en/exchange2010/threads

     

    Meanwhile, I find some related articles for your reference. I assume you are using Exchange 2010.

     

    Understanding IPv6 Support in Exchange 2010

    http://technet.microsoft.com/en-us/library/gg144561.aspx

     

    IPv6 Requirements in Exchange 2010 

    http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/d0cade08-55e1-4748-be2b-7d5433b364ba

    IPv6 support in Exchange Server 2010 

    http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/1de08c4c-8a54-4545-b962-25f28b30379e/

     

    Best Regards,

    Niki


    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, November 21, 2011 7:57 AM
  • Thanks, but the problem is not limited to Exchange, this is just one example. Connecting to file servers shows the same issue. There are no problems with our IPV6 implimaentation as everthing works great at the main site. I'm sure the IPV4 VPN is causing the problem. I'm just trying to find a workaround.
    Mike Pietrorazio
    Monday, November 21, 2011 12:39 PM
  • Hi,

     

    Please check if the following articles are helpful.

     

    DirectAccess Workaround for reaching IPv4 address checking sites

    http://support.microsoft.com/kb/974080

    UAG DirectAccess and IPv4 Only Networks

    http://social.technet.microsoft.com/wiki/contents/articles/uag-directaccess-and-ipv4-only-networks.aspx

     

    I think the issue is not caused by client. It should be a networking issue from client to server via IPv4. I recommend posting in Server Forum to get more assistance.

    http://social.technet.microsoft.com/Forums/en-US/winserverPN/threads

     

    Best Regards,

    Niki


    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, November 23, 2011 8:41 AM
  • Hi,

     

    I am currently standing by for an update from you and would like to know how things are going. If you have any feedback, please let us know.

     

    Best Regards,

    Niki


    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, November 28, 2011 9:44 AM
  • As suggested, I posted in the Server forum. I have not had any response yet.
    Mike Pietrorazio
    Monday, November 28, 2011 12:51 PM
  • Hi,

     

    I notice you posted to Windows Server Forums -> IPv6. Please post the thread through the link I provided above (Windows Server Forums -> Platform Networking). If you still don't receive any response, I will involve someone familiar with this topic to further look at this issue.

     

    Sorry for the inconvenience.

     

    Best Regards,

    Niki


    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, November 29, 2011 8:58 AM
  • I have re-posted there.
    Mike Pietrorazio
    Tuesday, November 29, 2011 12:10 PM
  • Hi,

     

    Since the post in Server Forum has started, I will close this one.

    http://social.technet.microsoft.com/Forums/en-US/winserverPN/thread/7cc214ff-3ff4-447d-979b-79072b383393/#5d6b636f-3352-46c3-b2ae-a16dee036002

    BTW,  we'd love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts.

     

    Best Regards,

    Niki


    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Edited by Niki Han Thursday, December 1, 2011 8:37 AM
    • Marked as answer by Niki Han Thursday, December 1, 2011 8:37 AM
    Thursday, December 1, 2011 7:36 AM