J
Julie
We have a setup here where an XP Pro machine acts as
host for a single incoming VPN connection from another XP machine.
On the remote box, the "use default gateway on host" isn't checked
(to permit Internet use while the VPN is running.) So the IP address
handed out to the remote box by the VPN server has no gateway specified.
Because of this, we can't access the host by it's name, such as \\HOST.
However, we can access it by using its IP address, such as \\167.254.25.254.
The trouble is that the host's private IP address (167.254.25.254 in the example
above) changes periodically, so our shortcuts on the remote box to files on
the host stop working until we change them to reflect the host's new private
IP address.
Is there a way to either:
1. Stop the host's private IP address from changing; or,
2. Allow hostname resolution without using the host's gateway on the remote machine?
Thanks for any ideas!
host for a single incoming VPN connection from another XP machine.
On the remote box, the "use default gateway on host" isn't checked
(to permit Internet use while the VPN is running.) So the IP address
handed out to the remote box by the VPN server has no gateway specified.
Because of this, we can't access the host by it's name, such as \\HOST.
However, we can access it by using its IP address, such as \\167.254.25.254.
The trouble is that the host's private IP address (167.254.25.254 in the example
above) changes periodically, so our shortcuts on the remote box to files on
the host stop working until we change them to reflect the host's new private
IP address.
Is there a way to either:
1. Stop the host's private IP address from changing; or,
2. Allow hostname resolution without using the host's gateway on the remote machine?
Thanks for any ideas!