10,111 questions
Fire up fiddler on the workstation and see what the client is trying to connect to
Outlook takes 40 seconds stuck at "trying to connect"
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 27%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA3%3C/text%3E%3C/svg%3E)
AdamTyler-3751
431
Reputation points
Riddle me this batman. I have an isolated lab environment which doesn't have internet access, but does have Exchange, Domain Controllers, and client machines running Outlook. When opening Outlook in this isolated environment, it takes about 40 seconds for Outlook to find and connect to Exchange. If I jump into the lab firewall and give said client internet access, this problem goes away. Outlook client connects to isolated Exchange server instantly.
Exchange 2016 on-prem and Windows 10. Outlook version 2013.
Regards,
Adam Tyler
Outlook | Windows | Classic Outlook for Windows | For business
Exchange | Exchange Server | Management
7,925 questions
Accepted answer
-
Andy David - MVP 157.8K Reputation points2021-10-22T22:09:19.103+00:00 -
AdamTyler-3751 431 Reputation points
2021-10-22T22:25:05.147+00:00 Thanks for the tip. Here is the output from Fiddler while Outlook is hung "trying to connect".
-
AdamTyler-3751 431 Reputation points
2021-10-22T22:46:04.24+00:00 Sure enough. Once I whitelisted the IP that this resolves to, Outlook fires right up in dev with all other traffic blocked. Unfortunately the list of IPs associated with this FQDN seem to rotate depending on what public DNS server you query. So something you'd have to look every time.
Regards,
Adam Tyler
Sign in to comment -
1 additional answer
Sort by: Most helpful
-
AdamTyler-3751 431 Reputation points
2021-10-22T22:46:18.393+00:00 Sure enough. Once I whitelisted the IP that this resolves to, Outlook fires right up in dev with all other traffic blocked. Unfortunately the list of IPs associated with this FQDN seem to rotate depending on what public DNS server you query. So something you'd have to look every time.
Regards,
Adam Tyler