No connectivity to published services while on VPN

In article , Erwin Drager wrote: :On the Cisco 831 I use, I have made port forwardings for a number of :services, among which are port 80, 443 (webmail), 25 (smtp) etc. All :this works fine.

:However, when you connect to the 831 using VPN, its not possible to :get to the server I use for webmail/smtp etc because apparently the :port forwarding rule somehow blocks this?

:Is there any way to have the port forwarding, but also have the same :servers reachable under the same port number while on the VPN?

I haven't worked with VPNs on IOS much at all, but this might perhaps provide a lead: On the PIX the way you would do this would be to add an 'nat exemption' access list that matched the VPN traffic:

access-list nonat permit ip SOURCENET SOURCEMASK DESTNET DESTMASK nat (inside) 0 access-list nonat

nat 0 access-list is, on the PIX, always processed before any other kind of nat or static. The result is that "raw" IPs and ports are used for the VPN, but not for anything that does not match the ACL.

Hmm, thats sounds like what I want, only not sure I can do that on the

Thanks!

Erwin