Wednesday 28 August 2013

Remote Desktop Gateway 401 rpcping response

Remote Desktop Gateway 401 rpcping response

A vanilla domain-less install of Windows Server 2008R1 and following many
of available guides:
http://technet.microsoft.com/en-us/library/dd983949(v=ws.10).aspx
Full Computer Name set to TSGSERVER.local, Workgroup WORKGROUP.
Add roles for Remote Desktop Services and the Remote Desktop Gateway.
Create self-signed certificate.
Complete install.
Export certificate via MMC from Local Computer/Personal/Certificates.
Import certificate via MMC to Local Computer/Trusted Root Certification
Authorities.
Test with rpcping on command line:
rpcping -v 3
-e 3388
-t ncacn_http
-s localhost
-o RpcProxy=TSGSERVER.local
-P "Administrator,WORKGROUP,Password1"
-H NTLM -u NTLM
-a connect
-F ssl
-B msstd:TSGSERVER.local
-E
-R None
And the RPC fails:
RPCPing v6.0. Copyright (C) Microsoft Corporation, 2002-2006
Since you have specified the RPC/HTTP proxy echo only option (-E), the
endpoint
/interface you have specified will be ignored as no calls will reach the
RPC/HTT
P server
RPCPing set Activity ID: {0c934a78-201c-40a3-82e8-9700bd928be6}
RPCPinging proxy server tsgserver.local with Echo Request Packet
Setting autologon policy to high
Sending ping to server
Response from server received: 401
Use Server Preffered Auth Scheme: 2
Setting autologon policy to high
Sending ping to server
Response from server received: 401
Client is not authorized to ping RPC proxy
Ping failed
With the IIS log files being similarly informative:
#Software: Microsoft Internet Information Services 7.5
#Version: 1.0
#Date: 2013-08-28 18:01:02
#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port
cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status
time-taken
2013-08-28 18:01:02 192.168.1.1 RPC_IN_DATA /Rpc/rpcproxy.dll - 443 -
192.168.1.1 MSRPC 401 2 5 514
2013-08-28 18:01:02 192.168.1.1 RPC_IN_DATA /Rpc/rpcproxy.dll - 443 -
192.168.1.1 MSRPC 401 2 5 0
What steps am I missing?

No comments:

Post a Comment