Announcement

Collapse
No announcement yet.

Exchange 2007 can't acquire IPv6 address from ISATAP

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Exchange 2007 can't acquire IPv6 address from ISATAP

    Hi everyone!
    I'm sory for posting this message in two forums, but this is because I don't know whether the problem is with the Exchange Server 2007 SP1 or with Windows Server 2008 SP2 on which Exchange Server is installed.

    I am implementing DirectAccess in my company and I 'm having a problem with the Exchange 2007.

    DirectAccess server is configured as ISATAP router and it managed to configure all servers and clients in the network with the IPv6 addresses. The only problem is with Exchange Server 2007 which is installed on the Windows Server 2008 SP2. That server appears as IPv6 enabled, but when I ping it from another IPv6-enabled server it returs only IPv4 address.
    How can I make this server (exchange) acquire ISATAP address from the DirectAccess server?

    I have to mention that I deleted the registry key that disables IPv6 protocol in Windows Server 2008. That key was there because Exchange had no Service Pack. That Exchange server currently has SP1 installed.

    In the attached files you can see ipconfig/all output on two servers:
    Hyper1 is first domain controller and it has valid IPv6 address. (2002:c3fc:6bb4:1:0:5efe:192.168.21.11)
    Exchange is the Exchange Server 2007 SP1 server. It doesn't have ISATAP address configured. It only has Link-local IPv6 Address (fe80::21c9:4054:6cb1:b3de%10). Also, in the Exchange.txt file you can see the netsh configuration of ISATAP adapter.

    To explain the problem further, DirectAccess server is successfully configured, I can access resource on the internal network from the Internet. The only problem is with the Exchange Server which can't acquire IPv6 address. When I logon to exchange server and ping localhost I get reply from 127.0.0.1.

    When I ping exchange I get this:
    C:\Windows\system32>ping exchange

    Pinging Exchange.domain.com [fe80::21c9:4054:6cb1:b3de%10] from fe80::21c9:4054:6
    cb1:b3de%10 with 32 bytes of data:
    Reply from fe80::21c9:4054:6cb1:b3de%10: time<1ms
    Reply from fe80::21c9:4054:6cb1:b3de%10: time<1ms
    Reply from fe80::21c9:4054:6cb1:b3de%10: time<1ms
    Reply from fe80::21c9:4054:6cb1:b3de%10: time<1ms

    Ping statistics for fe80::21c9:4054:6cb1:b3de%10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

    When I ping exchange from some other server I get this:
    C:\>ping exchange

    Pinging Exchange.domain.com [192.168.21.33] with 32 bytes of data:
    Reply from 192.168.21.33: bytes=32 time<1ms TTL=128
    Reply from 192.168.21.33: bytes=32 time<1ms TTL=128
    Reply from 192.168.21.33: bytes=32 time<1ms TTL=128
    Reply from 192.168.21.33: bytes=32 time<1ms TTL=128

    Ping statistics for 192.168.21.33:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
    Attached Files
    Last edited by srdjan; 22nd July 2010, 14:44.

  • #2
    Re: Exchange 2007 can't acquire IPv6 address from ISATAP

    Please do not double post. If there's an issue w/ Exchange 2007 after the IP resolution issue gets fixed then we can either split the relevant posts of the thread to each issue or move the whole thread over if deemed necessary.
    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment


    • #3
      Re: Exchange 2007 can't acquire IPv6 address from ISATAP

      OK, sorry.

      Now, ISATAP is connected, but still doesn't get the IPv6 address from DirectAccess server. What could be the problem? The other hosts on the network get the 2002:::::... IP address, so ISATAP interface is correctly advertasing settings to the network hosts...

      C:\>ipconfig /all
      Windows IP Configuration
      Host Name . . . . . . . . . . . . : Exchange
      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 . : domain.com
      Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Ada
      pter
      Physical Address. . . . . . . . . : 00-15-5D-15-1F-02
      DHCP Enabled. . . . . . . . . . . : No
      Autoconfiguration Enabled . . . . : Yes
      Link-local IPv6 Address . . . . . : fe80::21c9:4054:6cb1:b3de%10(Preferred)
      IPv4 Address. . . . . . . . . . . : 192.168.21.33(Preferred)
      Subnet Mask . . . . . . . . . . . : 255.255.255.0
      Default Gateway . . . . . . . . . : 192.168.21.254
      DHCPv6 IAID . . . . . . . . . . . : 184554845
      DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-11-CC-98-07-00-15-5D-15-1F-00
      DNS Servers . . . . . . . . . . . : 127.0.0.1
      192.168.21.11
      NetBIOS over Tcpip. . . . . . . . : Enabled
      Tunnel adapter Local Area Connection* 8:
      Connection-specific DNS Suffix . : domain.com
      Description . . . . . . . . . . . : isatap.domain.com
      Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
      DHCP Enabled. . . . . . . . . . . : No
      Autoconfiguration Enabled . . . . : Yes
      Link-local IPv6 Address . . . . . : fe80::5efe:192.168.21.33%11(Preferred)
      Default Gateway . . . . . . . . . :
      DNS Servers . . . . . . . . . . . : 127.0.0.1
      192.168.21.11
      NetBIOS over Tcpip. . . . . . . . : Disabled
      C:\>

      Comment

      Working...
      X