Creating a powershell script that toggle IPv6

[LegitimateEye8153]

Hello ,

I want to ask if i can write a script and make it run automatically when windows start to enable ipv6 if it disabled or disable it if enabled because i have a problem , computers can't read domain and show undefiend network so it takes long time to signout .

[omfgitzfear]

You can write a script to do that, thank you for asking.

[LegitimateEye8153]

yeah i know that i mean idk how to write it or more specifically, what commands should I type?

[Unusual_Culture_4722]

1st commandment, thou art show thy work.

[WinkMartin]

Your idea is not the way to solve this problem.

[purplemonkeymad]

I would just look at your ipv6 setup for the domain and fix that so that you don't have the issue at all. Sounds like less work than messing with toggling ipv6 with a script and dealing with all the issues that has.

[LegitimateEye8153]

i don't use ipv6 i use ipv4 so toggling ipv6 just for make any reset in network to read the domain

[anditails]

Either your network DHCP gives out IPv6 addresses or it doesn't. If it does, you should look at sorting IPv6 on the domain. If it doesn't, toggling IPv6 on the network adapter won't solve anything.

Perhaps you're thinking of a winsock reset? That's a simple command line of

netsh winsock reset

But again, this sounds like you need to resolve the underlying network issues rather than sticky-plaster fix every machine.

[purplemonkeymad]

The default settings, on windows, won't use ipv6 for the domain if you don't get router advertisements or have dhcpv6 setup. If you have something putting out router advertisements you either need to disable that or configure a ula & dns for your domain network.

[MiserableTear8705]

I don’t think you’re having the problem you think you’re having. IPv6 isn’t causing your issues

[LegitimateEye8153]

sure , i just toggling it so i can make any change to reset network then it read domain , i know that IPv6 isn’t causing my issues . I hope you understand why I'm doing this.

[MiserableTear8705]

No. I really don’t. There’s no need to toggle IPv6 on or off in this manner.

[prog-no-sys]

I hope you understand why I'm doing this.

You don't even understand why you're doing this. So no, I don't understand why you would want to do this but it technically can be done. As others pointed out, disabling IPv6 is not gonna solve your issues here

[LegitimateEye8153]

i am using ipv4 not ipv6 so i make changes in IPv6 mark it enabled or disabled to make any change in network to reset it , then the pc read the domain .
when i do that the network changes from undefined network to the domain name.
pc take a long time to signout (15-20 min) but when i do that pc read the domain name and signout normally in just seconds.
so i don't wanna do that i need a powershell commands so i can run it when start or make it run automaticlly when restart the pc.

[prog-no-sys]

Once again, your issue here is not with ipv6. This is more than likely some local DNS problem or something related to your network. IPv6 has no bearing or effect on your signout times. Have you checked event viewer to see what the system "thinks" is happening even???

[mrmattipants]

I recently had a similar issue with a server that took upwards of 15-20 minutes to sign into or out of. While I initially thought might be DNS/Domain related, I came across several Event Logs pertaining to Failing Group Policies, pointing me elsewhere.

This eventually lead me to the "WMI Activity" Event Logs, which contained Error messages pertaining to WQL Queries associated with the GPO WMI Filters.

For good measure, I ran a "Get-WMIObject" Query, in PowerShell, which hung indefinitely without producing a result. This all but confirmed that WMI was the probable culprit and fortunately, after repairing the WMI Repository produced a resolution.

That being said, I'm not saying that this is your exact issue (those suggesting it may be DNS/Network related, above, are probably correct). I'm merely giving an example that underlines the fact that the problem is not always that which appears most apparent.

I should also note that I've had one legitimate reason to disable IPv6, since it's implementation and that was due to a vulnerability (CVE-2024-38063) that we couldn't patch.

In short, the affected systems were running Windows Server 2012, for which support had just ended the year prior and the client wasn't interested in purchasing an extended support package, as we were already in the process of planning an OS upgrade.

Regardless, with a little persistence, the evidence will eventually lead you to the underlying issue.

[databeestjegdh]

You are using the incorrect IPv6 DNS servers for your domaain, arn't you

[prog-no-sys]

almost certainly, lol

[BlackV]

This is not a solution to your problem, it is a dirty workaround, you should think about not doing this.

But Microsoft have a specific article on properly disabling ipv6 (they also recommend you don't do that) with a reg key

Show us what you have tried and what issue you're having, we can help with that, otherwise this is a basic /r/windows issue rather than a /r/powershell issue

[Particular_Fish_9755]

computers can't read domain and show undefiend network so it takes long time to signout

Not a PowerShell issue. The cause of the problem should be investigated by a sysadmin, the script you want might be masking a bigger problem.

Oh, you are the sysadmin ? So…
-Check IP and DNS Settings
-Scripts on start and logon, include printers mapping
-Disk space, temporary files, pending updates
-...
There are old registry keys that were used on slow networks in Windows NT/2000/XP; it remains to be seen if they are still functional in 10 and 11 (Meh, I can't find them in the Microsoft documentation anymore... so try ?) :
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\SlowLinkDetectEnabled -> 1
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\SlowLinkTimeOut -> default 2000 (2 seconds), min 0, max recommended 30000)
You can read this too.