Newly deployed RDS Broker, NlaSvc service timeout, force restart

Question

Hello everyone, we just deployed a new RDS broker running windows server 2022 version 21H2 build 20348.1487, the licensing runs on a separate vm, with two server session hosts. On the first start of its release to user terminals that morning no one could connect and they would get just blue color screens or black, pulseway monitoring would be showing the system online and offline repeatedly. we would shutdown the server, and a few times had to force it. The system would come up, users could connect, and pulseway reported normal below are the errors that would coincide with the event. These errors will not show backup till the above issues show up again and we do the process over gain.

multiple

A timeout (90000 milliseconds) was reached while waiting for a transaction response from the iphlpsvc service.

then this would come up
A timeout (90000 milliseconds) was reached while waiting for a transaction response from the NlaSvc service.

This happens every day since its deployment, and I can not find any rhyme or reason for it, its the only system doing it, it is not the only windows server 2022 standard in operation.

Has anyone come across this issue before? I can't really find anything on this and it is easy to mitigate right now but the force shutdowns are going to take a toll on the vm (and my sanity)

Thank you for any help!

Answer 1

Hi. Thank you for your question and reaching out. I’d be more than happy to help you with your query.

The errors you are encountering suggest that there are issues with the iphlpsvc (IP Helper) and NlaSvc (Network Location Awareness) services on your RDS broker. These services are responsible for various network-related tasks such as DHCP, DNS, and IP address configuration.

The timeout errors indicate that these services are not responding in a timely manner, which is causing the RDS broker to become unresponsive and preventing users from connecting. This could be caused by a number of factors such as network connectivity issues, resource constraints on the RDS broker, or a bug in the Windows Server 2022 version 21H2 build 20348.1487.

To troubleshoot this issue, I would recommend checking the following:

1. Verify that the network connectivity between the RDS broker and the licensing server and the session hosts is stable and that there are no issues with the network infrastructure.
2. Check the resource usage on the RDS broker, including CPU, memory, and disk usage. Make sure that the RDS broker has enough resources to handle the number of connections it is receiving.
3. Check the event logs on the RDS broker and the licensing server for any relevant error messages that might provide more information about the issue.
4. Check if there is any update or hotfix related to the issue on Microsoft support website
5. If the issue persist, consider opening a support ticket with Microsoft to get further assistance on this issue.

It's also worth noting that you recently upgraded to Windows Server 2022 version 21H2 build 20348.1487, it may be that this version has some bugs that are causing the issue.

If the reply was helpful, please don’t forget to upvote or accept as answer, thank you.