When I connect to our VPN server managed by our SBS2011 server, the IP address I get is in the range of 169.254.128.x. Our lan IP range is 192.168.0.x. Shouldn't the VPN ip address I get be in the same range as the local lan ? Access to to shares on the server itself from the vpn pc works fine, but I cannot ping any device on our local lan ip (192.168.0.x). Should the VPN wizard on the server reconfigure the proper ip settings, or use different method ?
This started happening after a major problem caused by Eset's uninstaller utility on the server. The normal uninstall did not work, so had to use their utility to cleanup the remainings of Eset. But after running it and rebooting the server, The uninstaller had reset all network cards, set to dhcp, etc etc. So AD was not working anymore, nwk cards were disabled, could not connect to the server anymore, quite a nightmare. Long story short, after putting back the ip address and network settings on the card, the server was finally functionnal and pc's could access it normally, with Exchange services, RWA, etc. The VPN seems to be the last item to fix back.
The only problem that remains is that name resolution does not work , except for the server name itself (which I am able to browse shared folders on it using its name and not having to use it's ip address). IE: I can vnc to a pc using the ip address but ping or vnc using the pc name will not work. Note: I did not enter anything in the vpn properties for DNS and Wins IP addresses.
Any idea ?