none
Windows 7 loses IPv6 address after ~5 minutes

    Pertanyaan

  • Hiya,

    My problem is that my Windows 7 PC loses its IPv6 Link-local address, which its gained from a DHCP server after about 5 minutes.

    I have an Astaro Security Gateway V8 (8.305) with a IPV6 (and 4) DHCP server(s) set up.

    It distributes IP addresses from FE80::F000 to FE80:FFFF and the lease time is 30 days. Confirmed with ipconfig /all.

    After +- 5 minutes my netmon trace states my PC is asking for a address release of my gotten FE80::FC37 address... And of course my DHCP server complies and let my PC release it. (DHCPV6:MessageType = RELEASE)

    First its:

    -------------------------------------------------------------------------

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller #2
       Physical Address. . . . . . . . . : 40-61-86-F4-62-4D
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::fc37%12(Preferred)
       Lease Obtained. . . . . . . . . . : dinsdag 3 juli 2012 21:05:37
       Lease Expires . . . . . . . . . . : donderdag 2 augustus 2012 21:05:37
       Link-local IPv6 Address . . . . . : fe80::4071:4a82:3b08:5c83%12(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.13(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : fe80::3246:9aff:fe45:4dee%12
                                           fe80::1%12
                                           192.168.1.254
       DHCPv6 IAID . . . . . . . . . . . : 306209158
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-1E-72-63-40-61-86-F4-62-4C

       DNS Servers . . . . . . . . . . . : fe80::1%12
                                           192.168.1.254
                                           4.4.8.8
       NetBIOS over Tcpip. . . . . . . . : Enabled

    -------------------------------------------------------------------------

    And then 5 minuts later:

    -------------------------------------------------------------------------

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller #2
       Physical Address. . . . . . . . . : 40-61-86-F4-62-4D
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::4071:4a82:3b08:5c83%12(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.13(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : fe80::3246:9aff:fe45:4dee%12
                                           fe80::1%12
                                           192.168.1.254
       DHCPv6 IAID . . . . . . . . . . . : 306209158
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-1E-72-63-40-61-86-F4-62-4C

       DNS Servers . . . . . . . . . . . : fe80::3246:9aff:fe45:4dee%12
                                           192.168.1.254
                                           4.4.8.8
       NetBIOS over Tcpip. . . . . . . . : Enabled

    -------------------------------------------------------------------------

    And this cycle repeats at least when i´m accessing my NAS web interface over IPv6.

    And lastly as recommended on TechEd 2012, I disabled all IPv6 tunneling protocols: teredo, 6to4 and isatap on my LAN adapter.

    Any insights?

    Thanks!

    04 Juli 2012 13:29

Jawaban

  • Hi,

    Based on my knowledge, IPv6 link-local addresses are a special scope of address which can be used only within the context of a single layer two domain. Packets sourced from or destined to a link-local address are not forwarded out of the layer two domain by routers. These addresses are useful for establishing communication across a link in the absence of a globally routable prefix or for intentionally limiting the scope of traffic which should not be routed (for example, routing protocol advertisements).

    So, I don't think it will be leased by DHCP. This IP address is likely to the 169.254.x.x (IPv4), and it was allocated as the reservation in the system. Where can you find it was leased by DHCP?

    Could you please upload the network trace for us? Or Paste it here for the clarification?

    Thank for your help.

    Best Regards,

    Annie Gu

    10 Juli 2012 9:33

Semua Balasan

  • Buggy network driver?
    04 Juli 2012 14:30
  • I hope not, it's an about one year old mobo: http://eu.msi.com/product/mb/890FXA-GD70.html

    When I set an address in there manually it's working just fine.

    04 Juli 2012 15:41
  • Hi,

    First, please update your network adapter driver, chipset, BIOS from computer manufacturer's website. Then, open an elevated command, type the following commands.

    netsh winsock reset
    netsh interface ipv6 reset
    ipconfig /flushdns


    Niki Han

    TechNet Community Support

    05 Juli 2012 2:59
  • Thanks, I will look at that.

    I will also look at a thing that came up on my own research that I want to share with the group. I used a FE80::/64 address range while this is supposed to be the APIPA of IPv6. I should have used FC00::/7 as my 'private range' DHCP scope. Maybe this has something to do with my problem. I will check.

    But first... my vacation :)

    06 Juli 2012 15:35
  • netsh winsock reset

    netsh interface ipv6 reset
    ipconfig /flushdns

    First of all: thanks for helping.

    Well, before I go on vacation I did some tests anyway :)

    I updated all drivers from mobo to networkcard.

    I did all commands asked. No joy. Even after netsh winsock reset I had to reboot my pc, not quite unexpected. But after that a lot of networking tools crashed. Even ipconfig /all!

    After a reboot (again) things started working again.

    Now I am trying my own idea, but no luck with that either...

    A fixed address does work, just not a DHCP one.

    06 Juli 2012 19:39
  • Hi,

    Based on my knowledge, IPv6 link-local addresses are a special scope of address which can be used only within the context of a single layer two domain. Packets sourced from or destined to a link-local address are not forwarded out of the layer two domain by routers. These addresses are useful for establishing communication across a link in the absence of a globally routable prefix or for intentionally limiting the scope of traffic which should not be routed (for example, routing protocol advertisements).

    So, I don't think it will be leased by DHCP. This IP address is likely to the 169.254.x.x (IPv4), and it was allocated as the reservation in the system. Where can you find it was leased by DHCP?

    Could you please upload the network trace for us? Or Paste it here for the clarification?

    Thank for your help.

    Best Regards,

    Annie Gu

    10 Juli 2012 9:33
  • Hi,

    I would like to know if you have any update about this issue?

    If you have any concern, please feel free to let me know.

    Thanks.

    Best Regards,

    Annie Gu

    13 Juli 2012 6:35