Unable To Connect To Terminal Server Farm Externally With TSBroker Enabled

-

remote clients not able connect our farm externally when have tsbroker service enabled. internal connectivity not issue.
we have external ip address being natted ip of broker service server. able connect think due fact broker service server has directed connection instead of 1 of other servers in our farm. when disable broker service, able connect without issues. happens when attempt connect receive initial login screen ( broker server think ) , login screen ( server directing client use) , @ point errors out , states client unable connect remote computer.

remote users able connect if establish prior vpn connection. there better method accomplish we're trying here enable have ability connect remotely tsbroker service features without needing have active vpn connection?

thanks,
markpl

have considered using rdweb , rdgateway r2 out?  rdgateway th service looking believe.  pipe connections through single ip address on ssl.  session broker not functionality.



Windows Server  >  Remote Desktop Services (Terminal Services)



Comments

Post a Comment

Popular posts from this blog

server manager error: ADAM.events.xml could not be enumerated.

-
firewall off isnt it. rerun ldap wizard:?  why?  will screw exchange server running on machine?  ldap wizard asks questions don't understand. please dont send generic links to: http://social.technet.microsoft.com/wiki/contents/articles/13444.windows-server-2012-server-manager-troubleshooting-guide-part-ii-troubleshoot-manageability-status-errors-in-server-manager.aspx thanks, john hi john, >> ok. server manager app. these questions refer this. nothing else 2.  do need create app dir or not?  this server manager, shouldnt done? (why did break in first place?) how check if app dir exists server manager or not. 3.  if "lightweight" implementation of anything, sure hate see "heavyweight" version. the waring events can't enumerated. , cause not completing configuration of ad lds. ad lds not related server manager. used provide flexible support directory-enabled applications. if not implementing such applications, remove role. her
Read more

Cannot access Anywhere Access using domain name?

-
after installing anywhere access in windows server 2012 essentials r2, cannot use anywhere access using setup domain name in wizard such remote.mydomain.com? if enter public ip address, example, 72.2.34.5 works. before set anywhere access, created a record pointing public address...pinged , worked...so not sure doing wrong?  is wizard supposed create record etc , make remote.mydomain.com work? if enter public ip address while on lan, takes me router webpage.  shouldn't work on lan if accessed via public ip? thank you, tim. the wizard can configure remote.microsoft_names.com  remote.remotewebaccess.com but cannot configure domains purchased outside wizard.  depends on how domain configured if wildcard.yourdomain.com should work  if try ping remote.your_domain.com afar , not give proper  public ip, need add record mariette said. much have record domain.com www.domain.com , if have website somewhere else www.domain.com , need remote.domain.com go box gr
Read more

WMI Failure: Unable to update Local Resource Group

-
Image
hi i have windows server 2008 r2 enterprise terminal services installed. this has been working fine, unable add new computers local computer groups policy on rd gateway manager i following error wmi failure: unable update local resource group  just confirm on , resource authorization policies then manage local computer groups hi hussain, posting in windows server forum. firstly please let know, did find particular event log issue? please ensure have configured rap settings correctly , set correct value , permissions rap.xml file , rapstore registry key. please check below thread more details. 1. wmi failure- unable create resource access policy (answered clarence) 2. event id 543 — rd gateway server configuration 3. event id 642 — rd gateway server availability hope helps! thanks, dharmesh Windows Server
Read more