Saturday, November 9, 2013

Windows Server 2012 - IPv6 - PING: transmit failed. General failure.

I thought I had demonstrated that Windows Server 2012 and Windows 7 clients could function in an all IPv6 network (with IPv4 disabled) - at least in the very small test environment I created.
 
In fact, this did work at one point. In previous blog posts, I was able to ping remote hosts using IPv6 addresses. I had disabled IPv4 to see if AD could function on IPv6 alone.
 
I realized something was wrong when I attempted to join a new server to the domain and was informed that:
 
"The domain "machlinkit.biz" could not be found."
 
I also noticed that on the Windows 7 client ("PC1"), the domain was not being detected and the Windows Firewall "Public" profile was being used. Yet this client was joined to the domain.
 
Re-enabling IPv4 restored network connectivity.
 
But I still cannot ping with IPv6.
 
At this point, I am working with only two nodes, both have the Windows Firewall disabled:
 
  • Windows Server 2012 (DC/GC,DNS,DHCP)
  • Windows 7 SP1 client
 
Moreover, nslookup seems to default to IPv6 and fails even with IPv4 re-enabled.

Here is the output of IPCONFIG , PING and NSLOOKUP:

C:\>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : PC1
   Primary Dns Suffix  . . . .  . : machlinkit.biz
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . .. : No
   DNS Suffix Search List. . . . . . : machlinkit.biz


Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : machlinkit.biz
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
   Physical Address. . . . . . . . . : 00-0C-29-F8-C0-46
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . : Yes
   IPv6 Address. . . . . . . . . . . : fd00::5495:a8c8:c79c:3c33(Preferred)
   Lease Obtained. . . . . . . . . . : Saturday, November 09, 2013 12:09:08 PM
   Lease Expires . . . . . . . . . . : Thursday, November 21, 2013 12:09:08 PM
   Link-local IPv6 Address . . . . . : fe80::e07e:50de:a86e:edc7%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 10.1.1.21(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.0.0.0
   Lease Obtained. . . . . . . . . . : Saturday, November 09, 2013 12:08:50 PM
   Lease Expires . . . . . . . . . . : Saturday, November 09, 2013 12:36:51 PM
   Default Gateway . . . . . . . . . : 10.1.1.4
   DHCP Server . . . . . . . . . . . : 10.1.1.10
   DNS Servers . . . . . . . . . . . : fd00::10
                                                 10.1.1.10

   NetBIOS over Tcpip. . . . . . . . : Enabled



C:\>ping 10.1.1.10

Pinging 10.1.1.10 with 32 bytes of data:
Reply from 10.1.1.10: bytes=32 time<1ms TTL=128
Reply from 10.1.1.10: bytes=32 time<1ms TTL=128
Reply from 10.1.1.10: bytes=32 time<1ms TTL=128
Reply from 10.1.1.10: bytes=32 time<1ms TTL=128

Ping statistics for 10.1.1.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms


C:\>ping fd00::10

Pinging fd00::10 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.

Ping statistics for fd00::10:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),




C:\>nslookup
Default Server:  UnKnown
Address:  fd00::10

> machlinkit.biz
Server:  UnKnown
Address:  fd00::10

*** UnKnown can't find machlinkit.biz: No response from server
>




I tried this command (on client PC1):

C:\>netsh int ipv6 show neighbors

Interface 1: Loopback Pseudo-Interface 1

Internet Address                              Physical Address   Type
--------------------------------------------  -----------------  -----------
ff02::c                                                          Permanent
ff02::16                                                         Permanent
ff02::1:2                                                        Permanent


Interface 13: Teredo Tunneling Pseudo-Interface

Internet Address                              Physical Address   Type
--------------------------------------------  -----------------  -----------
ff02::16                                      255.255.255.255:65535  Permanent
ff02::1:2                                     255.255.255.255:65535  Permanent


Interface 11: Local Area Connection

Internet Address                              Physical Address   Type
--------------------------------------------  -----------------  -----------
fd00::10                                      00-0c-29-5a-c2-c0  Stale
ff02::2                                       33-33-00-00-00-02  Permanent
ff02::c                                       33-33-00-00-00-0c  Permanent
ff02::16                                      33-33-00-00-00-16  Permanent
ff02::1:2                                     33-33-00-01-00-02  Permanent
ff02::1:3                                     33-33-00-01-00-03  Permanent
ff02::1:ff6e:edc7                             33-33-ff-6e-ed-c7  Permanent
ff02::1:ff9c:3c33                             33-33-ff-9c-3c-33  Permanent





Looks like the IPv6 address of the DC/DNS server is "stale".

If I disable IPv6, nslookup hesitates a second... then seems to resort to IPv4... and finds the DNS server for machlinkit.biz:

C:\>nslookup
DNS request timed out.
    timeout was 2 seconds.
Default Server:  UnKnown
Address:  10.1.1.10

> machlinkit.biz
Server:  UnKnown
Address:  10.1.1.10

Name:    machlinkit.biz
Addresses:  fd00::10
          fd00::24ec:9605:cca:cdad
          10.1.1.10





With the respective firewalls still disabled, I reboot both machines - and then re-enable IPv6 on the Windows 7 client.

Status changes to "reachable" but... still no ping.

C:\>netsh int ipv6 show neighbors

Interface 1: Loopback Pseudo-Interface 1

Internet Address                              Physical Address   Type
--------------------------------------------  -----------------  -----------
ff02::c                                                          Permanent
ff02::16                                                         Permanent
ff02::1:2                                                        Permanent


Interface 13: Teredo Tunneling Pseudo-Interface

Internet Address                              Physical Address   Type
--------------------------------------------  -----------------  -----------
ff02::16                                      255.255.255.255:65535  Permanent
ff02::1:2                                     255.255.255.255:65535  Permanent


Interface 11: Local Area Connection

Internet Address                              Physical Address   Type
--------------------------------------------  -----------------  -----------
fd00::10                                      00-0c-29-5a-c2-c0  Reachable
ff02::2                                       33-33-00-00-00-02  Permanent
ff02::c                                       33-33-00-00-00-0c  Permanent
ff02::16                                      33-33-00-00-00-16  Permanent
ff02::1:2                                     33-33-00-01-00-02  Permanent
ff02::1:3                                     33-33-00-01-00-03  Permanent
ff02::1:ff6e:edc7                             33-33-ff-6e-ed-c7  Permanent



C:\>ping fd00::10
Pinging fd00::10 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.

Ping statistics for fd00::10:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),





Then status goes to stale again:

C:\>netsh int ipv6 show neighbors

Interface 1: Loopback Pseudo-Interface 1

Internet Address                              Physical Address   Type
--------------------------------------------  -----------------  -----------
ff02::c                                                          Permanent
ff02::16                                                         Permanent
ff02::1:2                                                        Permanent


Interface 13: Teredo Tunneling Pseudo-Interface

Internet Address                              Physical Address   Type
--------------------------------------------  -----------------  -----------
ff02::16                                      255.255.255.255:65535  Permanent
ff02::1:2                                     255.255.255.255:65535  Permanent


Interface 11: Local Area Connection

Internet Address                              Physical Address   Type
--------------------------------------------  -----------------  -----------
fd00::10                                      00-0c-29-5a-c2-c0  Stale
ff02::2                                       33-33-00-00-00-02  Permanent
ff02::c                                       33-33-00-00-00-0c  Permanent
ff02::16                                      33-33-00-00-00-16  Permanent
ff02::1:2                                     33-33-00-01-00-02  Permanent
ff02::1:3                                     33-33-00-01-00-03  Permanent
ff02::1:ff53:5176                             33-33-ff-53-51-76  Permanent
ff02::1:ff6e:edc7                             33-33-ff-6e-ed-c7  Permanent




After an additional reboot of both machines, this time with IPv6 enabled at the time of reboot, the status is still "stale"

C:\>netsh int ipv6 show neighbors

[snip]
Interface 11: Local Area Connection

Internet Address                              Physical Address   Type
--------------------------------------------  -----------------  -----------
fd00::10                                      00-0c-29-5a-c2-c0  Stale



***

So far, my research on Internet has not yielded any solution. I suppose there are not many IPv6-only networks where this might be observed. Has anyone encountered this? Is there a solution?
 
Note: there is no router, IPv6 or other, in the network. Server and client are both guests running on VMware Workstation 9.

6 comments:

  1. I'm currently troubleshooting the same issue you're describing. Have you by any chance been able to resolve or further explain the behavior you observed?

    ReplyDelete
  2. I encountered same issue using HE tunnel in Win 7. I am stuck

    ReplyDelete
  3. status showing "stale" is not a problem it is by design..
    https://www.youtube.com/watch?v=rljkNMySmuM&list=PL7FBD333BAB233A44&index=1

    i am having the same issue though.. which is unable to ping with the generic failure :(

    ReplyDelete
  4. here is how you fix this and the logic:
    http://www.networkworld.com/community/blog/setting-dhcpv6-dynamically-issue-ipv6-address

    ReplyDelete
  5. Cool, thank you. Looks like I was missing my /64 route statement.

    ReplyDelete
  6. Thanks for the comments guys. I've since moved on to something else but it's good to see that the community effort is providing solutions to the readers.

    ReplyDelete