Recent content by IfAtFirst

Moving towards a solution using SSH's last gasp guidance: 'Don't confuse me with virtual adapter address and gateway info,' says the VP41, 'Just use ANY / ANY.' This helped. I connected and did well with the VP41s in another tabletop setup. With Sentinel (but not with SoftRemote), I can...

I seem to have spoken to soon of my presumption of limted success with using a software client to talk to a Linksys router - putting each on distinct LAN segments. A tabletop setup using 2 (BEF)SX41s worked as I described. In the real world, I placed VP41s at my target sites. I liked their...

wa1dar: Thanks for comments. They spurred me to return to some experiments, where I paid close attention to routing tables on the machines hosting Sentinel and SoftRemote. These yielded some results I discussed in a similar thread I started in the VPN forum. I guess you picked up on some...

Thank you (so far) to Paul, themut, and lgarner (and to wa1dar who answered nearly the same question in the Remote Access forum). My further discoveries have been that I can put the target on a subsegment of 192.168.1.0/24 - say 192.168.1.0/27, and I can get the remote client with a virtual...

It's true. When doing router-to-router VPNs, like Linksys (BEF)SX41s and VP41s, you cannot talk to someone with the same DNA (IP address on the same segment) through a tunnel. You must use distinctly different segments at each end, or a packet in the tunnel doesn't know which way to turn...

or red book? Is there any documentation or experiences with virtual addresses working? They are supposed to be able to land you on the same LAN segment - 192.168.1.114 should be able to gain access to 192.168.1.0, when things go right. But they don't. When targeting a Linksys BEFVP41...

Virtual addresses for Sentinel/SoftRemote clients are purportedly able to get you onto the same LAN segment as that implied by the virtual address. E.g., my target is a faraway segment: 192.168.1.0 (with LAN gateway at 192.168.1.50). I set my virtual address at 192.168.1.114 and these software...

I experienced this problem on SSH-Sentinel, and then upgraded to its commercial successor - SafeNet's SoftRemote - but continue to be virtually shut out of my target LAN. Target LAN is accessed by Linksys (BEF)VP-41, with static IP address on the Net. Subnet there is 192.168.1.0 255.255.255.0...

Linksys BEFSX41 is one of cheapest, but only does 2 tunnels. BEFVP41 does 70, and is worth the extra $50 (street). Once you get a tunnel configuration working, you don't want to tear it down, if you are experimenting with another setup. You may well experiment. Once you've gotten...

Pro machine must be target. Home machine is remote "client" which initiates connection. Vice versa isn't accommodated by Microsoft. Go to "Help and Support" on your start button on either machine. It starts up a viewer widget in which you can search for topical...

You can store different VPN connections, but can only use one at a time in XP

ekyjim's rate of 1MB/min is similar to what we experience using Linksys routers. We also know the upload and download rates are not the constraint. We have NetBIOS info trafficking thru the tunnel. I'm guessing ekyjim had NetBIOS broadcasting on, if he was grabbing individual files. We...

We have a Linksys BEFXS-41 (a 2-tunnel baby VPN router) working successfully behind a Zyxel 645.

On the other hand, when you read threads by "Markku" ( http://www.tek-tips.com/userinfo.cfm?member=markku ), who appears to have a keen sense of things with Linksys routers, you sort of get the message that the WRV54G is a work-in-progress. Caveat emptor, I guess.

VP41's are more stable - I'm guessing because of more processing power, including separate chip for the encryption duties. SX41's were more crashy. Configuring them is very similar - just check out the userguide PDF's - which you can download and peruse ahead of purchasing whatever you buy...