That's a name resolution issue. What is the domain suffix for each remote site? -----Original Message----- From: Ted D [mailto:tdoholis@xxxxxxxxxxxxx] Sent: Wednesday, February 02, 2005 6:51 AM To: [ISAserver.org Discussion List] Subject: [isalist] strange differences between networks...... http://www.ISAserver.org I have ISA 2004 with many networks behind it. Everything seems to be set up correctly as web proxy clients all work correctly however there seem to be 2 confusing items left: 1. remote secure nat clients do not work. The routing layout works as remote clients below: remote site GW - 10.20.3.9 | remote router (10.20.3.9)(10.20.7.2) | Local router (10.20.7.3)(10.20.1.9) |default route to ISA | ISA (10.20.1.41 inside)(no gw) Windows route to 10.20.3.x via 10.20.1.9 2. clients from 1 remote site can access an internal webserver via a dotless name but clients from another remote site must use a FQDN? any ideas? ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 Exchange Server Resource Site: http://www.msexchange.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: jim@xxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist Report abuse to listadmin@xxxxxxxxxxxxx All mail to and from this domain is GFI-scanned.