Jordan4501
I'm running OpenVPN server on one of my domain-connected Windows Server 2012R2 machines. This install is from a while ago, and it has one TAP adapter for the server. When I start up the OpenVPN server, that adapter identifies its network as the internal domain network. This is all good and happy.
I recently added a second TAP adapter so I could have a TCP server running at the same time (the first one is UDP). With this adapter, however, when the OpenVPN server starts up it says it's on an "unidentified network", which is causing all sorts of connectivity nightmares. This has something to do with the TAP adapter itself and nothing to do with the OpenVPN config file (because if I use the old UDP config file from the original install, it still doesn't work). Some previous admin did something on the network to make my domain controller recognize that first TAP adapter as a domain-authenticated device, and I cannot seem to figure out how to do the same with my new TAP adapter. Any advice on this?
It's a Windows network with a DNS server, DHCP server, and Active Directory / Domain Control server.