Windows 10 Pro (1903) Server, "Unidentified" network...

[A_Pickle]

Server config: Running OpenVPN 2.4.8

Code: Select all

port 1194
proto udp
dev tun
ca ca-chain.pem
cert serv.crt
key serv.pem  # This file should be kept secret
dh dh2048.pem
server 172.20.88.0 255.255.255.0
client-config-dir ccd
push "route-metric 512"
push "route 0.0.0.0 0.0.0.0"
keepalive 10 120
tls-auth ta.key 0 # This file is secret
cipher AES-256-CBC
comp-lzo
persist-key
persist-tun
status openvpn-status.log
log openvpn.log
verb 3

Client config: Running OpenVPN 2.4.8

Code: Select all

client
dev tun
proto udp
remote-cert-tls server
remote 192.168.1.1 1194
resolv-retry infinite
nobind
ca ca-chain.pem
cert client.crt
key client.pem
tls-auth ta.key 1
cipher AES-256-CBC
compress lz4
status openvpn-status.log
log openvpn.log
verb 3

I was under the impression that the push "route-metric 512" and push "route 0.0.0.0 0.0.0.0" in the server config would give all connecting Windows clients a default gateway, and thus evade the "Unidentified Network" problem. That does not appear to be the case anymore - the server is content with the VPN and is showing it as a private network, but clients are automatically connecting and seeing an "Unidentified Network" where they used to prompt the user, asking if the newly-detected network was a private or public network. How do I restore this behavior?

[AdrianG001]

Server config: Running OpenVPN 2.4.8

Code: Select all

port 1194
proto udp
dev tun
ca ca-chain.pem
cert serv.crt
key serv.pem  # This file should be kept secret
dh dh2048.pem
server 172.20.88.0 255.255.255.0
client-config-dir ccd
push "route-metric 512"
push "route 0.0.0.0 0.0.0.0"
keepalive 10 120
tls-auth ta.key 0 # This file is secret
cipher AES-256-CBC
comp-lzo
persist-key
persist-tun
status openvpn-status.log
log openvpn.log
verb 3

Client config: Running OpenVPN 2.4.8

Code: Select all

client
dev tun
proto udp
remote-cert-tls server
remote 192.168.1.1 1194
resolv-retry infinite
nobind
ca ca-chain.pem
cert client.crt
key client.pem
tls-auth ta.key 1
cipher AES-256-CBC
compress lz4
status openvpn-status.log
log openvpn.log
verb 3

I was under the impression that the push "route-metric 512" and push "route 0.0.0.0 0.0.0.0" in the server config would give all connecting Windows clients a default gateway, and thus evade the "Unidentified Network" problem. That does not appear to be the case anymore - the server is content with the VPN and is showing it as a private network, but clients are automatically connecting and seeing an "Unidentified Network" where they used to prompt the user, asking if the newly-detected network was a private or public network. How do I restore this behavior?

Try any one of the below methods

Method 1. Windows 10 Unidentified Network Caused by Hardware
Firstly, make sure there are no problems with the network-related hardware, like the router, the network card, USB wireless dongle, etc., which should be checked just in case you waste time on other useless computer operations. Reconnect the network cables. Restart the wireless router and the modem. Also make sure the network card sits right in the port.

Method 2. Turn off the Airplane Mode on Windows 10 Fall Creators Update / Creators Update / Anniversary Update
Windows airplane mode is the special networking setting that can control the wireless signal receiving. Windows 10 airplane mode on and off errors will also affect the network connection and result in the Windows 10 unidentified network issue. Turn off or disable the airplane mode if you want a normal network connection.

Let me know how it helps.