VPN Route forcibly enabled?

[wmason]

On the VPN host, I'm getting the message "Forcibly enabled" when I expand the routes. Users can connect, but the host shows as "inaccessible".

Expanding Published Routes:
NAT/Translated
192.168.1.0/255.255.25.0 (Forcibly enabled)
192.168.1.100/255.255.255.255

Users are accessing host via DSL routers. User local subnets are 192.168.y.x (where y is >1 and unique).

Version is 1.0.10 running on WinXP (SP1).

[dparry]

I believe that the route 192.168.1.0/255.255.255.0 is forcbly enabled because in your VPN configuration you have selected "Local Network Access" or some similar option.

Regards,

David Parry

[ipweb]

On the VPN host, I'm getting the message "Forcibly enabled" when I expand the routes. Users can connect, but the host shows as "inaccessible".

Expanding Published Routes:
NAT/Translated
192.168.1.0/255.255.25.0 (Forcibly enabled)
192.168.1.100/255.255.255.255

Users are accessing host via DSL routers. User local subnets are 192.168.y.x (where y is >1 and unique).

Version is 1.0.10 running on WinXP (SP1).

Did you ever figure out this problem? I have the same problem and can't use the VPN.

[Pascal]

Did you ever figure out this problem? I have the same problem and can't use the VPN.

If you are running an upgraded VPN version (Anything prior to 1.0.10 upgraded) you might have older versions of the routing overrides saved in your registry. Previous versions saved all the routing information so they could refer back to it, the newer versions only save the changed (Forcibly enabled / disabled) routes.

It might be necessary to clear that, if you did run an upgrade. (If so, post back and I'll send you instructions for that)

However, there could be several reasons for them not talking happily to one-another and most of them are routing related. Are both ends of your VPN setup on different subnets ? Can you ping either end of the VPN when it is connected ?