Fax Software

Community Forums


Thank you for your quick response.

“Sending & receiving…when logged off” is checked, and does work – provided that I have not run the controller at all when I do log on.

I make a point of logging in as the same admin user every time (the same user that installed Winfax to begin with). I have not tried it under a different user.

If I boot the machine, when the login screen comes up, I can receive faxes before I log in, which indicates that the Winfax service is working. Likewise, if I log in & log out – without starting the controller while logged in – it receives when I log back out, which again, indicates that the Winfax service is working.

But if I log in, start the controller, and log out, the Winfax service does not work when I log back out. It doesn’t matter if I close the controller manually or let the OS close it. Then, if I immediately log back in, the controller won’t load. I see it in the taskbar (auto receive disabled). If I right click on it, I get nothing, so I start Message Manager and it locks up at the point where it initializes the controller. The system doesn’t hang, just Winfax. Once I kill Winfax, the system still works and I can even use the same modem to connect to the internet, etc. The only way to get Winfax to work again is a reboot.

From what I understand, the controller has control when logged on. The service has control when logged off. Seems to be an issue with how the controller closes & releases the modem, so the service can take over when you log off.

How the modem fits into this changeover, I have no idea. Because of the status lights on my modem, I do know that you can see the service initialize the modem when you first boot up. When you start the controller, the status lights don’t even flicker. They remain in the “ready” mode, which is all good. When you close the controller, the status lights indicate a “not ready to receive” state, which you would expect. Then, when you log off & the service takes control, you would expect the modem to be “ready” again, but it isn’t. It stays in the “not ready” state.

It there a way to audit any of this or create a log? Does Winfax create it’s own log?

Could this be a DCOM issue? A security issue? Anything to check here?

I really appreciate your time on this. Symantec support was no help at all.

Gary Reid