locked
Creating a new IPv6 DHCP Scope on Windows Server 2008 RRS feed

  • Question

  • I am trying to create a new ipv6 DHCP Scope however I do not know what is an acceptable DHCP Scope and Prefix. Can someone please help me with this?

    I also currently have unknown being listed on nslookup as the server at the moment and it is listing the ipv6 address for the server as the default so I am hoping that doing the above will also fix this error.

    Any help will be appreciated.
    I.T. Construct admin@itconstruct.com.au http://itconstruct.com.au
    Monday, August 10, 2009 5:15 AM

Answers

All replies

  • BUMP.. Can someone please help me!

    I am running Windows Server 2008 Enterprise x64 in a AD Environment.

    I.T. Construct admin@itconstruct.com.au http://itconstruct.com.au
    • Edited by itconstruct Tuesday, August 11, 2009 12:17 AM
    Tuesday, August 11, 2009 12:16 AM
  • Hi,

     

    The prefix is the part of the address that indicates the bits that have fixed values or are the bits of the network identifier. Prefixes for IPv6 routes and subnet identifiers are expressed in the same way as Classless Inter-Domain Routing (CIDR) notation for IPv4.

     

    The following articles could be helpful for you to better understanding IPv6 addressing:

     

    Expressing IPv6 addresses

    http://technet.microsoft.com/en-us/library/cc784831(WS.10).aspx

     

    Configuring IPv6 prefix addresses

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

     

    IPv6 configuration methods

    http://technet.microsoft.com/en-us/library/cc779656(WS.10).aspx

     

    IPv6 address autoconfiguration

    http://technet.microsoft.com/en-us/library/cc778502(WS.10).aspx

     

    Hope it helps.


    This posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked as answer by Joson Zhou Tuesday, August 18, 2009 10:14 AM
    Friday, August 14, 2009 7:29 AM
  • I have a similar issue.

    My DHCP for IPv6 is set, and my reverse lookup zone.

    My 2 DC's with static IPv6 addresses and NSLOOKUP any client/server and can only ping eachother.

    Clients cant NSLOOKUP (Server Unknown) or ping, just times out. But they do get assigned the IPv6 IP within the scope...

     

     

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : HYPERV01
       Primary Dns Suffix  . . . . . . . : mba.local
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : mba.local

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . : mba.local
       Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS
     VBD Client)
       Physical Address. . . . . . . . . : A4-BA-DB-39-2E-B0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : fc00:1234:5678:9abc::2(Preferred)
       IPv6 Address. . . . . . . . . . . : fc00:1234:5678:9abc:f000:a86d:d8ac:4d35(P
    referred)
       Lease Obtained. . . . . . . . . . : Monday, May 02, 2011 6:31:51 PM
       Lease Expires . . . . . . . . . . : Saturday, May 14, 2011 6:31:50 PM
       Link-local IPv6 Address . . . . . : fe80::c43:e88b:d97:c95c%15(Preferred)
       IPv4 Address. . . . . . . . . . . : 10.53.11.50(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : fc00:1234:5678:9abc::
                                           10.53.11.201
       DHCPv6 IAID . . . . . . . . . . . : 363117275
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-BF-01-7D-A4-BA-DB-39-2E-AA

       DNS Servers . . . . . . . . . . . : fc00:1234:5678:9abc::2
                                           fc00:1234:5678:9abc::3
                                           10.53.11.150
                                           10.53.11.50
       NetBIOS over Tcpip. . . . . . . . : Enabled
       Connection-specific DNS Suffix Search List :
                                           mba.local

    Tunnel adapter isatap.{DFA541A7-C114-4132-BB1A-BA6D83B973EF}:

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

    Tunnel adapter Teredo Tunneling Pseudo-Interface:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    C:\Users\HYPERV01>

     

    C:\Users\HYPERV01>nslookup hyperv02
    Server:  hyperv01.mba.local
    Address:  fc00:1234:5678:9abc::2

    Name:    hyperv02.mba.local
    Addresses:  fc00:1234:5678:9abc::3
              10.53.11.150
              10.53.11.151


    C:\Users\HYPERV01>ping hyperv02

    Pinging hyperv02.mba.local [fc00:1234:5678:9abc::3] with 32 bytes of data:
    Reply from fc00:1234:5678:9abc::3: time<1ms
    Reply from fc00:1234:5678:9abc::3: time<1ms
    Reply from fc00:1234:5678:9abc::3: time<1ms

    Ping statistics for fc00:1234:5678:9abc::3:
        Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms
    Control-C
    ^C
    C:\Users\HYPERV01>

     

     

    Any help would be great.

    Tuesday, May 3, 2011 1:34 AM
  • Cyban,

     

    i am having the same issue.

     

    did you manage to resolve this issue? if yes - can you please let me know how?

     

    thanks

     

    jack

     

    Monday, September 12, 2011 12:51 PM