unable to connect

B

Brian Paap

I currently have 2 w2k servers set up in a cluster. I am
also running Terminal server on both nodes. I am able to
connect to the 1st node without any problems, but an
unable to connect to the second nose. I receive the
following error "remote connection might not be enabled
or the server may be too busy to accept connections"

I have shecked and the service is running. I also ran
netstat -an and found that the second node does not show
that it is listening on port 3389. I checked the
registery of both machines and the port number listed is
the same for both machines.

Does anyone have any ideas?
 
H

Huei Wang [MSFT]

Is there any event log entry on second node? is RDP-Tcp on second node
enabled, you can check in via tscc.msc
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Remote desktop over the internet 2
client could not connect to the terminal server. 1
Termsrv not listening on 3389 0
Remote Desktop disconected error 3
Unable to Connect to TS 2000 1
NLB with Terminal Srvr 3
Cannot Connect to TS over VPN 3
clients cannot connect 4

Top