Just a query, something odd is happeing when using WINS for name resolution. Once connected to the VPN, only two clients, the server and backup machine are resolving correctly (10.0.0.1 and 10.0.0.3 on my LAN).
These IPs are out of the DHCP scope, but so is my machine, 10.0.0.9. When doing a simple ping test, it comes back as 10.0.0.10. And every other machine resovles out to an IP one up from what is should be ie. if the IP was to be 10.0.0.99, and pinging it using WINS, it will resolve out to 10.0.0.100.
There isn't anything wrong with WINS as it works fine in the office, just not from the VPN connection. Any ideas or suggestions?
Also, there seems to be a very short idle timeout of about 30 seconds to a minute. If no traffic is flowing over the VPN connection, and for lack of better words, it goes stale and no traffic is sent back, but I can see traffic being sent... odd. Ideas?
Regards,
James
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all,
Just a query, something odd is happeing when using WINS for name resolution. Once connected to the VPN, only two clients, the server and backup machine are resolving correctly (10.0.0.1 and 10.0.0.3 on my LAN).
These IPs are out of the DHCP scope, but so is my machine, 10.0.0.9. When doing a simple ping test, it comes back as 10.0.0.10. And every other machine resovles out to an IP one up from what is should be ie. if the IP was to be 10.0.0.99, and pinging it using WINS, it will resolve out to 10.0.0.100.
There isn't anything wrong with WINS as it works fine in the office, just not from the VPN connection. Any ideas or suggestions?
Also, there seems to be a very short idle timeout of about 30 seconds to a minute. If no traffic is flowing over the VPN connection, and for lack of better words, it goes stale and no traffic is sent back, but I can see traffic being sent... odd. Ideas?
Regards,
James