Comments on: Fix remote desktop connection error "The connection was ended because of network error"

By: Sachin Sable

Sachin Sable — Wed, 03 Mar 2010 11:36:55 +0000

Thanks for the solution. It worked for me. Thanks a lot.

By: SK

SK — Tue, 26 Jan 2010 16:06:05 +0000

This worked great man!!
Initially our machine was not showing any msg, but would show the blurred login screen only after I entered the login name and pass. But after trying to fix this issue for 5-6 hours we got the following msg the next day :
“The connection was ended because of network error”
Which led us to this article and then things got working

Thanks!!

By: Jason

Jason — Fri, 15 Jan 2010 00:25:16 +0000

I was pulling out my hair as well after viewing the fix to resolve our RDP connection it worked so thank you so much for your help really, really appreciated

By: Dan Frederick

Dan Frederick — Sun, 03 Jan 2010 03:13:38 +0000

I connected an Epson Artisan 810 (all in one) printer to my home network; a desktop (Win7) a laptop (Win 7) another laptop,(XP) and a netbook (Win 7 starter). After installing Epson software with new Windows 7 drivers, every device printed. However, after some time, perhaps 20 – 30 minutes, most devices will not print. It appears that the router, Buffalo WZRZ-G300N “sleeps” and when it does, no one prints except the desktop. The printer is connected to the router. I first tried printer completely wireless and that didn’t work. Any ideas?

Thanks,
Dan

By: Jason

Jason — Mon, 16 Nov 2009 20:22:24 +0000

that worked thank you

By: wahpong

wahpong — Fri, 16 Oct 2009 06:16:01 +0000

! Oh work amazing 555

Thank you

By: changi south

changi south — Fri, 16 Oct 2009 02:56:09 +0000

thanks ! good karma for u!

By: shane

shane — Mon, 05 Oct 2009 15:29:05 +0000

I just deleted and recreated the RDP connection and it worked just fine too.

By: Abhishek Gupta

Abhishek Gupta — Wed, 24 Dec 2008 07:16:37 +0000

Hi,

This is amazing it really fixed the problem.

Thanks alot.

By: JJK

JJK — Wed, 29 Oct 2008 08:16:06 +0000

Perfect, this fix worked on a fresh Windows 2003 Server, created from a template to run virtual in vmware esx 3.5
Thanks