For some reason our VPN Client to site has stopped working.

Two days ago I installed bm37fp3b.exe and rebooted. I was able to
make
a VPN connection from home that night. I had installed the patch
because we were getting ABENDs about one per week for PROXY.NLM or anunderlying process.

Today, I added a new static route to the routing table and then
rebooted
the server. I believe VPN was working to this point. I did notice
that
time was NOT SYNCRONIZED (after the reboot) when I found out the VPN
did
not work. I unloaded and reloaded TIMESYNC and that cleared the timeerror. I also unloaded NLSLSP, which reloaded automatically.

Still, the VPN did not work. So I tried a couple times to BMOFF and
REINITIALIZE SYSTEM. I had to REINITALIZE SYSTEM because the VPN
Tunnel
was unloaded with BMOFF, but did not reloaded when I loaded CPFILTER,BRDSRV, and VPMASTER.

Since I was trying to fix the problem remotely, I then did a BMOFF
followed by RESTART SERVER. Still, the VPN did not work.

Other than that, nothing has changed. No change in NAT, filters,
etc.,
nor changes at the client side.

I do not notice any errors while booting the server, but I have
noticed
the following:

1. In NWADMIN, "Novell+BorderManager Client VPN+370" has 0 units in
use. It seems to me that this should be 1 in use.

2. In the VPN logs, I see the error "Failed registration for VPN Site

to Site license". Looking back through the logs, I saw this error
after
each reboot for the last two days. None prior to 8/5/03 though.

3. When I attempt to connect from a client, the only entry in the VPN

logs is "Connection closed for the VPN client at address 68.xx.xx.xx".

This only shows once for each time I attempt to connect.

4. Earlier in the day, and in the middle of the night, I also saw
this
error in the VPN log: IP (Red Stop Sign) "(SKIP) Construction of SA
failed for peer 12.127.16.68". This occurred several times at
different
times of the day.

Does any one have an idea as to what would cause this, or how I should

troubleshoot it ?