asked on

very strange exchange behavior ...

exchange is installed on the sbs server, prem edition.
all clients connect fine on their client pc's.
there is a win 2003 R2 server which acts as a TS server.
I installed outlook on that server for the users. (latest updates, SP's)

When I open outlook (cached mode), it always sys that the connection has been restored.
When I DONT use cashed mode (which i prefer) I CANT open outlook, it says the exchange server is unavailable .... .
I can ping, telnet to the exchange server. It's in the same domain etc etc.

Sometimes the outlook works in a TS session, ofter I click send/receive twice !?!
first time pressing s/r it says: exchange server unavailable ...

Can somebody please help me with this very strange behavior...

Jeffrey Kane - TechSoEasy

Well Cached Mode cannot be used on a Terminal Server, so your preference is a wise one. However, since it was most likely enabled and then disabled you have probably corrupted the user profile. Please make sure that you have installed Outlook according to this KB: http://support.microsoft.com/kb/828955 and then you will need to recreate the user profiles by removing any profiles that are currently on the server.

Jeff
TechSoEasy

suppsaws

ASKER

Jeff,

I reinstalled outlook, and deleted the profile.
I started outlook, without cached mode, typed in the servername and the username (administrator in this case), I pressed 'check name' and it finds the exchange server + username.
Then I press ok, and still get that same error:

"cannot start microsoft office outlook. unable to open the outlook window. the set of folders could not be opened. the connection to the MS exchange server is unavailable. outlook must be online or connected to complete this action".

The only other thing I can think of is ISA. isa client is installed on the server ... .
Problem is that this is one of my first ISA installation, so maybe that could be the problem?
Although I don't think isa is blocking smth locally to the exchange server??

suppsaws

ASKER

it looks like there are some more people with the exact same problem, but without a solution:
http://groups.google.be/group/microsoft.public.windows.terminal_services/browse_thread/thread/c55075abf3580fc5/8be58d742ad6c56e?lnk=st&q=outlook+terminal+server+the+connection+to+the+microsoft+exchange+server+is+unavailable&rnum=2&hl=nl#8be58d742ad6c56e

I can ping the server, IO can telnet to port 25
the ping replies with the FQDN etc etc ....
Any idea's?

ASKER CERTIFIED SOLUTION

Jeffrey Kane - TechSoEasy

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

suppsaws

ASKER

Hello Jeff,

I found the answer in the google groups:

"It might be worth trying this, it worked for me.
Outlook configuration - more settings - security tab - tick encrypt data etc."

I'me glad I found the solutuion, but I really would like to know WHY I have to tick the 'encrypt data' tab .....

(checking your solution meanwhile)

suppsaws

ASKER

I don't think it's the RPC thing, because it's just an internal connection to the exchange server, that doesn't work over RPC, does it?

Jeffrey Kane - TechSoEasy

Did you do that and did it solve the problem???

Jeff
TechSoEasy

Jeffrey Kane - TechSoEasy

RPC is used for internal communication between servers. Please see this line in the download details:

"In Small Business Server (SBS) scenarios, this may commonly occur when Outlook is installed on a server running Terminal Services in application sharing mode."

Jeff
TechSoEasy

suppsaws

ASKER

Jeff,

It looks like both solutions work!
I installed the patch, everything works fine.
It looks like if I chose 'encrypt data' it doesn't go via rcp anymore ...