Antispoofing deals with receiving a packet with a source IP that doesn't belong in that network. Trust me; you want to know when that occurs. If you're routing internal traffic around ISA to the external interface, then ISA will balk at that traffic (as it should). You want the clients so use ISA to route their web traffic, but you don't want to configure them to talk to it? Jim Harrison MCP(NT4, W2K), A+, Network+, PCG http://isaserver.org/authors/harrison/ ----- Original Message ----- From: "William Holmes" <wtholmes@xxxxxxxxxxxxxx> To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> Sent: Monday, December 03, 2001 11:22 Subject: [isalist] Antispoofing http://www.ISAserver.org Hello, Is it possible to configure Antispoofing ? I would like to disable Antispoofing. I essentially want my ISA server to act as though its my Web server. I have published the "Real" web server with the ISA server and that works fine. The only problem is that users on the inside network are unable to connect to the ISA servers external network due to the Antispoofing rule. I have the ISA servers external network in a DMZ network and do expect traffic from my internal nets. Notes: I can connect successfully to the Internal Interface and see my published web servers. I would like to enable this capability for my internal users without having to configure proxies or having them point to the internal address of the ISA server. Thanks Bill ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: jim@xxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')