This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SSL Remote access - Is a masq rule needed for remote to internal?

Setup a 7.505 box for a potential customer....

For SSL remote connection, had to add a Masq rule from VPN pool to Internal before the remote client could connect to internal machines.

(Internal is in Local Network list and Automatic Packet Filter Rules is selected)

Adding a Masq rule for this is not specified and I have several other boxes that work without this extra step.

Why?

Tom

This thread was automatically locked due to age.

Parents

0 BAlfson over 15 years ago

This also can occur if you assign VPN IPs in the range of "Internal (Network)."

Cheers - Bob
Cancel
Vote Up 0 Vote Down

Cancel
0 Ed.Kok over 15 years ago in reply to BAlfson

This also can occur if you assign VPN IPs in the range of "Internal (Network)."

Cheers - Bob

That is what I did at first because I thought that otherwise I had to create new routing-rules. It didn't work and it does work with the default pool for Cisco-clients without creating any routing-rules.

So thats nice, but a connected client doesn't have DNS-settings for LAN-usage. So I can ping hosts on the LAN by IP-address but I cannot resolve anything.
Is it possible to configure this?

Ed
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Ed.Kok over 15 years ago in reply to BAlfson

This also can occur if you assign VPN IPs in the range of "Internal (Network)."

Cheers - Bob

That is what I did at first because I thought that otherwise I had to create new routing-rules. It didn't work and it does work with the default pool for Cisco-clients without creating any routing-rules.

So thats nice, but a connected client doesn't have DNS-settings for LAN-usage. So I can ping hosts on the LAN by IP-address but I cannot resolve anything.
Is it possible to configure this?

Ed
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data