Use API from Windows Service

I would not recommend doing it. WinInet in API internals is not safe enough to be used in system services.

I've implemented it as a Windows Service using SRVANY and it's been working fine for several months.

 

 

Well, the F5 salesman and the engineer he had on the phone when we described in detail what we need to do didn't seem to think there should be any problem with it. Based on that, we are about to buy our third FirePass box.

 

 

This worked running as a service under the LocalSystem account with version 6.0.1, but does not appear to work anymore with 6.0.2. It still works if run under a user account, but under LocalSystem it fails with the message "The system could not find the phone book entry for this connection."

 

 

I think it's using the dialup "Network Connection" defined in the registry under CURRENT_USER, so that's why it's not finding it.

 

 

Has anybody else run into this or have an idea of how work around it?

 

We back-leveled our FirePass box to 6.0.1 and confirmed that this works in 6.0.1, but does not work in 6.0.2. Any word on a new version to fix this?

A new day...nothing different but maybe a reboot --and today connecting with 6.0.1 fails with the same error as 6.0.2. I guess it wasn't the version up after all.