2 BEFSX41's connected... now what?

[jharlan]

To start... Linksys tech support is LAME!

I set-up 2 BEFSX41's according to Linksys's support page.

BEFSX41 Number #1
Local Secure Group: Subnet 192.168.0.0
Remote Secure Group: Subnet 192.168.1.0
Remote Secured Gateway: FQDN

BEFSX41 Number #2
Local Secure Group: Subnet 192.168.1.0
Remote Secure Group: Subnet 192.168.0.0
Remote Secured Gateway: FQDN

Pressed "Connect" on both 41's. Both say "Status: Connected"

VPN logs say:

IKE[1] Set up ESP tunnel with [WAN IP ADDRESS] Success !

So I think all looks good, but now what?

My Goal: Have an XP Pro on Network #2, with IP 192.168.1.6 that needs to mount a directory on Windows 2000 Server on Network #1, with IP 192.168.0.2.

How do I do that? Tried XP Pro's Network Set-up for a VPN, but not sure.

Please help.

Jim.

[YeOldeStonecat]

Not Linksys supports responsibility to support your own network, just the routers.

If you have it configured to allow Netbios to pass, you should easily be able to browse and find the "other" network in network places. Can you ping the server from the remote workstation? Should be able to see it.

Netbios passing through can bog down your VPN tunnel if you don't have a lot of upstream bandwidth. In those cases, better off doing local host file on the remote machines to help them resolve by name.

[jharlan]

K.

I'm on the 192.168.1.0 network, and can ping the 192.168.0.1 gatewa/router. I created an LMHOSTS file in the proper directory of the XP Pro machine.

I can "Explore" to \\Remote_Machine_1\ (windows 2k pro),
to \\Remote_Machine_2\ (w2k pro), BUT NOT TO \\Remote_Server\ (Windows 2000 Server). The Remote_Machines ask for a username/password, which I supply, but the Remote_Server does nothing.

Is this now a Windows 2000 server issue?

Thanks.

Jim.

[jharlan]

UPDATE.

At Windows 2000 Server, I enabled "Web Sharing" for the directory and Voila! Everything works.

BUT... it appears that after sometime (like over night), the BEFSX41's drop the VPN connection. I can re-establish via the admin page of the routers, but that is REALLY burdensome...

Can the remote users re-establish the VPN by simply trying to access the H: drive that is mapped to \\Remote_Server\Directory?

What about the Linksys's VPN Advance settings like "NetBIOS Broadcast" or "Keep-Alive?"

Please help.

THanks.

[YeOldeStonecat]

Keep Alive helps. NetBIOS...that will slow things down a bit, adds a lot to the traffic, which depending on how much actual bandwidth you have...can slow down the VPN tunnel.

Both ends static IP addresses? (meaning the actual DSL account, the WAN IP)

Latest firmware on the routers?

If the VPN tunnel is vitally important, you may want to look at more robust routers, such as Sonicwalls. They're lightening fast, and bulletproof reliability. Naturally, at 10x time cost of a Linky.

But for 75 bucks per, the little SX Linkies do OK, just a bit slower, and as you'll see, sometimes that VPN tunnel drops.

[jharlan]

Will add Keep-Alive on both BEFSX41's.

Have a FQDN on both for dynamic IPs... nice feature of the BEFSX41's to include the DDNS update capability.

Yes, latest firmware on both... 1.50.9, March 17, 2004.

And for the cost... very nice.

Thanks for the help.

Jim.

[YeOldeStonecat]

Originally posted by jharlan
Will add Keep-Alive on both BEFSX41's.

Have a FQDN on both for dynamic IPs... nice feature of the BEFSX41's to include the DDNS update capability.

Yes, latest firmware on both... 1.50.9, March 17, 2004.

And for the cost... very nice.

Thanks for the help.

Jim.

Hmm...I haven't done them that way, just with static IP's at both ends. I've tried to stay away from DynDNS stuff.

[Duzmor]

Cat - I have a Linksys BEFsx41 Great router- But Jharlan is say the Firmware is March 17,2004 #1.50.9 - But Linksys Support is saying that the Firmware is Version is 1.45.3 - 9/26/2003

Were is the Firmware Version 1.50.9 - ????

Duz !!