[lix]

As I suspected, there is now one week since the vpn server runs without a hitch. I did not have the time to look into the issue, however any hints would be appreciated.

[lix]

Problem is in my case, I have this issue +with+ iVPN (I bought it too)!

Meanwhile I think I got a trace: it appears that if I am restarting the vpn server using the iVPN GUI, or manually in a terminal (vpnd), I have the issue. However, if I reboot the machine and basically vpnd is run at boot time by the startup script, then the problem does not occur. I had more than one day since the vpn server has been started with no problems at all. Today I reconfigured some parameters using iVPN and the problem re-appeared immediately. I rebooted the machine (a mini, latest generation with a fresh Leopard on it, up to date) and I can log-in without problem. I will check again in a couple of days to report if it still works. It is a kludgy work-around (that is, after each VPN server configuration change I have to reboot the machine!), but I see no other solution for now.

So I suspect that the start-up must be done in a certain order (how various daemons must be started), otherwise vnpd does not work properly. At boot-time maybe the order is right, while by simply restarting vpnd it does not suffice.

However, my theory does not explain your initial problems, and especially that your problems have been solved by using iVPN.

[lix]

Hello,

I don’t have an answer, rather the same problem. In my case the server runs for only a couple of minutes, then I get the same messages as you get. Only a restart helps, but again for a limited period of time. Did you find a resolution for this problem?

Lix

[Author]

Posts