alphahoogl.blogg.se - Viscosity vpn getting 169 ip address

#Viscosity vpn getting 169 ip address windows 10

Have the local VPN endpoint NAT the connection.

The crazy stuff some people come up with.Īt any rate, there's two possibilities I can think of, one (or both) of which might work depending on exactly how this misguided attempt at. How "I know your IP and MAC address" is an authentication mechanism just boggles the mind. The company we got it from said if we can make it work with a remote machine, that would be perfectly fine. I guess it needs to be as if I'm sitting there on the actual network with a physical MAC.Īlso, before you ask, no I am not doing anything illegal or out of bounds for the software we purchased.

#Viscosity vpn getting 169 ip address windows 10

Is there any hardware, or any kind of configuration that will allow me to have an actual MAC address on the network when I'm connected via VPN? I'm currently using Windows 10 PRO on the remote machine and using its built in VPN connector feature to connect to the Domain. But because this remote computer is connected via VPN, remotely, it fails to "Resolve" the MAC address. However, the server software is programmed to resolve both the IP and the MAC address of any connecting client machines. However, I have a remote computer which I have connected to the network via VPN through the router, and I've joined the Windows Domain using this method. Everything works just fine when 6 of the client computers, which are on the same local network as the server, connect to server and use the software.

This software requires there be a server, and workstations that connect to the server in order to run the client software.įor authentication purposes, when the client software tries to connect to the server, the asks for the client's IP and MAC addresses. I run a small business and I have purchase an inventory software.