Solved remote desktop

September 10, 2009 at 11:56:22
Specs: Windows XP

can't connect remote desktop connection
frustrated - used to have RDP working fine from home to office where I have a small LAN - no changes in router or configuration but now can't connect. Computer I am trying to connect TO is WinXP Pro SP3 - port forwarding is on as before and it is set to a static address within the LAN. To minimize confusion, I have tried using another computer on the LAN to connect to it and get the same error message - not even able to establish a connection (windows networking is otherwise fine). I am able to ping that computer, I am able to telnet the computer on port 3389 and connect. I am able to connect FROM that computer to another on the LAN running XPPro SP3 (using RDP). I have Norton AV - uninstalled it in case it was blocking with an update with no change. I even uninstalled SP3 to go back to SP2 to see if something had changed there with no luck.
To be clear - the error message that I get is a rotation of messages - network error, data encryption error - never do I get to the point of trying to give credentials to logon. Help.

See More: remote desktop

Report •


✔ Best Answer
September 11, 2009 at 14:03:41

You can also click the the errors for more information from web on the event logs.

See this but it shouldn't apply to you. (opps, yes, I didn't see one line)
http://support.microsoft.com/kb/323497
Again here
http://www.windowsreference.com/win...

Playing to the angels
Les Paul (1915-2009)



#1
September 10, 2009 at 11:59:24

can you rdp from pc to pc on the lan?

Report •

#2
September 10, 2009 at 12:00:48

I am able to RDP FROM the computer that I want to connect to on the LAN TO another on the LAN but cannot do the reverse (both XP Pro), When I pinged it and used telnet to connect, both were done from the other XPPro computer on the LAN

Report •

#3
September 10, 2009 at 12:39:34

You don't have a wan/router or forwarding problem then.

Did you review the firewall settings? I would suspect its blocking access.


Report •

Related Solutions

#4
September 10, 2009 at 12:50:53

I played with both windows firewall and Norton. With windows firewall (which is generally turned off), I was able to confirm that when I turned it on and unselected RDP as an exception, it blocked my connection on 3389 (using telnet from the other computer on the LAN). When I select RDP as an exception, or when I turn Windows Firewall back off, it allows connection so it seems to be working as it should. It is generally turned off. I did uninstall Norton with no change in my connection ability. Also - if Norton was blocking the RDP connection, would it still allow the telnet connection? That's the part that confuses me. I may just uninstall it again to be certain but any other suggestions?

Report •

#5
September 10, 2009 at 14:16:46

What is the exact error.

See also event logs.

Could it be a udp issue?

Playing to the angels
Les Paul (1915-2009)


Report •

#6
September 10, 2009 at 14:28:15

jefro:
The exact errors read: "The computer can't connect to the remote computer. The connection was lost due to a network error. Try connecting again ..." and interspersed with "Because of an error in data encryption, the session will end. Please try connecting to the remote computer again." Note - I uninstalled Norton Internet Security and same problem. Sorry but where do I find the event logs? I'm not as computer literate as I am trying to be. I wouldn't know how to tell if it is a udp problem. If it helps, I am trying to connect to the offending computer using RDP with both the LAN IP address (which is what I use to successfully connect with telnet) and the computer name - both give the same errors.

Report •

#7
September 10, 2009 at 15:50:35

Your telnet config is messing with your testing.
Correct the registry entries for RDP back to 3389
uninstall norton on both
disable the windows firewall on both
use only ip address

to troubleshoot you eliminate everything but the basics and then you build up from there. Right now you are a long way from basics.

You need to get basic pc to pc connectivity via rdp before you move on to via the internet.

Unless you are trying to stream sound the udp protocol is irrelevant.
Event viewer logs are under Administrative Tools


Report •

#8
September 10, 2009 at 18:27:37

wanderer: Thanks for your help - at this point I thought I was down to the basics - I am trying to connect using RDP on two computers over a LAN - neither have Norton (one didn't have it and the one I can't get RDP working on I have uninstalled it), windows firewall is disabled on both and I am trying to use the RDP connection with ipaddress. I mentioned the telnet ability to connect since this meant to me that the port was open. From my limited knowledge it seems that the problem is with RDP itself on the computer that I want to connect to but I am trying to eliminate other potential sources of interference. I have not changed the registry entry for the RDP port - it is set and appears to be listening at 3389.
Is there something specific I should be looking for in the event logs?

Report •

#9
September 11, 2009 at 08:11:55

go to services. is terminal services started on the pc you cant rdp to?

doubt the logs have anything but you can review the security and application log for errors related to networking, services not starting or access denied errors.


Report •

#10
September 11, 2009 at 11:50:46

I checked and the terminal service is started. In the event logs there are errors under system, notably "The RDP protocol component "DATA ENCRYPTION" detected an error in the protocol stream and has disconnected the client." under Source: TermDD and another DCOM that states it is unable to find a file wmiprvse.exe and one in Applications that indicates a WMI Adapter failure to open. Unsure if any are significant. Thanks for chewing through this one with me.
PS - may be onto something here - each time I try to connect to the computer it adds another error to the services log with "The RDP protocol component "DATA ENCRYPTION" ... Could this component be corrupt?

Report •

#11
September 11, 2009 at 13:27:04

Sounds like you are using unlike versions of RDP. What are the operating system versions you are using and what is the service pack level?

Personally I hate RDP and use VNC, it works so much better.


Report •

#12
September 11, 2009 at 14:03:41
✔ Best Answer

You can also click the the errors for more information from web on the event logs.

See this but it shouldn't apply to you. (opps, yes, I didn't see one line)
http://support.microsoft.com/kb/323497
Again here
http://www.windowsreference.com/win...

Playing to the angels
Les Paul (1915-2009)


Report •

#13
September 11, 2009 at 14:18:56

That last link jefro appears to be the answer. Good job

Report •

#14
September 12, 2009 at 18:41:15

That did it. Thanks to all.

Report •


Ask Question