Home > Remote Desktop > Remote Desktop The Connection Was Ended Because Of Network Error

Remote Desktop The Connection Was Ended Because Of Network Error

I am able to connect FROM that computer to another on the LAN running XPPro SP3 (using RDP). WARNING: Always back up the registry before making changes. Suresh November 6, 2011 at 12:18 am Superb. Thanks to the 800+ of you... navigate here

Microsoft Enterprise Mobility + Security (EMS) delivers identity-driven security without getting in the way of your users’ productivity experience.... Suresh August 13, 2008 at 6:16 am Great stuff, works wonders now. It also talks about some of the basic settings to enable remote desktop sessions which are covered in symptom 1 above. I am an admin on a LAN that has a few hundred XP boxes. 2 of them gave an error when trying to connect via Remote Desktop: The connection was ended http://kb.parallels.com/en/123855

Have a look at this EventID page for ideas. For full access please Register. 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've marked this thread as 'Resolved'. Tony Hill March 18, 2008 at 7:19 am Thanks for this solution, i was pulling my hair out trying to work this out. If you have a question to ask us, submit your question at Answers By Trouble Fixers. Report • #2 hateswindows 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

Sanjay Mishra March 29, 2011 at 12:41 pm Thanks a lot i was working in this issue for 5 hours after that i fixed this issue through your solution. Similar Threads Remote Desktop Connection michaelj, Jul 10, 2003, in forum: Windows XP Networking Replies: 0 Views: 266 michaelj Jul 10, 2003 Re: Unable to Use XP Remote Desktop Connection Steve 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 great post to read Beside application and system event logs, some other detailed TS/RDS event logs will logged under: Event Viewer\Custom Views\Server Roles\Remote Desktop Services Event Viewer\Applications and Services logs\Microsoft\Windows\TerminalServices-LocalSessionManager, TerminalServices-RemoteConnectionManager.

Sign Up Now! Please check the event viewer. By continuing to use this site, you are agreeing to our use of cookies. How are things going?

Please try connecting to the remote computer again A frequent cause of these problems stems from issues with some registry values in the TermService\Parameters registry key. https://softwaretesttips.com/2014/03/06/the-connection-was-ended-because-of-a-network-error-please-try-connecting-again-to-the-remote-computer-again/ This article summarizes the various causes for Terminal Server Client (Remote Desktop Client) connection failures and how to fix them. Open Start >> Run and type regedit and press enter. 2. Thank you , TomTom Monday, August 20, 2012 7:31 PM Reply | Quote All replies 0 Sign in to vote Hi, Thanks for your post.

Thanks! http://supercgis.com/remote-desktop/remote-desktop-connection-error-unable-to-open-connection-file.html Fantastic. I am able to ping that computer, I am able to telnet the computer on port 3389 and connect. Just click the sign up button to choose a username and then you can ask your own questions on the forum.

I spent a few days trying to fix it and there were a ton of articles and blogs that offered several solutions that didn't work. good karma for u! I had come across the DE problem a while ago but did not think of it. -- Uncle John Can't find your answer ? his comment is here No, create an account now.

Forum The remote computer disconnected the session because of an error in the licensin Forum SolvedUsing remote desktop connection without password Forum SolvedRemote Desktop Connection Issue Forum Solvedremote desktop connection Forum Most were geared toward the Terminal Services server. Get the answer Anonymous 5 August 2005 06:29:11 Archived from groups: microsoft.public.windowsxp.general (More info?) Chris, That is very good news.

If you like this article or this article helped you, you can +1 to recommend this article on google plus.

Read more Load More... Any ideas? thank u. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.Would you like to participate?

Articles & News Chart Forum Business Brands Tutorials Other sites Tom's Hardware,The authority on tech Search Sign-in / Sign-up Tags : Graphics Cards CPUs Motherboards Enterprise Storage Cases Cooling Apple Notebooks Ask ! Associated Event IDs: Event ID: 50 The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client. weblink Please read the User Guide for more information.Click to expand...

The connection was lost due to a network error. Michael Wakari July 9, 2008 at 8:00 pm it's work. Forum More resources Read discussions in other Windows XP categories Configuration Customization Drivers Security Video Ask the community Tags Example: Notebook, Android, SSD hard drive Publish Top Experts a b δ Akash May 13, 2008 at 6:15 am Aaah, you're a lifesaver!

I changed the RDP Security Layer to Low and I still get the error message when I try to connect to the Terminal Server... (I did not reboot the server... When I try to connect from the RF I still get the The connection was ended because of a network error. Click on it to mark your thread as solved.