Checkpoint secure remote client & wingate

[ngrayson]

Guys,

I have skirted around this issue before believing that the problem belonged to my company and not me but I am now less than convincd.

I have a home network which uses wingate. Ok so far. My company gives us VPN access via Scuremote client when it works.

Wingate is set up to use proxy with transparent redirect (effecivly NAT as I understand).

On my Laptop, the secure remote client connects through wingate and I can check emails etc and then it appears to freeze givening me no access to the company internal resources. If I disconnect secure remote and reconnect it, it believes it has reconnected and is usable only its not. I have no access to the internal resources and when I check the client status its failed its MTU negotiation.

Does anyone run a similar setup or know of any issues between Secure remote/wingate. I should point out that irrespective of the version of secure remote this happens evn the latest NG. Wingate version is currently 6.0.3

[genie]

Does this connection work if Wingate is not running?

[ngrayson]

Hi There,

Well, that a difficult one to qualify since at home, my ISDN card is built into my server. I therefor cant access the internet without wingate.

Having said that we took my laptop and through its internal modem, and my ISP account I was able to work all morning so that way appears to work. Having said that Secremote beehaves slightly differently as when the dial up connection goes, it will see it and terminate its session. This will not happen on my internal LAN as its see a permamnt connection even if the ISDN link has dropped.

As a little more background, it will initiially connect and I am typing this though it. After some apparenlty random time period it stops passing data ( and the ISDN line is up still). I disconnect the secure remote session and then reconnect but it will not pass data again until I reset wingate.

I now have my ISDN timeout set to one hour and the ports which Secure remot uses set to never timeout.

In secure remote under the MTU tunnel properties (status), when its working it shows success and a discovery time and when its not it shows failed and yet secure remote apparently goes through the same state process, i.e. working or not, it shows "user authenticated" and then issues its bridsong warble to say its connected.

Dont know if this helps.

[genie]

I wonder if it might be a DHCP problem of some kind?

[ngrayson]

I'll check but I think we wil always get the same address.

[genie]

Please, check because even if the same IP address is allocated it should still be re-requested - that is if DHCP is involved.