republican-creole
site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Uniqs:
156
Share Topic
Posting?
Post a:
Post a:
Links: ·MS Apps FAQ ·Windows XP FAQ ·Windows 7 FAQ ·Windows Home ·Office Home
AuthorAll Replies


janderso1
Jim
Premium,MVM
join:2000-04-15
Saint Petersburg, FL

2 edits

Help-Windows 7 PC fails to use DHCPv6

I have a notebook PC that uses auto configuration instead of DHPv6. The problem with this is it doesn’t get the IPv6 name servers. Other Windows 7 PCs on the same subnet use DHCPv6 so I believe the router (DHCPv6 server) is configured correctly. I am using a /64 subnet of the /48 tunnel assigned to me by Hurricane Electric. My router is a Zyxel USG 50 which handles the tunnel and is the DHCPv6 server. The IPv6 address it uses is within the /64 so it is getting it from my DHCPv6 server/router.

C:\Users\janderso>netsh int ipv6 show int 14

Interface Wireless Network Connection Parameters
----------------------------------------------
IfLuid : wireless_0
IfIndex : 14
State : connected
Metric : 25
Link MTU : 1480 bytes
Reachable Time : 33500 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 1
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : enabled
Router Discovery : enabled
Managed Address Configuration : enabled
Other Stateful Configuration : enabled
Weak Host Sends : disabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 64
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled

Link-local IPv6 Address . . . . . : fe80::a09e:8e1d:2703:62e7%14(Preferred)
IPv4 Address. . . . . . . . . . . : xx.yy.zz.211(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::ca6c:87ff:fe36:f82e%14
xx.yy.zz.1
DHCPv6 IAID . . . . . . . . . . . : 357362498
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-70-0C-67-84-8F-69-CD-AD-18

DNS Servers . . . . . . . . . . . : 65.32.5.111
65.32.5.112
xx.yy.zz.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{5B7EF111-0565-43A3-A08E-D527966C82AE}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yesipconfig /all

C:\Users\janderso>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : NB3
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Centrino(R) Wireless-N 1030
Physical Address. . . . . . . . . : 4C-EB-42-40-D5-0D
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:xxxx:yyyy:2:a09e:8e1d:2703:62e7(Prefe
rred)
Temporary IPv6 Address. . . . . . : 2001:xxxx:yyyy:2:19ff:ecd9:6b1d:17a4(Prefe
rred)
--
Jim Anderson


janderso1
Jim
Premium,MVM
join:2000-04-15
Saint Petersburg, FL

How do you change the Windows 7 DHCPv6 timeout?
It now looks like DHCPv6 timeout problem. Either my router takes longer to respond to a DHCPv6 request or Windows 7 has a shorter timeout for DHCPv6 vs. DHCP (v4). I have two wireless access points configured as access point plus repeater (WDS) for better wireless coverage. The first access point has a gigabit wired connection to the router. The second access point connects wirelessly to the first. The PC that wasn’t using DHCPv6 was wirelessly connected with the second access point. Apparently the two wireless hops add too much delay and Windows 7 uses auto configuration. My hopefully temporary work around is to power down the second access point. This caused the problem PC to connect wirelessly to the first access point and it was able to get its IPv6 address and name servers via DHCPv6.
--
Jim Anderson


Monday, 08-Apr 06:41:26 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 13.5 years online © 1999-2013 dslreports.com.
Most commented news this week
Hot Topics