Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Sunday, July 30, 2017 12:53 AM
Hello, I am a volunteer for a small nonprofit organization that does not have the budget to pay for someone to configure and maintain the network. So i volunteer my time to do it for free. For the most part everything i know is self thought.
Back in October 2016 I set up a Windows Server 2016 server. Right now I am wanting to configure the DHCP to assign IPv6 addresses but there are several things that i'm completely confused about.
My first question is when I am configuring the IPv6 scope it asks me for a prefix. I understand what the prefix is in the IPv6 address but how do I know what prefix i should be using on our network.
The second question I have is once I get the scope set up do I need to do anything so that all the workstations can still communicate with Active Directory and DNS as well as still connect to the internet and be able to brows the local network?
Any and all help would be greatly appreciated.
Thanks.
All replies (3)
Monday, July 31, 2017 4:46 AM
Hi,
>>My first question is when I am configuring the IPv6 scope it asks me for a prefix. I understand what the prefix is in the IPv6 address but how do I know what prefix i should be using on our network.
The prefix is the part of the address that indicates which bits have fixed values or reflect the subnet identifier. Prefixes for IPv6 subnet identifiers and routes are expressed in the same way as Classless Inter-Domain Routing (CIDR) notation for IPv4, that is, in address/prefix-length notation. For example, 21DA:D3::/48 is a route prefix and 21DA:D3:0:2F3B::/64 is a subnet prefix.
More information about IPv6 , please refer to the following article:
https://technet.microsoft.com/en-us/library/cc755011%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396
The second question:
IPv6 runs alongside IPv4, so you will have to 'run' IPv6, but you won't be 'only running' IPv6 (I think this is what your concern is here). IPv6 doesn't interfere with existing IPv4 infrastructure, it just runs at the same time. In fact, if all your boxes are IPv6 capable, IPv6 is probably already running. It's not a new subnet exactly, it runs in parallel with IPv4.
If you just want to connect ipv6 website,you could refer to the follow article:
If you'd like your Intranet change to ipv6 resolving，you could follow the article below：
Please Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
There are some similar issues with you：
Best Regards,
Frank
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Thursday, August 3, 2017 8:33 AM
Hi,
Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.
Best Regards,
Frank
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, August 11, 2017 4:10 AM
Hi,
Was your issue resolved?
If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.
If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.
If no, please reply and tell us the current situation in order to provide further help.
Best Regards,
Frank
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].