In my experience, nearly all "delayed connection" problems surrounding ISA are related to DNS. It is not latency, it is a name resolving issue. We learned the hard way migrating from a classic NT 4.0 WINS based domain where everything was based on netbios names and netbeui broadcasts. When we installed ISA, suddenly Telnet sessions where taking up to 2 minutes to connect. Implementing a new DNS server with properly setup forward and reverse lookup zones fixed everything. ----- Original Message ----- From: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> Sent: Tuesday, September 17, 2002 6:00 AM Subject: [isalist] Latency http://www.ISAserver.org I recently installed ISA between my router and office network. I have most everything working as I need it thanks to this helpful site. I know hav a latency problem when I access my router or DMZ. For example, when I telnet from my workstation through ISA to the router it takes 25 seconds to get a login prompt. I have similar problem when I access computers on my DMZ with PCAnywhere, or public FTP sites. When I access a public website like this one there is no noticeable delay. IMAP, POP3, SMTP all work fine too. Any tips? office network -- ISA server -- switch -- router --- Internet | | other computers ------------------------------------------------------ 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 ------------------------------------------------------ Exchange Server Resource Site: http://www.msexchange.org/ Windows Security Resource Site: http://www.windowsecurity.com/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: rdzek@xxxxxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')