TS Gateway - Certificate warning

-

hi,

 

just installed beta 3, , i'm running following problem:

 

- installed server rather cryptic netbios name.

- installed friendly named certificate on machine (eg tsgateway.tamtam.nl), signed internal ca

- installed ts gateway (and ts web) , configured both use friendly named certificate (tsgateway.tamtam.nl)

- published ts gateway on isa server 2004 ee, using wildcard certificate on listener (*.tamtam.nl). isa server bridging ssl, terminates , re-establishes tunnel ts gateway. clients use 'tsgateway.tamtam.nl' connect server. external dns setup point tsgateway.tamtam.nl correct listener.

 

using vista's built-in mstsc.exe, configure use tsgateway. connecting internal server, i first asked enter login credentials target server (as normal), , presented login box provide gateway server credentials. after successful login, receive following message:

 

"this computer can't connect remote computer because terminal services gateway server address requested , teh certificate subject name not match. contact network administrator assistance."

 

i'm guessing because hostname not match wildcard certificate. there issue vista ts client , wildcard certificates? possible install update client, ones provided xp , windows server 2003 - or still unresolved issue?

 

-m

hi martin, thank question.  problem addressed in lh beta-3 build.  using mstsc client , tsg server beta-3 build?  both needs beta-3 version scenario work.  elango


Windows Server  >  Remote Desktop Services (Terminal Services)



Comments

Post a Comment

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

-
looking options resolve error , prevent in future. thanks help. hardware: 2 node dell hv cluster running2012r2 dc 8 nic/ea in multiplex mode 4x hyper-v 4x hosts storage: 2x synology nas, accessed through iscsi hosts , cluster relevant logs: log name:      microsoft-windows-failoverclustering/diagnostic source:        microsoft-windows-failoverclustering date:          event id:      2050 task category: none level:         warning keywords:       user:          system computer:      l description: [dcm] filter wimmount found @ unsafe altitude 180700 log name:      system source:        microsoft-windows-failoverclustering date:         event id:      5125 task category: cluster shared volume level:         warning keywords:       user:          system computer: description: cluster shared volume 'volume1' ('cluster disk 1') has identified 1 or more active filter drivers on device stack interfere csv operatio
Read more

Failed to delete the test record dcdiag-test-record in zone test.com

-
ps c:\users\administrator.test> dcdiag /test:dns directory server diagnosis performing initial setup:    trying find home server...    home server = dc02    * identified ad forest.    done gathering initial info. doing initial required tests    testing server: default-first-site-name\dc02       starting test: connectivity          ......................... dc02 passed test connectivity doing primary tests    testing server: default-first-site-name\dc02       starting test: dns          dns tests running , not hung. please wait few minutes...          ......................... dc02 passed test dns    running partition tests on : forestdnszones    running partition tests on : domaindnszones    running partition tests on : schema    running partition tests on : configuration    running partition tests on : test    running enterprise tests on : test.com       starting test: dns          test results domain
Read more

Azure MFA with Azure AD and RDS

-
i have setup following lab in azure , need help. a server (domain controller) , remote desktop services. and server multi factor authentication server. i have setup following one http://www.rdsgurus.com/uncategorized/step-by-step-using-windows-server-2012-r2-rd-gateway-with-azure-multifactor-authentication/ and when im connecting got following error. the user "domain\username", on client computer "xxx.xxx.xxx.xxx", did not meet connection authorization policy requirements , therefore not authorized access rd gateway server. authentication method used was: "ntlm" , connection protocol used: "rpc-http". following error occurred: "23003". also on security log i've got following authentication details: connection request policy name: ts gateway authorization policy network policy name: - authentication provider: radius proxy authentication server: test.test.local authentication type: - eap t
Read more