Configuring VPN from server to Linksys router

Hi Mike,

Much thanks for the response.

I think we're talking at cross points... ;-)

In Regards to #1, I know that and have ordered one (Linksys rv42). The issue is that my VPN router will not arrive for a few days and in the meantime the client desparately needs me to finish programming their solution, which is why I was trying to come up with a work around that could use what I have available. Think Apollo 13... <g> All I have to work with is a Win 2K Adv Server running ICS and ZA Pro, a rv016 on the clients end and sitting behind the Win2K Adv Server on my end is my Win Server 2003 Dev machine. There are no other options until the router arrives.

As far as #2 the problem existed when I ran WinProxy (somethiung I did to eliminate ICSs influence) and *has* to be on their end because I have several other clients ALL of whom I RD into and they all work fine, even with ICS running. This is the only one that repeatedly drops RD connections (and AOL, et al from inside their network as well). Evidently this is due to one WAN port being static and the other dynamic and load balancing arbitrarily routing traffic to one or the other.

While we're here this (the linksys rv016 wan dual port issue) is a problem they and I could really use some help with. It kills them for all their IM stuff, SSL when they are trying to running credit cards and so on... Anyone run into this?

Anyway, back to the item at hand.

#3 believe me getting rid of ICS is happening...

Again I truly want to thank everyone for their efforts. The situation was (and is) that I am trying to get some sort of work around for a few days so I can get some emergency work done for this client until my hardware solution arrives.

But please do allow me a (or another...<g>) stupid question... once I get my rv42 and set up a router to router VPN with their rv016 will I STILL be able to access my other clients (and other services) via the internet simultaneously and independently of the VPN (I'm assuming so but thought WTH, I should ask...)?

Thanks Again!
Brad

 

Hee hee

OK!

Yes! But if you do make other VPN connections to other locations you will then need to use a client.

OK we no know you had ordered and were no longer looking for other options.

Ok so lets get on that.

This is the key arbitrarily. How are they controlling this. Is there a way to enter and exception for port 3389 (RDP Port) so that it is not switched to the other NIC/IP.

Here is an excellent link from Brian Madden the Terminal services supreeme geek.

http://www.brianmadden.com/content/content.asp?ID=278

This particular artical is about load balancing multiple machines but the principle is the same.

If it was setup correctly it should maintain RDP connectivity.

Paste the lines between the ====== into a txt file named KeepAlives.reg

Backup the existing reg entries and install the reg on their end. These are only for RDP and will effect noting else.
==================================
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
"KeepAliveTime "=dword:0000ea60
"KeepAliveInterval "=dword:000003e8
"TcpMaxDataRetransmissions "=dword:0000000a

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server]
"KeepAliveEnable "=dword:00000001
"KeepAliveInterval "=dword:00000001
================================

If you can, try this. Then see if RDP operates normally.

BTW: How long can you stay on at the longest. And do they seem to get disconnected if left without key board input for a while. If so the above will help. I have used it myself.

Mike

 

That's what I was afraid of. So if one of my other clients decide they want me on a VPN I will have to disconnect and reconnect at the router level to switch between them, correct? IOW, I cannot run simultaneous clients

That's the problem, eveidently the RV016 doesn't allow that as it doesn't (so I've been told) provide for port binding

Thanks for the hack and I'll see if it helps but I'm sure the problem is at the router since when I was able to to connect in via a client VPN I could connect to that machine and had no problems.

I guess it's lookng like I may end up having to dump the 2003 install and return to my Adv Svr 2K setup... Good Ole M$...

Anyway, thanks again and should you, or anyone else for that matter, come across a fix for the Server 2003/VPN client BSOD issue please forward it to me.

Best,
Brad

 

Nope you are wrong

You will be able to make other VPN connections even with this hardware VPN router.

Think about it! The VPN router uses no client it will feel to you just like a direct cat5 connection. Within the wan speed limitations of course.

You will not have to disconnect and reconnect.

Understand the hardware VPN is going to be like an internet connection or cat5 or wireless connection "on " all the time!!!!

If you are on, they are on, and internet and routers are working. Network places will show them as availabe just as if you were there in their office. They will see you also from their end.

Now if you decide to connect to another customer via VPN you will then use a client to their specfic IP and could have several different ones.

Remember you said you have no problem except this particular one.

After removing the ICS etc. If you still have a BSOD with VPN (client) it will have to fixed that is for sure but I think it can be.

Example: Connected to this customer via Hardware VPN routers at the same time connected to ACME via one VPN client connection and FMCORP on another.

If this customer is now hot and need you a lot of access now then you get them in order that you don't need all this access.

Then you get a new customer that requires a lot of access, you just reprogram your router to connect to their router (assuming they have a VPN router).

Now you connect to the old customer via a client and to the new customer via routers.

Wait until you get the VPN router up and working and you will see you don't need to dump your 2003.

Cool you jets!!

Mike

 

Yeah, If I could get the BSOD taken care of that would fix all my problems....

BTW, just to be clear, ICS is NOT running on the same computer that the VPN client is causing the BSOD on. The computer the BSOD is occuring on is not running any sort of routing application ICS or otherwise.

Thanks,
Brad

 

Humor me!!

But it has to go thru the other computer that does have.

After ICS is gone I will bet you 1 beer against a case that it will go away. And I will work to extreme to help you fix it if not.

Since I believe this, I need the ICS out of the way first!

But you did understand the rest of my previous post????

I wish I could help until the VPN Router arrives but I can't.
Shoulda overnighted.

One other thing about the VPN Router setup. Not only will you have conectivity but on both of your machines including VPN Clients at the same time. And since you now have a hub/switch you could hook up anothe PC and it would also.

And as for screen real estate, thought about dual monitors?

Let us know.

Good luck
Mike

 

OK. Let me give it a try, I'll see if I can get WInproxy going on the machine. The strange thing is that my Win2K server doesn't barf on the Client VPN and it's running behind ICS (BTW, don't get me wrong I agree that ICS is a piece of garbage) albeit on the same machine...

Yes

Yeah, but at the time it wasn't an issue. I'd already ordered the RV42 so I could shotgun my internet connections (dsl & Cable Modem). Then in the interim, like an idiot, I thought "well, I may as well upgrade..." Stupid... :-(

Actually, I've already got a 6 computer network running locally.

Check my earlier posts... ;-)

Will keep you apprised...

Thanks,
Brad

 

Now my bet is no ICS (all windows) no proxy!

But I hope that cures it, and it is worth a try in the interm.

Mike