0

I have these servers...

Name : DC1
Roles: PDC, File/Print, RD License, SQL 2012

Name : DC2 
Roles: BDC, RD Webaccess

Name : SVRDS1
Roles: RD Broker (primary), RD Host session

Name : SVRDS2
Roles: RD Broker, RD Host session

Name : SVRDS3
Roles: RD Broker, RD Host session, RD Gateway

I've set up a round-robin dns (called rd.mycompany.local) for the SVRDS1, SVRDS2 and SVRDS3.

This round-robin name is set up in broker HA round-robin name.

If I log on externally via webaccess (I see that the round-robin name is used as address), I get an error ... "An authentication error has occurred (Code: 0x607)".

If I change the round-robin name in the broker HA to SVRDS1.mycompany.local, then I log on perfectly fine.

If I change the round-robin name in the broker HA to SVRDS2.mycompany.local or SVRDS3.mycompany.com, then I get the error again ... "An authentication error has occurred (Code: 0x607)".

I'm lost to where to start to look.

Why is it only one of my rd hosts that works with the round-robin dns name?

Why doesn't it work with the round-robin dns name rd.mycompany.com?

Thanks.

14
  • Just to verify then, you do have rd.mycompany.com pointed to all three servers in DNS? Meaning there are three separate entries in DNS with the same name but pointing to the three IPs of the RDSH servers? If not, then that is your first problem. Apr 27, 2014 at 21:46
  • Yes all three RDSH servers IPs use the same dns (rd.mycompany.comn) in DNS.
    – MojoDK
    Apr 28, 2014 at 5:15
  • Forgive these trivial questions I'll be asking you, but I think I know what's going on and I just need to confirm before I direct you on how to proceed. 1) Does using rd.mycompany.local in your Remote Desktop Connection log you on to the farm? If yes, great, if not, then we'll address that. 2) If you're trying to use rd.mycompany.com, do you have a zone for mycompany.com which is different than mycompany.local? If you don't, resolution is your problem and we can address that too. Please let me know the answers to these. I work with RDS all the time so we should be able to fix it. Apr 28, 2014 at 18:05
  • ... And the above two questions are asking from the standpoint of you being inside your network, on the LAN. We'll deal with the WAN/external users after that. Apr 28, 2014 at 18:06
  • Answers to these? Apr 29, 2014 at 13:57

1 Answer 1

0

Problem solved by calling MS.

They changed CAP and RAP to default values and lowered the security on collection to low.

Furthermore I found out it's only possible to use collection by using webaccess. I thought I could use Remote Desktop App and the broker address as "Computer Address", but that's not possible.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .