MAPI and IPv6

Duncan Smith noted recently that MAPI appears to have a problem with IPv6. He contacted me to see if I knew anything about the issue. I didn’t, but one of the Exchange PMs spotted the connection between Duncan’s issue and the recently reported DSProxy issue over on the Ehlo blog. It turns out that issue affects regular MAPI connections – not just RPC/HTTP.

The gist is – right now, DSProxy doesn’t listen on IPv6. It only listens on IPv4. So if you’re running a MAPI client on an IPv6 enabled box (such as, say, installing the MAPI download on an IPv6 enabled Exchange 2007 server), then profile creation is going to fail when the client tries to ask the server for a referral to a GC.

As the Ehlo article notes, a fix is in the works. Until then, you can try one of the following:

  • Turn off IPv6 on your server – Ehlo gives instructions for that – this has been confirmed to work .
  • When creating a MAPI profile, instead of using the Exchange server name, use the name of a GC or DC. We’ve not had a chance to test this yet – we’d love to hear if someone tried it and it worked.
Comments (4)

  1. X says:


    Its strange that you mention that Dsproxy doesnot listen on IPV6 because i have seen a LOT of instances of the Outlook anywhere bug but in almost all of those scenarios, a regular mapi profile doesnot have any issues connecting.

  2. The IPv6 issue only affects MAPI clients if both the MAPI client and the server are on IPv6 boxes. The Outlook Anywhere issue can happen when just the server is on IPv6. So – not strange.

  3. I had another issue recently where MAPI wasn’t able to connect via NSPI to the Exchange server or DC.

  4. X says:

    i read the other blog you wrote about ipv6 issues continuing to re-surface even after applying RU5 (which supposedly had a fix for this bug) and i have seen some instances myself.

    P.S abt the earlier comment, i missed out the fact that the client has to be ipv6 🙂 i realized this when i stumbled upon the issue once