[vpn-help] Problem with static vs automatically assigned IP for virtual adapter
Benedikt Bauer
mastacheata at gulli.com
Mon May 14 19:25:30 CDT 2012
Hello everyone,
I've got a strange problem/situation I don't understand.
IKE Phase 1 is established successfully, but my Phase 2 is rejected
because no matching inbound policy can be found.
The connection general tab is set to use a virtual adapter and when the
adapter should automatically assign an IP address the VPN Client doesn't
seem to set the correct security policies itself.
Remote LAN is 192.168.0.0/24, local LAN is 192.168.99.0/27
The VPN Client always trys to assign 192.168.99.16 to the virtual adapter.
If I assign anything but 192.168.99.16/32 to the virtual adapter IKE
Phase 2 fails.
I've got another 2 computers with The Greenbow VPN Client that work fine
and both of them have not assigned any static IP address to their
virtual adapter. (VPN Client Address: 0.0.0.0)
Can anyone explain to me why that doesn't work with automatically
assigned IPs instead of static IP?
Regards,
Benedikt Bauer
More information about the vpn-help
mailing list