Re: NAT with IP Filters
- From: "Jerome Baum" <gratemyl@xxxxxxxxx>
- Date: 29 Dec 2006 18:08:41 -0800
Phillip Windell wrote:
"Jerome Baum" <gratemyl@xxxxxxxxx> wrote in message
news:1167410837.115945.186740@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I just noticed that the "NAT Session Mappings" table shows nothing
about the made connections - is it supposed to? (these are outwards
connections which I mean, from a private interface).
I think that is only for inbound connections (Static NAT aka, Reverse NAT).
Nothing
I don't know what to tell you about the RDP. I think without a real
firewall product beng in use it is going to be "all or nothing". I think
your only option is to control *who* can connect based on their user account
and not be concerned with where they came from.
That policy is already in place. My plan is that everybody who is
connected via the VPN (i.e. any of the internal interfaces) can connect
via NAT to the outside world, but the outside world can only access
certain ports on the router. The problem is that I cannot set the
inbound filters to allow only certain ports without blocking the
internal interfaces off for outbound connections.
Thx again
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
The views expressed are my own (as annoying as they are), and not those of
my employer or anyone else associated with me.
-----------------------------------------------------
.
- Follow-Ups:
- Re: NAT with IP Filters
- From: Bill Grant
- Re: NAT with IP Filters
- References:
- NAT with IP Filters
- From: Jerome Baum
- Re: NAT with IP Filters
- From: Jerome Baum
- Re: NAT with IP Filters
- From: Jerome Baum
- NAT with IP Filters
- Prev by Date: Re: DFS replication
- Next by Date: Create user that only has access to VPN?
- Previous by thread: Re: NAT with IP Filters
- Next by thread: Re: NAT with IP Filters
- Index(es):
Relevant Pages
|
