Score:1

How to setup Windows Remote Desktop Connection Broker HA with SQL Server Express?

cn flag

I am preparing an environment in which Remote Desktop Connection Broker for which HA is to be based on SQL server (windows server standard 2022)

In my case, the SQL server is MS SQL Server Express 2022 - I have properly prepared DNS, group in AD, permissions granted for this group, firewalls turned off, appropriate ODBC connector.

But every time I get a connection error - the database is created from SSMS (empty).

error connectionstring

Driver={ODBC Driver 18 for SQL Server};Server=tcp:SERVERNAME\NAMEDINSTANCE,1433;Trusted_Connection=Yes;APP=Remote Desktop Services Connection Broker;Database=rds_db

I used these two paths in the configuration: https://rdr-it.com/en/rds-farm-high-availability-service-broker-configuration/ https://woshub.com/configure-rds-connection-broker-high-availability-windows-server/

Isn't SQL Express sometimes the problem? I have port 1433 and the wizard clearly says port 1434

What else can I pay attention to?

How to resolve this problem?


error

PLS help, Imm trying same thing in lab - but same error.

lab

quick summary:

sql.lab.net - sql server express with new empty db: rds_db

rds1.lab.net - first rds host with broker role

rds2.lab.net - second rds host

in active directory im have secuirty group with this two hosts

ad_group

in sql im have login maped to this security group (dbowner, dbcreator, public, sysadmin)

sql_login

all firewalls are down - check telnet from rds1.lab.net to sql.lab.net port 1433 is open

on rds1.lab.net and rds2.lab.net in local group: RDS Managment Server i'm add hosts rds1,rds2 and network service

local group

in DNS im have two records A in revers lab.net zone with name rds.lab.net (ip of rds1) and rds.lab.net (ip of rds2) - round robin

dns

cn flag
If you haven't confirmed what port your database/server is listening on, do it using netstat. Typically default instances are on 1433, and named instances on another high port. 1434 is typically for the SQL Browser, which you don't need if you know the port that you have configured for your rds_db database
Score:0
us flag

Here are some things you need to check:

Make sure your Instance is really listening on TCP 1433, if you want to connect this way. Open Sql Server Configuration Manager. Expand on SQL Server Network Configuration and select Protocols for YOURINSTANCE. Right klick on TCP/IP and change to IP Addresses. Either your IPv4 Address or IPALL needs to have the TCP Port set to 1433. Verify this by looking for the sqlserver process in Resource Monitor in the Network Tab at Listening Ports. Also maybe try to connect from another host with SSMS.

Is that ODBC Driver you want to use installed? Check in the ODBC Data Source Administator in the Drivers tab. Is it even supported by the application you want to configure? For testing purpose try using the Native Client.

Maybe check this Documentation too: Add the RD Connection Broker server to the deployment and configure high availability

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.