In stasis!!! Sound like a Heart attack!!

[ajdionne]

Hello!

Need some guidance... Continuation on problem, problems and problems

Recap: Can browse and remote access all worksation behind Wingate server but Wingate server id mark as unaccessible.

O.K. got someone to sit behind server and me being far far away this is what we found

Client

On client both tunnel are active and working

On Wingate Server

Tunnel from Client to server is fine
Tunnel from Server to client in Stasis

I don't understand the other topic reply on same problem.

Could explain please.

[Pascal]

Recap: Can browse and remote access all worksation behind Wingate server but Wingate server id mark as unaccessible.
Tunnel from Client to server is fine
Tunnel from Server to client in Stasis

You are using WinGate 5.2.2 on the Server, and VPN Standalone 1.2 on the Client, correct ?

We did have a GUI bug in a previous version (Around 5.0.2 or 5.0.4) that meant you had to go offline in GK and go online in GK again before the tunnels would show up properly. This was fixed though.

A tunnel should only show up as "In Stasis" if the server never received a request from the Client to join the VPN. Otherwise, it should show up as "Pending" (Normally so fast you don't see it), "Active" or "Error".

Can you enable logging for the VPN on the Server and the Client, connect, and then send us the parts of the logfile relating to that connection, please ?