Why are you so sure it's not a DNS issue? Have you tried sniffing the wire during the setup to see what's going on? What about the IIS logs? Anything there? How are you taking the ISP out of the picture and testing? Al -----Original Message----- From: Tony Anderson [mailto:tandersn@xxxxxxxxxxxxxxxxx] Sent: Monday, October 20, 2003 2:22 PM To: [ExchangeList] Subject: [exchangelist] SSL & win2k3 & E2k3 & comcast http://www.MSExchange.org/ Hello all, I am having a problem with the configuration listed in the subject line. In those circumstances, there are 2 delays connecting to OWA, each 20-40 seconds. if you take away any one thing, then it works fine. Anyone else experience this? Have a solution? (NOTE: COMCAST= previously @home cable modem) For example: NON-SSL http + win2k3 + exch2k3 + comcast = INSTANT CONNECT SSL + win2k + exch2k + comcast =INSTANT CONNECT SSL + win2k3 + exch2k3 + DSL/local network = INSTANT CONNECT SSL + Win2k3 + exch2k3 + comcast = BIG DELAY obviously the 2 most suspect items are COMCAST & the win2k3 implementation of SSL. THIS IS NOT A DNS ISSUE Thanks! Tony ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: Leading Network Software Directory: http://www.serverfiles.com No.1 ISA Server Resource Site: http://www.isaserver.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 ------------------------------------------------------