Problem with Demand Dialing
Problem with Demand Dialing
(OP)
Hi,
We have a remote site to which we need to create a "as needed" connection. We have attempted to use a vpn connection through our respective firewalls, but the remote end could not handle it (old software that wont be replaced). I remembered reading about a feature of RRAS in Win2K server that handles demand dialing really well.
So anyway, I set it up and am now having the following problem. When a machine on the lan attempts to ping a remote machine (at the other end of the remote dial) it times out (ping **** /t) . The link is initiated on the RRAS server, and the rras box CAN ping around the remote network. Machines on my lan cant ping the remote end.
I realise that its bound to be something really silly, but I cant spot it at all. Can anyone help?
Thanks
Steve
We have a remote site to which we need to create a "as needed" connection. We have attempted to use a vpn connection through our respective firewalls, but the remote end could not handle it (old software that wont be replaced). I remembered reading about a feature of RRAS in Win2K server that handles demand dialing really well.
So anyway, I set it up and am now having the following problem. When a machine on the lan attempts to ping a remote machine (at the other end of the remote dial) it times out (ping **** /t) . The link is initiated on the RRAS server, and the rras box CAN ping around the remote network. Machines on my lan cant ping the remote end.
I realise that its bound to be something really silly, but I cant spot it at all. Can anyone help?
Thanks
Steve
Talk To Other Members
RE: Problem with Demand Dialing
This will always happen on the first ping to the outside world as Ping will not wait for the connection to be established. If you wait about 30 secs for the dial up to get sorted, a second ping should then work. You will see this if you are using Dial On Demand for a shared internet connection as well - Explorer (or whatever) will always return page not found as it can't be bothered waiting, the second fetch should work OK. This is a known limitation of DOD - see Microsoft knowledge base for more info - search for ICS.