Tunnel (xx) to Local network of XX - In stasis

[chuckh]

why am i constantly getting the "in stasis" status on my VPN tunnel from my VPN host?

zanop01 is the master
dpoffice is the local.

when looking at the local network of the master, the tunnel shows "in stasis" after i try to map any drives, move any data etc.

the tunnel under the local network of the local machine says "active".

connection options are set to allow tunnels to/from all nodes and the local participation is set for the local network.

ideas? thanks!

-chuck. [/img]

[wolf5]

Try searching in the old forums: http://webboard.deerfield.com/guests.

This is a possible solution I found there:

My situation:
One VPN host server. (NT4)
One labtop which had to connect to this server. (Win XP, remote client)

The problem:
When I joined a VPN connection to the server the 2 tunnels on the labtops where active. On the server there was only 1 tunnel active (the tunnel to the server), the tunnel from the labtop was "in stasis" on the server.

What helped for me:
Fix 1:
After some researched I discovered that when I uninstalled the "QoS packet scheduler" my problem was gone.
All the tunnels where active and I was able to connect to every server behind the VPN Gateway server.

Fix 2:
Go to the properties of your VPN connection on your server.
Set Local Participation to Local Network.
Then customize your routes, you should only publish your internet IP and internal network range.
Example:
Destination Mask gateway Type Status
Internet IP 255.255.255.255 127.0.0.1 LocalMachine Published
130.13.0.0 255.255.0.0 130.13.12.1 LocalNetwork Published

Someones lucky enough to get it working. Me, I can't even get the ping part to work, even by manually adding routes to the remote network.

-Wolf5