unable to connect

  • Thread starter Thread starter Brian Paap
  • Start date Start date
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?
 
Is there any event log entry on second node? is RDP-Tcp on second node
enabled, you can check in via tscc.msc
 
Back
Top