Linksys QuickVPN + Remote Desktop

aftrshock · 08-27-2008, 04:34 PM

Hi folks.

Currently using Linksys QuickVPN client to create a VPN; Linksys RVS4000 on one side and a laptop on the other.

VPN connects fine; I can ping my server address (in this case, 10.10.10.50), and my remote desktop target (10.10.10.108). . . . however, I can't get the remote desktop to function.

The user is grouped under mobile user, remote web workplace, and domain user (and domain admin), and I get the blue screen and the yellow dropdown bar, but no login, and connection failed.

Ideas? Need more info?

**djaburg** · 08-29-2008, 09:22 AM

I've used Linksys products for a long time and the one thing that I've noticed is that the QuickVPN product, most recently on the RV016 router (having also seen the same thing on the RV042 and WRV54g), seems to lack the consistent bandwidth to effectively do any remote work with large files, database access, or remote desktop. I used to attribute that to the client-side speed or the host-side speed, but I've also replaced the linksys product with a sonicwall TZ150 and it worked absolutely perfect with all things being the same except the router. Not sure if it's the encryption algorithm they're using, or their implementation of SPI, hard to say. If it's at all possible you can test my theory by trying to enable the VPN host portion of your server and connect directly to that instead of using the quickvpn and see if it still does that.

aftrshock · 08-29-2008, 12:14 PM

That's what I've done the most recently... Maybe part of my issue is that the quickvpn gives connectivity, but you'd have to institute yet another connection to gain internal IP addressing. I went to Windows VPN instead; we'll see if that works or not.

08-27-2008, 04:34 PM	#1 (permalink)
aftrshock Registered User Join Date: Feb 2007 Location: Bay Area, CA Posts: 48 OS: Multiboot: XP,2k, Ubuntu 6.10	Linksys QuickVPN + Remote Desktop Hi folks. Currently using Linksys QuickVPN client to create a VPN; Linksys RVS4000 on one side and a laptop on the other. VPN connects fine; I can ping my server address (in this case, 10.10.10.50), and my remote desktop target (10.10.10.108). . . . however, I can't get the remote desktop to function. The user is grouped under mobile user, remote web workplace, and domain user (and domain admin), and I get the blue screen and the yellow dropdown bar, but no login, and connection failed. Ideas? Need more info?

08-29-2008, 09:22 AM	#2 (permalink)
djaburg TSF Enthusiast Join Date: May 2008 Posts: 1,319 OS: XP SP3/Vista/7 Server 2K/2K3/2K8	Re: Linksys QuickVPN + Remote Desktop I've used Linksys products for a long time and the one thing that I've noticed is that the QuickVPN product, most recently on the RV016 router (having also seen the same thing on the RV042 and WRV54g), seems to lack the consistent bandwidth to effectively do any remote work with large files, database access, or remote desktop. I used to attribute that to the client-side speed or the host-side speed, but I've also replaced the linksys product with a sonicwall TZ150 and it worked absolutely perfect with all things being the same except the router. Not sure if it's the encryption algorithm they're using, or their implementation of SPI, hard to say. If it's at all possible you can test my theory by trying to enable the VPN host portion of your server and connect directly to that instead of using the quickvpn and see if it still does that. __________________ Computers make it easier to do a lot of things, but most of the things they make it easier to do don't need to be done. The inherent vice of capitalism is the uneven division of blessings, while the inherent virtue of socialism is the equal division of misery.

08-29-2008, 12:14 PM	#3 (permalink)
aftrshock Registered User Join Date: Feb 2007 Location: Bay Area, CA Posts: 48 OS: Multiboot: XP,2k, Ubuntu 6.10	Re: Linksys QuickVPN + Remote Desktop That's what I've done the most recently... Maybe part of my issue is that the quickvpn gives connectivity, but you'd have to institute yet another connection to gain internal IP addressing. I went to Windows VPN instead; we'll see if that works or not.