I was at a clients place a few days ago. They are running a NT 4.0 server. The external modem was bad. I replaced the external modem. I was able to move around in the Gatekeeper program; however, Wingate would not connect to the existing dial up account. Removed that acount and reset it up. The problem is that Gatekeeper now pegs the cpu usage. I am able to make a connection to the ISP using Dial UP Networking. If I let Wingate make the connection, it connects and disconnects as though it could not able to authenicate the connection.
The customer is running an older version of Wingate, I believe it was about ver 4.5. I was thinking of updating to ver 6. However, I am not sure how this will affect the license(s) of the product. It was installed several years ago and there is no information. Will upgrading reguire any inputting of a License Key, or will it pull the information it needs when the upgrade is done?
Would deleting the History.dbf and History.cdx help in correcting Gatekeeper from pegging the cpu usage?
Finally, is there any reason why the modem disconnects when Wingate makes the connection instead of doing locally on the PC? Or should I cross that bridge after getting the Gatekeeper issue resolved?
Regards,
Mike