![]() ![]() I skipped most of the commands except for the two below, since RRAS was already set to do routing for IPv6. You still need to run these commands below. Enabled routing in RRAS, same goes for setting the prefix, and setting it to advertise doesn't work. In a home lab I have setup a windows RRAS server that is doing ipv6 routing. Is this the usual idea when using DHCPv6, or am I missing something? ![]() The 2 normal addresses probably means that one of the 2 is done via auto-configuration. 2 normal addresses, one temporary and one link-local. I've now got IPv6 running, the only issue I face is that somehow the client gets 4 IPv6 addresses. Besides that, the "Managed" and "Otherstateful" flags need to be activated to enable DHCPv6. I'll look into this and will post a follow-up.Įdit 2: It seems that router advertisements are needed to publish a route on the network. It also seems that I have to some router advertising with netsh. Pinging link-local addresses works, from server to client and vice-versa. ![]() Resetting the IP stack on the workstation ("netsh int ip reset" and "netsh int ipv6 reset") doesn't help either.Įdit: It seems that the route isn't added on the client. I use fd48:5884:e6ae:e8e9::/64 as a prefix, fd48:5884:e6ae:e8e9::1 is the DNS server, the workstation has a dynamic address assigned by DHCPv6. Since this is a test network I've disabled the firewalls, but this does not change the situation. If I ping from the DC to the workstation I get a "Request timed out". But once I ping using Ping -6 I get " PING: transmit failed. DHCPv6 works without a problem, the client gets an IPv6 address assigned and the DNS Server address is delivered as well. IPv6 on the other hand is acting strange. IPv4 connectivity works fine, no problems here. I've got one VM as Windows 7 RTM 圆4, as a domain member. I've setup one VM as a DC, with 2008 R2 Standard Edition, AD, DNS and DHCP. I'm testing a IPv6 setup using Hyper-V on 2008 R2. ![]()
0 Comments
Leave a Reply. |