Home > 4612 the > 4612 the connection was ended because of a network error

4612 The Connection Was Ended Because Of A Network Error

Links HelpWithWindows.com RoseCitySoftware.com Recommended Links Menu Log in or Sign up Search Search titles only Posted by Member: Separate names with a comma. Newer Than: Search this thread only Search this forum only Display results as threads Useful Searches Recent Posts More... WindowsBBS Forums > Internet & Networking > Networking (Hardware & Software) > This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations. Cookies Registration Notice Resolved Error: The connection was ended because of network error. Discussion in 'Networking (Hardware & Software)' started by Mithun, 2009/07/01. 2009/07/01 Mithun Inactive Thread Starter Joined: 2008/04/21 Messages: 186 Likes Received: 0 Trophy Points: 106 Computer Experience: intermediate Hi, I am trying to connect another system using RDP protocol but it is giving me error message "The connection was ended because of network error. Please try connecting to the remote computer again".I have checked on remote computer that both the options a> All remote assistance invitation and Allow users to connect remotely are enabled and also firewall is disabled on remote computer.Both the computers are connected through Lan and also show connectivity.My system configuration is OS : WINDOWS xp Mithun, #1 2009/07/01 Arie Administrator Administrator Staff Joined: 2001/12/27 Messages: 14,743 Likes Received: 374 Trophy Points: 1,093 Any events listed in the System Event log? Support WindowsBBS Arie, #2 Log in or Sign up to hide this advert. 2009/07/15 Mithun Inactive Thread Starter Joined: 2008/04/21 Messages: 186 Likes Received: 0 Trophy Points: 106 Computer Experience: intermediate Arie said: ↑ Any events listed in the System Event log?Click to expand... THE RDP PROTOCOL COMPONENT "DATA ENCRIPTION" DETECTED AN ERROR IN THE PROTOCOL STRAM AND HAS DISCONNECTED THE CLIENT. Event ID: 50 Mithun, #3 2009/07/15 Arie Administrator Administrator Staff Joined: 2001/12/27 Messages: 14,743 Likes Received: 374 Trophy Points: 1,093 Have a look here: "The RDP Protocol Component "DATA ENCRYPTION" Detected an Error..." error message Support WindowsBBS Arie, #4 2009/07/16 Mithun Inactive Thread Starter Joined: 2008/04/21 Messages: 186 Likes Received: 0 Trophy Points: 106 Computer Experience: intermediate Arie said: ↑ Have a look here: "The RDP Protocol Component "DATA ENCRYPTION" Dete

February 21, 2008 Advertisement Trouble: One of our reader Rameshwar reported us a problem regarding remote desktop connection on windows XP. When he tries to connect to a specific machine on LAN, rather than getting connected Windows xp gives the following remote desktop connection error - "The connection was ended because of network error" Let's see how can we fix this remote desktop connection error. Fix: The main cause behind this problems is some problem in the registry entries at the following path: HKLM\System\CurrentControlSet\Services\TermServices\Parameters Follow the procedure below to fix it. Advertisement 1. Open Start >> Run and https://www.windowsbbs.com/threads/error-the-connection-was-ended-because-of-network-error.85210/ type regedit and press enter. 2. Navigate to the following path: HKLM\System\CurrentControlSet\Services\TermServices\Parameters 3. Now delete registry keys named Certificate, X500 Certificate and X509 Certificate ID values. (These keys will get auto generated after system restart with system default values, which is actually needed) 4. Exit Registry editor and restart your computer. 5. Try to establish a remote desktop connection by typing mstsc at Run Prompt. Note: Always http://www.troublefixers.com/fix-remote-desktop-connection-error-the-connection-was-ended-because-of-network-error/ back up the registry before making any changes that may damage your system configuration. If you like this article or this article helped you, you can +1 to recommend this article on google plus. You can follow us on Twitter or join our Facebook Fan Page. If you have a question to ask us, submit your question at Answers By Trouble Fixers. Looking for something else? Search here : { 29 comments… read them below or add one } dennisb March 4, 2008 at 3:13 pm Awesome. This fix worked perfect when I received this error on a box. Thanks! Tony Hill March 18, 2008 at 7:19 am Thanks for this solution, i was pulling my hair out trying to work this out. Fantastic. Alfred Prospere April 23, 2008 at 4:55 am Thanks, this saved me after two days of searching fro solutions. Well done!! Akash May 13, 2008 at 6:15 am Aaah, you're a lifesaver! Thank you! Michael Wakari July 9, 2008 at 8:00 pm it's work. i just delete certificate key, and it's work. thank u. JB August 11, 2008 at 5:02 am It worked like a charm. Nice article dude. Thanks, you saved me a

network error" Source Link"Trouble: One of our reader Rameshwar reported us a problem regarding remote desktop connection on windows XP. When he tries to connect to a specific http://ricotroubleshooting.blogspot.com/2008/12/fix-remote-desktop-connection-error.html machine on LAN, rather than getting connected Windows xp gives the following remote desktop connection error - "The connection was ended because of network error" Let's see how can we fix http://support.slingbox.com/KB/KB-5000268 this remote desktop connection error. Fix: The main cause behind this problems is some problem in the registry entries at the following path: HKLM\System\CurrentControlSet\Services\TermServices\ParametersFollow the procedure below to fix it. 1. 4612 the Open Start >> Run and type regedit and press enter.2. Navigate to the following path: HKLM\System\CurrentControlSet\Services\TermServices\Parameters 3. Now delete registry keys named Certificate, X500 Certificate and X509 Certificate ID values. (These keys will get auto generated after system restart with system default values, which is actually needed) 4. Exit Registry editor and restart your computer. 5. Try to establish a remote 4612 the connection desktop connection by typing mstsc at Run Prompt. Note: Always back up the registry before making any changes that may damage your system configuration." Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: remote, windows Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Categories Choose a Category 2008 (1) active directory (1) adb (1) address book (1) alias (1) android (7) apple (3) blackberry (1) browser (2) centos (4) chrome (1) cluster (1) database (1) dfs (2) DNS (3) download (1) drivers (2) email (23) esx (4) eventlog (1) exchange (7) exmerge (1) filesystem (8) firefox (1) forum (1) freeware (20) ftp (1) function (1) google (9) hardware (2) HP (6) ibm (2) iLO (1) internet (1) ios (1) LG (1) lotus notes (3) mac (2) management (4) mbr (1) microsoft (19) misc (6) mobile (4) monitoring (2) mysql (1) nagios (3) nas (1) network (4) nexus one (4) nutanix (2) office (2) opensource (17) optware (1) osx (1) outlook (1) pac (1) php (3) powershell (4) print (1) proxy (1) pst (1) putty (2) raid (2) reg

Sign up for our newsletter! Choose your Location and Language Americas United States - English Canada - English Brazil – Portuguese Colombia - Español El Salvador - Español México - Español Europe Austria - English Belgium - English Denmark - English Deutschland - Deutsch Finland - English France - English Ireland - English Israel – Hebrew Italy - English Luxembourg - English Nederland - English Norway - English Spain - English Sweden - English Switzerland - English United Kingdom - English Asia and Oceania Hong Kong - English India - English Japan - Japanese Singapore - English Americas United States - English Canada - English Brazil – Portuguese Colombia - Español El Salvador - Español México - Español Asia and Oceania Hong Kong - English India - English Japan - Japanese Singapore - English Europe Austria - English Belgium - English Denmark - English Deutschland - Deutsch Finland - English France - Francais Ireland - English Israel – Hebrew Italy - English Luxembourg - English Nederland - English Norway - English Spain - English Sweden - English Switzerland - English United Kingdom - English Support System Status All Slingbox network systems are OK View Top Searches View Top Searches Understanding Watch on Slingbox.com error codes Have you received an error code from Watch on Slingbox.com, such as "W-201,"W-202," or "W-211"? Here's a full list of theerror codesand what theymean. Error number Error text that you might see What it means in English Try doing this W100 eInvalidPassword The Slingbox Administrator password that you typed is incorrect. Re-enter the password. W101 eGeneric There was an error connecting to your Slingbox. Try connecti

 

Related content

No related pages.