Wingate connecting problems...getting error 676 line busy.

[saisri]

I installed Wingate 5.0.7 yesterday. Everything went smoothly during installation. But after the system restarted, I couldn't connect to my DSL line. It always gives me Error 676: line busy.
I did install ENS during installation but didnt install VPN.

Now after I uninstalled Wingate completely, I was able to connect to my DSL connection without any glitches.

Then I restarted and installed Wingate again, but this time I didnt install ENS. Now I could connect to my DSL line. But I dont have NAT now.

What should I do to get around this problem?

I have a network here comprising of One server and 6 clients. The server is connected to internet through an ADSL modem and is running Win2k pro.

Any help is greatly appreciated.
Thanks in advance.

[saisri]

I just installed Wingate 5.1 and the above problem is solved. I can now connect to my DSL line.

But I have another problem now. Whenever I try to stop the engine, it doesnt stop. It says Wingate engine stopping but it doesnt stop. I cant even start it again. I have to restart the system.
In the Gatekeeper, when I try to go online, it says that the wingate server you are trying to connect is busy shutting down. Please wait until it has completed and try again.

Is this an issue or a bug or something like that?

[saisri]

Today after I started my server, the gatekeeper didnt start. The wingate engine showed that the service is starting but it didnt start and i couldnt get the gatekeeper to start. I waited for a long time for the service to start but it didnt. In the task manager, the CPU usage was at 100%. and the whole system was very slow.
What is happening over here???
Isnt 5.1.0 a stable version?