I've recently installed an SBS2003 standard network at a client, and 8 of the 10 pcs can be accessed in the normal fashion via RWW remotely and internally. Two of the PC's fail with the usual error of "Cannot connect to the remote computer. Be certain its turned on and connected to the netowrk. Netowrk congestion problems could also be causing this, etc, etc". I can generate this identicla error on both pc's when attemting to connect via Rww either internally or externally. I've checked that "allow remote connections" and included the user name is ticked in the remote tab of my computer properties. Netstat -a shows that each of these 2 PC's are NOT Llistening on port 3389. I've checked the registry to be sure the port is correct (3389) and that Tservdeny connections is set to 0. Windows firewall has the remote desktop exceptions included and is turned on for the LAN connection via group policy. I've unchecked the "allow remote connections in the "remote" tab , rebooted, then re-enabled without success....
My issue is that while terminal servicies shows as started and auto launch in SERVICES, it apparently is not listening on the port. No wonder rww fails! So how do I "reinstall/repair" terminal services on these 2 pcs? I CAN connect outbound from each to the server using the RDP client (latest version). I've googled and looked for other ideas, and see that others have had similar issues, but no ready solutions.....
Thoughts?
Thx Norm
|