Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

206498

October 17th, 2013 12:00

Broker cannot connect to RDS

Hi,

i have installed 3 new RDS servers. 2 of the server are working fine, but the third one has a problem.

when I connect to my connection broker i can connect to the fist 2 servers. But the third one will not connect!

from the connection broker I can do everything:

- mstsc works

- ping the problem server -> OK

- telnet to the RDS on 5203, 4 and 5

I reinstalled the terminal server role of windows and quest. still no luck.... :-(

what can I do?

October 18th, 2013 07:00

Hello,

Can you check on the RDSH server to see if it has a Quest Data Collector installed and started ?

If you do, you can turn on Data Collector logging and this will confirm what the issue is. We normally prefer that you raise a case though when we start turning logging on.

Thanks, Andrew

43 Posts

October 17th, 2013 12:00

Hi Andrew,

At the server itself the server can initialize. but from the broker it cannot initialize

Capture.PNG

the image is taken from the broker. if I initialize from the problem server the server turn green, and that is ok :-)

October 17th, 2013 12:00

Hi Sander,

Did the machine initialize in the console OK? Can you send a screenshot through of the error?

Thanks.

October 17th, 2013 14:00

Hello,

Ok, that's not the initialize I was looking for. I was talking about this:

initialize.JPG

So, do Users still get logged onto that TS?

If it is just connecting to the server in the management console, to view user sessions etc, then this issue is normally caused by broken wmi.

David had a solution for rebuilding WMI that fixes this. Let me know which issue you have - if it's the wmi issue, I'll dig out Dave's solution,

Thanks, Andrew.

43 Posts

October 18th, 2013 05:00

Andrew,

the screenshot in your reply is not for us. We still use physical RDS servers.

And because of that the broker cannot connect to the RDS server it also not possible to connect as a TS user to that server.

I think it is the WMI. In the eventviewer I see a Event ID 10 - Source WMI with the following message:

 

Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

43 Posts

October 18th, 2013 06:00

Andrew,

I just rebuild the WMI to follow the instuctions on: https://support.quest.com/SolutionDetail.aspx?id=SOL88861

still no luck :-(

43 Posts

October 18th, 2013 07:00

Andrew,

I just created a case #2295115 :-). how can I enable logging?

October 18th, 2013 07:00

I've grabbed that case now. Thanks.

No Events found!

Top