Windows Firewall WS2016 Won't Accept IPv6 Loopback IP

Windows Firewall on Windows Server 2016: Unable to Set IPv6 Loopback Address Inbound Rule - Scope - Local IP Address

Windows Firewall is a critical component of Windows Server 2016, providing protection against unauthorized access to the system. However, some users have reported an issue where they are unable to set the IPv6 loopback address inbound rule for the scope of the local IP address.

Understanding the Problem

The IPv6 loopback address, also known as the localhost address, is a special address that always refers to the local machine. It is used for testing and development purposes, as well as for certain network services. In Windows Firewall, you can create inbound rules to allow or block traffic based on the source and destination IP addresses.

However, some users have reported that when they try to create an inbound rule for the IPv6 loopback address, they are unable to set the scope to the local IP address. The error message they receive states that "an error occurred verifying in...". This can be frustrating, as it prevents them from properly configuring their firewall settings.

Possible Solutions

There are a few possible solutions to this problem. One is to use the IPv4 loopback address instead of the IPv6 loopback address. This can be done by creating an inbound rule for the IPv4 address of 127.0.0.1, which is the equivalent of the IPv6 loopback address.

Another solution is to use a wildcard in the source address field of the inbound rule. This can be done by entering an asterisk (*) in the source address field, which will match any source address. This will allow traffic from any source address, including the IPv6 loopback address, to be accepted by the inbound rule.

If these solutions do not work, it may be necessary to manually edit the Windows Firewall configuration using the netsh command-line tool. This can be done by opening a command prompt and entering the following command:

This command will create a new inbound rule called "Loopback" that allows traffic from the IPv6 loopback address (::1) on the TCP protocol. This should allow traffic from the IPv6 loopback address to be accepted by the firewall.

The issue of being unable to set the IPv6 loopback address inbound rule for the scope of the local IP address in Windows Firewall on Windows Server 2016 can be frustrating, but there are a few possible solutions. By using the IPv4 loopback address, using a wildcard in the source address field, or manually editing the Windows Firewall configuration using the netsh command-line tool, users can properly configure their firewall settings and allow traffic from the IPv6 loopback address.

References

• Microsoft. (2017). Windows Server 2016: Configure a Windows Firewall Inbound Rule. Retrieved from
• Microsoft. (2017). Netsh Commands for Windows Firewall with Advanced Security. Retrieved from