Hey Tom, Take a look on the following e-mail Jim sent us yestarday... "http://www.ISAserver.org This is the dreaded (TS-coined) 14120 error. Internal clients trying to access a published server via external IP's cause this. There have been many suggestions on how to fix this, but the most reliable is to follow the directions in these KBs: http://support.microsoft.com/support/kb/articles/Q288/3/96.ASP http://support.microsoft.com/support/kb/articles/Q288/2/36.ASP Jim Harrison MCP(2K), A+, Network+, PCG" I'm sure this will HELP.... thanks again to JIM HARRISON!!! Aleks -----Original Message----- From: Tom Briody [mailto:tombr@xxxxxxxxxxx] Sent: quarta-feira, 25 de julho de 2001 20:16 To: [ISAserver.org Discussion List] Subject: [isalist] Event ID 14120 http://www.ISAserver.org Anyone know what this is all about? Every few days I get an event log entry ID 14120 from "Microsoft Web Proxy". It reads as follows; "The ISA Server services cannot create a packet filter xxx.xxx.xxx.xxx. this event occurs when there is a conflict between the Local Address Table (LAT) configuration and the Windows 2000 routing table. Check the routing table and the LAT to find the source of the conflict." I let ISA construct the LAT and even included the private address ranges and let it load from the internal routing table. We are a small flat IP network with one class C address range. Could an improperly configured packet filter cause this message? There are no symptoms other than the event log messages. Thanks in advance for any ideas. Tom Briody, MCSE Email: tombr@xxxxxxxxxxx <mailto:tombr@xxxxxxxxxxx> ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: Aleks@xxxxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')