Sign in
Microsoft.com
 
Windows Server TechCenter
 
 
 
Windows Server TechCenter > Windows Server Forums > Platform Networking > IPv6 - PING: transmit failed, error code 1231.
Ask a questionAsk a question
Search Forums:
 

Proposed AnswerIPv6 - PING: transmit failed, error code 1231.

  • Tuesday, February 19, 2008 7:10 PMHallis Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    I have set up a small network to test IPv6. I have a couple of servers and clients running in a virtual environment and some clients running on physical computers. All computers get their IP address from DHCP. In the virtual environment everything about IPv6 seems to work as expected. But on the physical computers nothing seems to work (except DHCP). If I try to ping form a physical computer I get this error: "PING: transmit failed, error code 1231." What could be wrong?

     

    All servers are WS2008 RTM and clients are Vista and Vista SP1.

     

All Replies

  • Wednesday, February 20, 2008 7:23 PMHallis Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    If I add an IP address manually using "netsh interface ipv6 add address" on one of the physical computers it starts to work.

    Does adding an address manually also set other parameters that the DHCP config does not?

     
  • Monday, August 31, 2009 10:39 PMTore85MVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    It seems that the DHCPv6 server doesn't send what space (/64, /48) it should be using.

    I'm currently stuck with the same problem:
    • DHCPv6 works
    • Clients get IPv6 addresses from the server
    • Clients can ping their own IPv6 address
    • Clients cannot ping any other IPv6 addresses in the scope
     
  • Thursday, September 03, 2009 5:44 PMTore85MVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer
    Sign In to Vote
    0
    Sign In to Vote
    I found out after some searching that the prefix has to be advertised.

    Try doing this on your DHCPv6 server:
    Netsh interface ipv6 set interface <server_interface> advertise=enabled man=en other=en
    Netsh interface ipv6 add route 1024::/64 <server_interface> publish=yes

    This tells the other clients on the network that 1024::/64 is the route, and that they should get their IPv6 IP's from the DHCPv6 server.
    • Proposed As Answer byTore85MVPThursday, September 03, 2009 5:44 PM
    •  
     
  • Saturday, November 14, 2009 7:57 PMFlo.W. Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Hi,

    very nice, it works for me like this as well.

    Thanks Tore85!

    Just two questions left:

    1. what is "man=en and other=en" ? - I didnt need this I think.

    2. My DHCPv6 Server was configured with a static IPv6 address of course.
    But when restarting the machine it gets two addtional IPv6 addresses.
    One of the two addtional ones has a lease in the DHCP addresses (so it seems to be assigned by the DHCPv6 it self).
    The second additonal one - no idea?!
    But the one is used for name resolution.

    When I ping the DHCP from a DHCP client it will not resolve the static IP it resolves one of the two IPv6 addresses which have been generated automatically.

    Can somebody explain this behavior?

    For better understanding the IPv6 configuration of the DHCPv6 server itself (stateful mode):


    Windows IP Configuration

       Host Name . . . . . . . . . . . . : DC
       Primary Dns Suffix  . . . . . . . : azure-corp.local
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : azure-corp.local

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . : azure-corp.local
       Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Adapter
       Physical Address. . . . . . . . . : 00-15-5D-64-CE-00
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:db8:1234:5678::2(Preferred)
       IPv6 Address. . . . . . . . . . . : 2001:db8:1234:5678:9829:b13c:bf6c:421c(Preferred)
       IPv6 Address. . . . . . . . . . . : 2001:db8:1234:5678:c0d0:588d:c3b7:731b(Preferred)
       Lease Obtained. . . . . . . . . . : Saturday, November 14, 2009 6:37:28 PM
       Lease Expires . . . . . . . . . . : Thursday, November 26, 2009 6:37:27 PM
       Link-local IPv6 Address . . . . . : fe80::9829:b13c:bf6c:421c%11(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.137.2(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 234886493
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-6C-2D-D8-00-15-5D-64-CE-00
       DNS Servers . . . . . . . . . . . : 2001:db8:1234:5678::2
                                           127.0.0.1
       NetBIOS over Tcpip. . . . . . . . : Enabled
       Connection-specific DNS Suffix Search List :
                                           azure-corp.local

    Tunnel adapter isatap.{1393D377-C106-44C7-809C-6F23D0761932}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : azure-corp.local
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes


    Thanks very much!

    Best regards,
    Florian