Outlook 2010 will not connect via TCP/IP but will with HTTP.
So I just built a new terminal server, Windows Server 2008R2sp1. Outlook will resolve my Exchange CAS array within seconds, but won't actually fire up. Says the server is unavailable.
HTTP(Outlook Anywhere) works fine.
All of my other clients seem fine, my other terminal server is fine.
I've re-installed Office multiple times, even rebuilt the server entirely(its a VM), same problem.
I'm obviously missing something here... the question is, what?
HTTP(Outlook Anywhere) works fine.
All of my other clients seem fine, my other terminal server is fine.
I've re-installed Office multiple times, even rebuilt the server entirely(its a VM), same problem.
I'm obviously missing something here... the question is, what?
kinecsys
Do the two terminal servers have the same version of Windows and Outlook (updated to the same level)? and the IP settings are the same (i.e. both getting a reserved IP from the same DHCP server, or at least both with the same exact static settings other than their own ip of course)?
ASKER
Well, the one server is quite a bit older, so updates probably were not installed in the same order, and some of the updates on the new server may have been a part of rollups.
One other thing of note.. The new server uses 32-bit Office, not 64 like the older one. I use 32-bit Office on servers that need to access SharePoint, or else Excel has issues.
I have yet another terminal server that only one department uses which runs 32 bit Office just fine though. Just verified that, actually.
One other thing of note.. The new server uses 32-bit Office, not 64 like the older one. I use 32-bit Office on servers that need to access SharePoint, or else Excel has issues.
I have yet another terminal server that only one department uses which runs 32 bit Office just fine though. Just verified that, actually.
Any firewall in use ?
Have u tried to configure new profile manually
Check that Office 2010 SP1 is installed
http://support.microsoft.com/kb/2460049
There are known issues with TCP and HTTP that were addressed in this SP
http://support.microsoft.com/kb/2460049
There are known issues with TCP and HTTP that were addressed in this SP
have you installed Office on Exchange server ?
ASKER
Firewall is off.
Office sp1 is installed.
No office on Exchange.
Yes, I've tried to create a new profile. Many, many times.
I'm noticing that while this server can ping the CAS array, it can't actually resolve it in Outlook... odd.
Office sp1 is installed.
No office on Exchange.
Yes, I've tried to create a new profile. Many, many times.
I'm noticing that while this server can ping the CAS array, it can't actually resolve it in Outlook... odd.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What is the result of telnet command from client
telnet <servername> 25
&
telnet <servername> 110
telnet <servername> 25
&
telnet <servername> 110
ASKER
I'm not sure why but the virtual NIC must've been having issues.