phone line busy error

[Brad Shutes]

I have identified a problem with Wingate 5.1 (and previous versions). Whenever you are using a DSL connection manager program and you just rebooted your machine, you have to wait about 2 to 3 minutes in order to reconnect to the DSL service again because it says "the phone line is busy", which for a DSL connection makes no sense whatsoever. HOWEVER, If I go into the Services console and disable the wingate engine entirely this problem never happens until I re-enable it. I often have to reboot my machine, and having to wait such a long time to get back into my online game is a pain in the....

My only course for now is to keep the wingate engine disabled until I need it.

Is there a solution for this? I have tried everything I can see. Ideally, there should be an option to have the the Wingate Engine load into memory only when a web connection (such as DSL connection) is actually available.

Any advice would be appreciated.
Brad

[adrien]

So you are saying that whenever WinGate is loaded it takes that long to make a DSL connection?

Does it eventually make the connection? If so, there may be some verification happening on the server at the other end that is timing out because of the WinGate firewall... do you see any blocked packet attempts in the firewall tab in GateKeeper? If so, you may need to open some ports.

Adrien

[Brad Shutes]

Thank you for replying.

I'm not using the Wingate Firewall, so I don't think that's a problem. I'm using a different firewall service called Zone Alarm, both at the client and at the server. Zone Alarm does not indicate any blocked packets from either the server, client or from the DSL provider's dynamic IP.

If the computer has been off for a while I can start it up and the DSL connection ALWAYS happens quickly. But, if I have to reboot the machine then the DSL connection requires at least 2 or 3 minutes to complete.

Now, before I installed Wingate I had no problems with rebooting and getting a quick re-connect of the DSL. I can also "Disable" the wingate engine in the Services console and then a re-connect is very fast upon reboot.

I've even gone so far as to use Regedit to make the wingate service "depend on" another service in the hope that it wouldn't activate until later in the boot process. That doesn't work either, apparently because even though you have the service depending on something doesn't mean it isn't already loaded into RAM while it waits on whatever it's supposed to depend on. (If that makes any sense)

*sigh*

Other than this headache, Wingate is fantastic and I'm happy I purchased it.

Brad