RDP Not working

[J Z]

I have a vista ultimate machine, I had RDP setup and working flawlessly and all of a sudden it just quit working, it says it can't connect to the pc or address. I have my router and everything set up correctly I even tried starting from scratch I can be fairly certain the problem does not lie there.

I made sure rdp was enable under my computer properties, I also made sure it was set to 3389 in the registry. I turned the firewall of to be sure it wasn't that and also went into group policy and made sure it was enabled. I have tried it remotly as well as on the local lan. I have searched for awhile and tried a good many things but nothing seems to work, hopfully someone can give me some good suggestions.

[brandnewfantx]

is it Vista to Vista or XP to Vista ?

Check the settings "All connections from computers running any version of remote desktop (less secure)"

[J Z]

  brandnewfantx said:

is it Vista to Vista or XP to Vista ?

Check the settings "All connections from computers running any version of remote desktop (less secure)"

I have tried it from both and neither work.

I do have that setting checked it doesn't make a differance.

[k22]

is the "terminal services" service set to "manual" and "started" under Control Panel, Administrative Tools, Services?

from the command line

telnet x.x.x.x 3389 [Enter] (where x.x.x.x is the ip of the remote machine)

does this give a blinking underscore or a timeout? this will tell you if the remote system is listening for connections on 3389 or not.

[J Z]

  k22 said:

is the "terminal services" service set to "manual" and "started" under Control Panel, Administrative Tools, Services?

from the command line

telnet x.x.x.x 3389 [Enter] (where x.x.x.x is the ip of the remote machine)

does this give a blinking underscore or a timeout? this will tell you if the remote system is listening for connections on 3389 or not.

it blinked for a little bit and then said that the connection could not be opened on the host on port 3389, connect failed.

[k22]

  J Z said:

it blinked for a little bit and then said that the connection could not be opened on the host on port 3389, connect failed.

then the service isn't running on the remote computer on 3389 or something is blocking it.

can you even ping the remote computer?

[J Z]

  k22 said:

then the service isn't running on the remote computer on 3389 or something is blocking it.

can you even ping the remote computer?

I can ping it, I uninstalled norten antivirus and security center completely and also disabled windows firewall completely but its still doing the same thing. Any Idea's

[k22]

  J Z said:

I can ping it, I uninstalled norten antivirus and security center completely and also disabled windows firewall completely but its still doing the same thing. Any Idea's

did you verify that the terminal services service is installed and running on the remote machine?

[J Z]

  k22 said:

did you verify that the terminal services service is installed and running on the remote machine?

It is set to automatic and started, there is a terminal services configuration and terminal services usermode port redirector that are both set to manual and not started.

[Dan~]

Are they both on the same domain name like MSHOME, mine wasn't on one machine which didn't allow me to remote in, which was weird :/

[k22]

  J Z said:

It is set to automatic and started, there is a terminal services configuration and terminal services usermode port redirector that are both set to manual and not started.

that could be part of the problem - give us more details on terminal services configuration and terminal services usermode port redirector

the only related service that you should have, assuming these are XP and Vista, is "terminal services". also, my machine (which has not been altered) has the "terminal services" service set to manual and started - you may want to change that back to the default. you wouldn't think that would be an issue but I've seen stranger things happen.

[sc302 Veteran]

on the host computer, do a netstat -a -n and make sure 3389 is open.

[J Z]

  sc302 said:

on the host computer, do a netstat -a -n and make sure 3389 is open.

I'm not seeing it listed as open, the service is running shouldn't that do it? is there another way I can make it open?

[sc302 Veteran]

you are going to have to go through your log files to see if there are any errors associated with remote desktop/terminal services

[J Z]

  sc302 said:

you are going to have to go through your log files to see if there are any errors associated with remote desktop/terminal services

I am getting 2 that I could find:

terminal service start failed. the relevant status code no such interface supported

the terminal server has failed ro create a new self signed certificate to be used for terminal server authentication on ssl connections. the relevant status code was object already exists.

not really sure what either is

[J Z]

I'm getting closer, I added network service to the administrators group and that got 3389 listening when i type netstat -na, but now im getting a error in the event log that says"the terminal server has failed to create a new self signed certificate to be used for terminal server authentication on ssl connections. the relevant status code was object already exists."

I'm also getting another error too "The RDP protocol component x.224 detected an error in the protocol stream and has disconnected the client"

Edited January 7, 2008 by J Z

[k22]

take your event ID and source to http://www.eventid.net/ and see what solutions are available there

[J Z]

  k22 said:

take your event ID and source to http://www.eventid.net/ and see what solutions are available there

I tried that and the site couldn't find either one that i am getting.

[wright97]

I HAVE HAD THE SAME DANG PROBLEM FOR 4 MONTHS! I too added network service account as local admin's group and low and behold the friggin' thing works again!!!

Thanks for the info. I had tried everything with no luck! I had even posted on experts-exchange and no one had any ideas.

[J Z]

  wright97 said:

I HAVE HAD THE SAME DANG PROBLEM FOR 4 MONTHS! I too added network service account as local admin's group and low and behold the friggin' thing works again!!!

Thanks for the info. I had tried everything with no luck! I had even posted on experts-exchange and no one had any ideas.

Glad you got yours working, the one error im getting "the terminal server has failed to create a new self signed certificate to be used for terminal server authentication on ssl connections. the relevant status code was object already exists." its event id 1057 and termservice source in the event viewer. I looked everywhere and only think I could find were a few places telling you to delete the certificate and x509 reg keys. Those are only on a terminal server I believe because I didn't have them on my PC. I have been stuck here for a few days, any help is greatly appreciated though i might be at the end of my rope.

[some random guy]

I had a similar problem with Vista today. I installed AOL version 6 and as a result I had to add both the network service and local service user to the admin group to clear up two problems. I also uninstalled AOL. The two problems I saw was the one in this thread, which adding the network service cleared up, but also a problem with the network in general, which adding the local service cleared up (or vice-versa). It appears I'm back up now, but I recall having an issue with XP in the past similar to what I saw with Vista today, no network icon by the clock, and an empty network connectione folder even though the network was connected and working, and adding the service account to the admin group fixed it, but I'm thinking I read somewhere that it opened up further vulnerabilities with compromised services, but I never found any other way to fix it. Long story short, if you have an IM program installed, try removing it and restoring to a known good day.