nlwtech
asked on
Remote Workplace RDP just started failing, Terminal Services Gateway server is temporarily unavailable
This problem just started when attempting to connect to a computer on a SBS 2011 server domain through Remote Desktop Connection from the Remote Web Access Remote Workplace. Note that I can login into the Remote Web Workplace just fine.
The actual error message from the remote computer is:
This computer can't connect to the remote computer because the Terminal Services Gateway server is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance.
On the SBS 2011 server, the only thing I found so far is that the Remote Desktop Gateway server will not start. It fails with the following error message:
Windows could not start the Remote Desktop Gateway service on Local Computer.
Error 1075: The dependency services does not exist or has been marked for deletion.
The dependencies include:
+ Remote Procedure Call (RPC)
-- DCOM Service Process Launcer
--RPC Endpoint Mapper
+ RPC/HTTP Load Balancing Service
-- Remote Procedure Call (RPC)
----DCOM Server Process Launcher
----RPC Endpoint Mapper
+ World Wide Web Publishing Service
-- HTTP
--Windows Process Activation Service
----DCOM Server Process Launcer
----RPC Endpoint Mapper
Thanks!
The actual error message from the remote computer is:
This computer can't connect to the remote computer because the Terminal Services Gateway server is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance.
On the SBS 2011 server, the only thing I found so far is that the Remote Desktop Gateway server will not start. It fails with the following error message:
Windows could not start the Remote Desktop Gateway service on Local Computer.
Error 1075: The dependency services does not exist or has been marked for deletion.
The dependencies include:
+ Remote Procedure Call (RPC)
-- DCOM Service Process Launcer
--RPC Endpoint Mapper
+ RPC/HTTP Load Balancing Service
-- Remote Procedure Call (RPC)
----DCOM Server Process Launcher
----RPC Endpoint Mapper
+ World Wide Web Publishing Service
-- HTTP
--Windows Process Activation Service
----DCOM Server Process Launcer
----RPC Endpoint Mapper
Thanks!
pclinuxguru
Have you tried restarting the machine that has the gateway service installed?
ASKER
Yes, restarted the SBS 2011 server multiple times including after I removed the Windows patches installed over the last week.
Is the rpc service started and if not will it let you start it?
Check for the events on this server.
ASKER
Yes, the RPC service is started.
There aren't any event errors or warnings when I attempt to RDP.
There aren't any event errors or warnings when I attempt to RDP.
There will be some events when you start the failing service.
Out of the services that are listed as dependencies which ones are running, and which ones are not or are missing?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I found this error in the event log when attempting to restart the Remote Desktop Gateway service:
Log Name: System
Source: Service Control Manager
Date: 9/5/2012 7:48:49 AM
Event ID: 7003
The Remote Desktop Gateway service depends the following service: IAS. This service might not be installed.
Log Name: System
Source: Service Control Manager
Date: 9/5/2012 7:48:49 AM
Event ID: 7003
The Remote Desktop Gateway service depends the following service: IAS. This service might not be installed.
Do you have an Internet Authentication Service listed and can you start it?
ASKER
No, it is not listed under services
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I ended up calling Microsoft but it was the Network Policy Service. Here was the resolution:
--Checked services console, RDP gateway was stopped.
--When we try to start RDP gateway it fails due to dependancy error.
--Checked dependences and found that Network Policy Server was not listed there.
--Checked further and found the NPS was not there in the Services console and neither was the IAS key present in registry under services.
--Uninstalled Network Policy and Access Services role from server manager.
--Rebooted the server and re-installed Network Policy and Access Services role by choosing NPS and RRAS.
--Successfully installed role, after which also re-installed Remote Desktop Services from Server Manager successfully.
--Ran the following command to enable RDP gateway manager gui:
dism /online /Enable-Feature:Gateway-UI
--Created the default RAP and CAP policies for RD gateway manager.
--Now able to RDP successfully using RWA.
--Ensured that RDP gateway service and RDP service both were started in services console. I was hoping to get by without a server restart but it was required. Not sure why the Network Policy Service disappeared in the first place
--Checked services console, RDP gateway was stopped.
--When we try to start RDP gateway it fails due to dependancy error.
--Checked dependences and found that Network Policy Server was not listed there.
--Checked further and found the NPS was not there in the Services console and neither was the IAS key present in registry under services.
--Uninstalled Network Policy and Access Services role from server manager.
--Rebooted the server and re-installed Network Policy and Access Services role by choosing NPS and RRAS.
--Successfully installed role, after which also re-installed Remote Desktop Services from Server Manager successfully.
--Ran the following command to enable RDP gateway manager gui:
dism /online /Enable-Feature:Gateway-UI
--Created the default RAP and CAP policies for RD gateway manager.
--Now able to RDP successfully using RWA.
--Ensured that RDP gateway service and RDP service both were started in services console. I was hoping to get by without a server restart but it was required. Not sure why the Network Policy Service disappeared in the first place