Remote desktop stop working, was working before


K

kpoon.ca

Hello,

Remote desktop on the XP Pro I have stopped working all of sudden.

* The Terminal Services service is started.


* No errors in the event viewer


* The two Remote Access checkboxes are checked in
the Remote Tab of the System Control Panel


* RDP-Tcp "Port Number" in the registry is set to 3389


* fDenyTSConnections in the registry is set to 0


* TSEnabled in the registry is set to 1


Any help would be appreciated?


i'm stumped for a solution.
 
Ad

Advertisements

K

kpoon.ca

Thanks for your reply, however, I've already checked everything and it
looks normal. I don't know what else to do.
 
K

kpoon.ca

I've also check local policy, all looks fine. Any other suggestion
would be appreciated.
 
S

Sooner Al [MVP]

When did this happen? Meaning did you recently install any personal firewall software or an
anti-virus/trojan/worm protection software package? Some folks report NAV 2005 worm protection kills
Remote Desktop connections.

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...
 
K

kpoon.ca

It started about 3 weeks ago. It has always had Norton Corp 8 in the
system since 2 years ago. It also had Spybot and Lavasoft Adware on it
while RDP was still working. I uninstalled them just to make sure. No
other software has been installed. No firewall, windows firewall
disabled. I've reinstall SP2, double checked all windows update.

The only thing I can think of is that if memory serves me correctly, it
started to happen after I ghosted the harddrive to my new computer if
it makes any sense.

I've also compared registry (RDP related) with another working system,
dll file version, etc.

Still no luck, it disconnects right away, doesn't even get as far for
username and password, therefore no error event log.
 
Ad

Advertisements

S

Sooner Al [MVP]

You might try...

1. Re-registering Remote Desktop using the command line that follows...Reboot the PC after doing
this...

regsvr32 remotepg.dll

2. Otherwise do a repair install of Windows XP.

http://michaelstevenstech.com/XPrepairinstall.htm

NOTE the warnings on the page...
--

Al Jarvi (MS-MVP Windows Networking)


Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...
 
K

Ken

I've tried #1, no luck.

We've recently enabled a Windows 2003 Terminal Licensing Server, would
it have any impact on my XP computer? Just curious.
 
S

Sooner Al [MVP]

Well, now your out of my area when you start talking W2003 Terminal Server and licensing issues... I
suggest you ask about that on this news group...

microsoft.public.windows.terminal_services

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...
 
K

Ken

Thanks Sooner Al,

I actually disabled W2003 licencing on the network, my pc still doesn't
work. Any other PC on the network doesn't have this problem. Anyhow I
think i'm going to give up. If you have any other idea, please let me
know.
I'll try a repair install to see if it helps. Thanks again.
 
Ad

Advertisements

G

Guest

could this also be the problem with Symantec client services v3.01? i've been
using it for about 2 weeks now, and yesterday was the first time i was out of
town again and as such, forced to remote desktop in.. which of course didn't
work.. i get the login screen, i login properly, only then the video hook
driver seems to be dead/get killed instantly. i can't currently access the
workspace locally and as such have no way of testing this to be true.. but it
seems mighty annoying if it were the case (and symantec would have to be
informed of it as well, i guess)

thanks in advance
 
Ad

Advertisements


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

Top