Client could not connect to the remote computer windows 2000

Collectives on Stack Overflow. Learn more. Ask Question. Asked 5 years, 2 months ago. Active 4 years, 4 months ago. Viewed 9k times. Improve this question. Manny Manny 71 1 1 silver badge 11 11 bronze badges. Add a comment. Active Oldest Votes. Improve this answer. Rohit Chopra Rohit Chopra 1 1 gold badge 4 4 silver badges 11 11 bronze badges. You're amazing, thank you so much! I will give these a try and will keep you updated. Windows Server TechCenter. Sign in.

United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums.

Remote Desktop Services Terminal Services. Sign in to vote. After 30 seconds or so the following error is displayed: The client could not connect to the remote computer. Connections to the session broker farm are load balanced using DNS round robin There is nothing ovbious in the event log and both servers have plenty of free resources. Enter computer name or IP address and select OK. Firewalls between your computer and the affected server may prevent successful connection. Remote Registry service should be running on the server.

Choose the connection you want Terminal Services to use. Using the GUID you noted in step 5 select subkey. It's LanaId. Change it's data to the value you noted in step 6. All such information and related graphics are provided "as is" without warranty of any kind.

Skip to main content. This browser is no longer supported.