The last time I had this issue, I was using Outlook2007. Now I've just 'inherited' the problem again after many months of successful operation with Outlook2010. Outlook uses some sort of fuzzy logic to determine what a 'fast' and 'slow' network is. There are two ways that Outlook can connect:
TCP port 135 (To an AD server, or the exchng srvr itself)?
HTTPS to the proxy specified.
I used my win7 laptop connected to a docking station, and a LAN connection attached to it. --This works like the wind.... no prob for many months. This morning, I attached to a different wireless network at work (still un-fettered access to all campus resources). This is the only thing that changed. NOW.. when i connect to the Exchng srvr, I noticed that "netstat -an" tells me that I'm using TCP/135 to connect to the server, and not HTTPS. NOTE: TCP/135 is not open, not even internally; only HTTPS can be used. Use of 135 will guarantee a failure.
Question: (I'm OK with doing this in the registry, if Outlook is going to be an a$$ about this...) how do I convince Outlook2010 ONLY ever connect using HTTPS via proxy, and never [what it calls] "TCP/IP" (TCP/135)? I've looked on the Internet, and 6 out of 10 complaints end in, "yea, I have that problem too", then there's no resolution provided. Its not good when the "IT Guy can't get his email working..."
↧