This is such a standard setup for RRAS (on ISA), I can't believe we're having this much trouble. Anyone have an idea?
The client dials-up an ISP, then does the VPN. Occasionally they can ping the internal hosts, usually not. I tried using a different ISP, same problem. When I connect the client to the ISA's external interface and do a LAN VPN it pings everytime. I then hung a modem on the ISA to test a straight RAS dialin and that works every time too. A reboot of the client allows it to ping again, but subsequent reconnects eventually fail.
The internal network is numbered 10.60.0.1 - 10.60.7.254 The RRAS is handing out addresses from a static pool of 10.60.7.1 - 10.60.7.254, it takes the first IP (10.60.7.1) for its internal interface. The client gets 10.60.7.2, which becomes its default gateway. The times when pinging fails, the client cannot even ping the ISA's virtual interface (10.60.7.2) but interestingly it still resolves DNS. I'm stumped. Any help is much appreciated.
The client dials-up an ISP, then does the VPN. Occasionally they can ping the internal hosts, usually not. I tried using a different ISP, same problem. When I connect the client to the ISA's external interface and do a LAN VPN it pings everytime. I then hung a modem on the ISA to test a straight RAS dialin and that works every time too. A reboot of the client allows it to ping again, but subsequent reconnects eventually fail.
The internal network is numbered 10.60.0.1 - 10.60.7.254 The RRAS is handing out addresses from a static pool of 10.60.7.1 - 10.60.7.254, it takes the first IP (10.60.7.1) for its internal interface. The client gets 10.60.7.2, which becomes its default gateway. The times when pinging fails, the client cannot even ping the ISA's virtual interface (10.60.7.2) but interestingly it still resolves DNS. I'm stumped. Any help is much appreciated.