Windows XP - Outlook Problem
Problem is with Machines outside the firewall running
Windows XP with Office XP. When they try connecting to our
Exchange Server 5.5, it takes Outlook 2-4 minutes to
open. On Windows 2000/NT machines with Office XP, Outlook
loads up instantly.
Our Exchange Server has the following ports open to
workstations outside the firewall:
5020 (MS Exchange DS Static Port)
5030 (MS Exchange IS Static Port)
Machines outside the Firewall:
Windows XP (SP1) with Outlook 2002 (SP2) - Problem
Windows 2000 (SP1) with Outlook 2002 (SP2) - No
Windows 2000 (SP3) with Outlook 2002 (SP2) - No
Windows NT (SP6a) with Outlook 2002 (SP2) - No
With one of the XP machines, we have also applied all the
latest Post-SP1 patches for Windows XP and all the latest
updates for Office 2002 and Outlook 2002.
When Windows 2000 machines start up Outlook, they connect
to the Exchange Server, using port 135. It then connects
to the DS and IS static ports.
Here's what happens (Every time) when XP machines start up
1) Client Connects to Server on port 135
2) Does nothing for 2 minutes
3) Exactly after 2 minutes the Client pings the
Server and Server Responds back
4) Client immediately tries connecting using ports
139 and 445 simultaneously on Server
5) 3 seconds later it does the same
6) 6 seconds later it does the same
7) 12 seconds later is connects to Server on port 135
8) 10-20 seconds later (varies) connects on port 135
and then DS and IS static ports and Outlook Opens.
When we do open the Firewall to allow ports 139/ 445
through, the Windows XP machines open Outlook straight
Port 139 (NETBIOS over TCP) and port 445 (SMB over TCP)
are for file sharing, I have not read any documentation
for Exchange 5.5 to have these ports open. These ports are
only open to the Domain Controllers for Authentication.
. Why is there 2 minutes of no activity when XP
. Why then does it try using ports 139/445.
. Instead of doing Steps 1-6 in which it does
nothing, why doesn't it immediately go to steps 7+8 which
Opens Outlook immediately.
. Why if ports 139/445 are open, it opens straight
away because it does not use these ports during the 2
minutes of no activity.
. I have not seen any, but is there any
documentation for Exchange 5.5 to have ports 139 and 445
open? This to me is a security issue.
Exchange XP Client Opens Up Outlook:
12:00:32 Client  Server rcp
12:02:32 Client  Server ICMP
12:02:32 Client  Server ICMP
ECHO Reply Accept
12:02:32 Client  Server Netbios IP
12:02:32 Client  Server 445
12:02:35 Client  Server Netbios IP
12:02:35 Client  Server 445
12:02:41 Client  Server 445
12:02:41 Client  Server Netbios IP
12:02:53 Client  Server rcp
12:03:02 Client  Server rcp
12:03:02 Client  Server Static DS
12:03:02 Client  Server Static IS
Microsoft Knowledge Base Articles
148732 Have tried using Static Ports
163576 Have tried changing the RPC Binding Order
325930 Have tried removing all RPC Client Protocol
Registry Entries except for ncacn_ip_tcp.
Differences in Registry Settings for a 2000 machine (no
delay) and an XP machine
The 2000 machine has the following registry values which
XP does not have: