What you've created is a flat network that just happens to include an ISA server. Packet filtering doesn't work when the internal and external subnets are the same. Jim Harrison MCP(2K), A+, Network+, PCG ----- Original Message ----- From: "Christian Kurmann" <ckurmann@xxxxxxxx> To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> Sent: Thursday, September 06, 2001 3:48 AM Subject: [isalist] ISA with internal Network using Public namespace adresses http://www.ISAserver.org Hi All I would like to create a more secure internal Net with ISA, but not change any of our IPs. (other then the gateway setting). Would the following setup work, or am I complettly overseeing something? (IPs not real) 195.208.154.4/254 255.255.255.0 Internal Net with various servers | | 195.208.154.3 255.255.255.0 ISA Firewall as Gateway | 195.208.154.2 255.255.255.0 External ISA IP | | 194.208.154.1 255.255.255.0 Router to the Internet. Is this possible at all? Can I then simply open up ports to the Server IPs, or do I have to publish the Servers? As far as I know this typ of setup would work with a Hardware Firewall, so I think it schould also go with an ISA or not? Thanks for any reply. Christian Kurmann (PS I know this isn't very secure, but all we want is to see whats going in and out of our site, and be able to block things we decide are not wanted.) ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: jim@xxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')