• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Weird Remote Desktop problem

kumquat

Supreme [H]ardness
Joined
Dec 7, 2005
Messages
5,269
I reinstalled Windows XP (w/SP3 slipstreamed) over the weekend. I did all the usual stuff, nothing too exciting, turned some services off, installed the AMD and nVidia drivers, replaced Notepad with Notepad2, and changed the remote desktop port.

So here's the problem:

When I try to connect to the machine using Remote Desktop without a port number, the connection times out, as expected.

When I try to connect using the correct port number, nothing whatsoever happens. I press Connect, the options gray out while it tries to connect, then about 2 seconds later it drops back to the connect dialog as if I didn't push anything.

No error.

If I select "Warn me" in the Server Authentication box on the Advanced tab, I get the "identity of remote computer cannot be verified" dialog box.

  • This happens whether connecting from the LAN or remotely, using a computer using either XP SP2 or SP3.
  • Remote Desktop is enabled in System Properties, and there is at least one user name allowed to connect remotely.
  • The Terminal Services, RPC, and Fast User Switching services are started.
  • Windows Firewall is disabled, and no other firewall is installed on the system.
Any ideas?
 
Format and totally clean reinstall.

Admin account has a password.

Turned off Security Center, System Restore, Wireless Zero Configuration, and Help and Support. Maybe one or two others, can't remember at the moment.

I'll try the Winsock repair thing when I get home. Thanks for the link.
 
Back
Top