Solved

Remote Web Workspace & OWA - Windows SBS 2008

Posted on 2010-09-06
3
501 Views
Last Modified: 2012-05-10
Whenever I reboot the Windows SBS 2008, remote users are unable to use the Remote  Web Workspace and receive. Users are able to input their user name & password and then receive the message below:
"The Terminal Services Gateway Service service is not running. Contact your network administrator to resolve this issue"

To fix the problem I have to:

1) Open IIS 7
2) Select Sites - SBS Web Applications
3) Select RPC
4) Double click on "SSL Settings" from the right pane
5) I then un-select Require SSL and select "Ignore for Client Certificate
6) Then stop & restart SBS Web Applications.

The above then allows Renote Web workspacve to work.
However if the Windows SBS Server is rebooted the following error appears when trying to use Remote Web Workspace:

"The Terminal Services Gateway Service service is not running. Contact your network administrator to resolve this issue"

I then check the SSL setting for RPC  and it has changed to  "Accept for Client Certificate", why does this setting keep changing when the server is reboot ? Why is this affecting Remote web workspace.

How can this problem be fixed ?

Thanks

Daljit
0
Comment
Question by:BhanaD2
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 15

Expert Comment

by:Dave_AND
ID: 33610472
0
 
LVL 2

Expert Comment

by:SiborgRaider
ID: 33610492
I had the same issue and following this article.
http://support.microsoft.com/kb/969743
0
 

Accepted Solution

by:
BhanaD2 earned 0 total points
ID: 33660882
Guys
I managed to fix the problem:

The solution was as follows:

1)      In the SBS Web Application folder in IIS the SSL Cert was set to require for the entire site directory.  Hence this was propogating down to the RPC Directory!
2)       As soon as I changed the setting to ignore on the site root it would stay on the RPC.  Since the security settings were already higher (128 bit & Require) on the RPCwithCert this was allowed and worked properly.
0

Featured Post

Forrester Webinar: xMatters Delivers 261% ROI

Guest speaker Dean Davison, Forrester Principal Consultant, explains how a Fortune 500 communication company using xMatters found these results: Achieved a 261% ROI, Experienced $753,280 in net present value benefits over 3 years and Reduced MTTR by 91% for tier 1 incidents.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I work for a company that primarily works with small businesses as their outsourced IT vendor. As such the majority of these customers utilize some version of Small Business Server. Due to the economics of running a small business, many of these cus…
You may have discovered the 'Compatibility View Settings' workaround for making your SBS 2008 Remote Web Workplace 'connect to a computer' section stops 'working around' after a Windows 10 client upgrade.  That can be fixed so it 'works around' agai…
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question