[Vpn-help] pcf cert file - connects after install never again after reboot 64bit Windows7

[Tony Hemy]

Hey Matthew,

One thing I have found is that on the work domain it work perfect, its only at home I get the issue.

As such I have ordered a better router, that explicitly lets me set VPN Pass thru... 

I won't get that till Thursday night, and will try it then.

My current router is a cheap little old thing, I do have MAC address filtering on it, and I did set the MAC I saw on the Shrew in the allow list, but tonight I will turn off MAC filtering completely and see if that works.

Now I just need to get my other Check Point VPN-1 Secureclient P12 Cert to work... any suggestion there?

I'll keep you updated.

t

Tony Hemy  Senior Developer/Team Lead Dynamics NAV


-----Original Message-----
From: Matthew Grooms [mailto:mgrooms at shrew.net] 
Sent: December-02-09 12:48 PM
To: Tony Hemy
Cc: 'vpn-help at lists.shrew.net'
Subject: Re: [Vpn-help] pcf cert file - connects after install never again after reboot 64bit Windows7

Tony Hemy wrote:
> Hey,
> 
> I am connecting to a customer site using the 2.1.5-rc5.
> 
> I import the pcf and setup the dns.
> 
> The client connects fine first time after I install, however after a 
> reboot it starts to go wonky. Sometimes it connects, sometimes it does 
> not. During the occasions it connects I can sometimes connect using TS 
> (but it losses connection fast) and sometime not.
> 
> Straight after installing Shrew is awesome and just what I need, it goes 
> sqwurily after a reboot. so I know it can work J
> 

Hi Tony,

When the connection doesn't work, do you happen to see multiple IP 
addresses assigned to the Shrew Soft virtual adapter? One other possible 
cause is a bug I noticed recently on Vista/7. Sometimes the MAC address 
of the adapter isn't read properly by the client when the tunnel is 
built which leads to communication failures. I will be releasing a 2.1.6 
beta build along with the 2.1.5 final release that will include a fix 
for this. I couldn't back port the change to 2.1.5 because it was too 
intrusive. You can give it a try once 2.1.6 has been uploaded to see if 
it corrects your issue.

-Matthew