[vpn-help] ShrewSoft 2.1.7 and 2.2.0 Issue
mgrooms at shrew.net
Wed Jan 12 15:26:31 CST 2011
On 1/12/2011 2:17 PM, Darren Nye wrote:
> Hi Matthew,
> Unfortunately installing your revised client alpha, didn't resolve the
> issues we're having.
> I'm not clear how to create a virtual adapter or what configuration changes
> I would need to make on both the Jupiter SSG5 and Shrew Client side?
You would have to create a configuration like the one described in the
SSG howto on our support site. Kevin gave some good information on how
the client needs to be re-configured but the SSG configuration changes
need to be made as well ...
I'm not sure why the consultant opted not to use a virtual adapter. It
solves other problems besides MTU and packet fragmentation issues. For
example, if two clients are handed the same DHCP IP address ( because
they are behind different Firewall/NAT devices using the same DHCP scope
), you will have problems with only one of the two working and the other
mysteriously breaking. That's why non-consumer level VPN gateways have
the option to assign private addresses to VPN clients.
That said, the client should also work ( barring IP address conflicts
and bandwidth provider issues ) with the non-virtual adapter mode. Its
just not clear to me what the problem may be at this point. I'm almost
certain that it has something to do with MTU and packet fragmentation.
Unfortunately, Microsoft IP stacks don't have a separate TCP Maximum
Segment Size setting for adapters, only an MTU setting. You could try
adding a MTU registry entry for your public interface adapter on one of
the 'trouble' workstations ( use a value of 1380 ) to see if it helps.
If you are unable to test other configurations, I'm not sure what else
More information about the vpn-help