Remote Web Workplace client computer connections suddenly stop working

I have a client that has been using SBS RWW for years to connect to their desktops at work.  They contacted me today because they can't connect suddenly.  Something has to have changed but I can't find it.  Here is what I do know.  Any suggestions are greatly appreciated.

Can reach RWW both locally and externally.  Can request any computer to connect to both externally and locally.  Get the same error either way:  Connectivity to the remote computer could not be established.  Ensure that the remote comuter is on and connected.....

BUT, if I use Server Management directly on the server, select the same client computer and select Connect to Computer via Terminal Services the logon screen pops right up.  No problems.

I can't find any errors logged anywhere.  The server was just rebooted 12 days ago or I would assume it was due for a reboot.  I don't want to just start and stop things willy nilly without some idea what is going on.  I assume something has changed or stopped that should be started but I can't find anything strange in my normal checklist.
LVL 2
dcgrindleAsked:
Who is Participating?
 
dcgrindleAuthor Commented:
A reboot did correct the problem, temporarily, but then it started to happened again.  

Turned out to be a memory management issue in Exchange.  They recently upgraded the memory on the box.  I found the following link discussing the memory management on exchange 2003: http://support.microsoft.com/kb/815372

I followed the recommended settings for msExchESEParamCacheSizeMax and HeapDeCommitFreeBlockThreshold registry entries.  I also used this site as a reference on those setting http://technet.microsoft.com/en-us/library/aa998384(EXCHG.65).aspx

After those changes, I restarted Exchange and it has been fine since.  It has also been a bit faster, according to the users.
0
 
Shreedhar EtteCommented:
- Reboot the server once and see.
0
 
Shreedhar EtteCommented:
0
 
dcgrindleAuthor Commented:
The other suggestions included one option I had already tried before posting plus rebooting the mcahine.  A reboot only cleared the memory problem temporarily - it did not solve it.  The problem started occurring again fairly soon.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.