This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

IPv6 takes down my domain every 2 days

Every two days or so, everything goes down hard.  I can't even log into servers, I have to use machine-local accounts to logon locally and reboot them.  Then everything is lightning fast and responsive for another 48 hours or so until it all fails again.  When they fail, everything stops working.  I can't even open powershell.  Resource manager shows CPU and Network utilization at 0%.  There is nothing running on the domain controllers except normal A/D services.

Today I saw that the domain controllers IP addresses have a subnet prefix length of 128, even though I statically assigned them as 64.  They have global ipv6 addresses.  As soon as one reboots, it's back to 128 again, and I have to log in locally and change it back to 64.

Another problem, though not fatal, is I notice that ALL local IPv6 traffic is routed over the UTM, even though machines are in the same /64 subnet on the same vlan.  I can't figure that one out.

I have UTM configured to hand out IPv6 with DHCPv6 and workstations seem to be configured correctly.  The workstations are all DHCP.

I have been at this for 3 days now and I can't figure out what's going on.  Where do I start?



This thread was automatically locked due to age.
  • It's definitely UTM that's doing this.  Every time a server restarts, it gets it's static ipv6 address that I entered, plus a DHCPv6 address from UTM, which I do not want.  I have turned off "advertising, router discovery, managed address configuration, etc" on the server, yet it is STILL getting bogus address information from the UTM.

    How can I stop it?

    I can't shut off prefix advertisements from UTM or that will break all my workstations.

    Right now, I have to manually login to every server and remove all the junk after each restart.

  • Well, my fix was to disable IPv6 Prefix Advertisements and DHCPv6 on the UTM and then configure the networks manually.

    So, no one else is having this problem?

     

    UTM is incorrectly sending prefix advertisements with /128 prefixes - this cannot work and there doesn't appear to be any way to change it.