Yes.. I have an idea. or rather a guess... I think that your NETLOGON service on your ISA server must already be listening on port 445 on all IP's for its self (try a NETSTAT -na and look for something that says 0.0.0.0:445 LISTENING) You prolly need to set that service to either not listen at all, or listen on an alternate port, and then the publising rule will be able to pick up that port and do what you want with it. -Jay Mobley -----Original Message----- From: Michael Lippman [mailto:Michael.Lippman@xxxxxxxxxxxxxxxx] Sent: Tuesday, February 12, 2002 10:08 AM To: [ISAserver.org Discussion List] Subject: [isalist] Netlogon Port 445 http://www.ISAserver.org I am trying to setup a front end exchange server. I have all the custom definitions completed except for Netlogon(TCP/445) Whenever I enable it I get a warning in the event log (14163) that the map failed because the port on the external interface is being used by another application. The firewall service failed to bind etc. . . . . Anyone have any ideas I would appreciate it. Thanks, MRL ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: jmobley@xxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')