ActiveFax not sending every job

December 1, 2007

Q:
I am currently testing ActiveFax on a clients network. We have about 20 users who are using thin clients in to a Terminal Server.  We seem to be having problems with the fax client as it is not sending every job to the fax printer. Are there any known problems with Terminal Services?

A:
When running ActiveFax with terminal services, you need to take care that the option for terminal server extensions is enabled on the fax client with the menu File / Automatic Startup / Terminal Server.
It is also important to once log off from Windows after the fax client has been installed and you should also avoid to login with the same user name on more than one terminal session, since the user name is used by the printer spooler to identify the terminal that created the print job and if there are multiple terminal sessions with the same user name the terminal that created the print job cannot be clearly identified.


Cornelia Wegmueller, ACTIVEFAX Customer Support
INTERTRADE ENTERPRISES LTD :: Blegistr.25 :: CH-6340 Baar/Switzerland
Phone: +41 44 5866974
Fax: +41 44 2742350
mailto:support@activefax-distribution.com
http://www.activefax-distribution.com

Advertisements

Access to the fax server through a terminal server session

December 1, 2007

When ActiveFax is running as a Windows service, access to the fax server window through a terminal server session is not possible. The reason for that conflict is, because the ActiveFax service always has to be running on the desktop of the console session. When connecting through terminal services, Windows creates a new self-contained desktop for the terminal server session, so the fax server window cannot be accessed from that desktop.

You can solve this with one of the following solutions:

If the terminal server is running Windows 2003 it would also be possible to connect to the console desktop with a normal terminal server connection when you start the terminal session with the parameter /console (i.e. mstsc.exe /console).
Access the fax server directly on the console screen rather than using a terminal server session to access the fax server.
Use a different remote access software (i.e. PCAnywhere or PCDuo) instead of a terminal server session to access the fax server.
Stop the fax server service and start the fax server in application mode by double-clicking at the fax server icon on the desktop. That way you can access the fax server also through a terminal server session. It is recommended to start the fax server as a service again before you leave your terminal server session in that case.


Cornelia Wegmueller, ACTIVEFAX Customer Support
INTERTRADE ENTERPRISES LTD :: Blegistr.25 :: CH-6340 Baar/Switzerland
Phone: +41 44 5866974
Fax: +41 44 2742350
mailto:support@activefax-distribution.com
http://www.activefax-distribution.com


ActiveFax device is not visible in terminal client

December 1, 2007

Q:
I had to reinstall my computer, where ActiveFax client worked correctly from terminal session as well as from local installed applications. After the reinstallation I added some printers shared in our local lan and of course I installed ActiveFax client. Now although I can fax from local installed application I cannot fax from terminal session. But I can print from the same terminal session on the printers shared on our local lan.

Other our computers can fax and print from terminal as well as from local installed application.

A:
In that case it is important that the option for terminal server extensions is enabled on the fax client with the menu File / Automatic Startup / Terminal Server (take care to once log off from Windows when you change that option). In general, I would also recommend to always install the ActiveFax printer on the terminal server through the ActiveFax setup instead of sharing the ActiveFax printer from a different PC.

Additional comment from the customer:
I have just resolved the problem. Registry hack was needed:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Terminal Server Client\Default]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Terminal Server Client\Default\AddIns]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Terminal Server Client\Default\AddIns\RDPDR]
“FilterQueueType”=dword:ffffffff


Cornelia Wegmueller, ACTIVEFAX Customer Support
INTERTRADE ENTERPRISES LTD :: Blegistr.25 :: CH-6340 Baar/Switzerland
Phone: +41 44 5866974
Fax: +41 44 2742350
mailto:support@activefax-distribution.com
http://www.activefax-distribution.com


Problem with the phone book

December 1, 2007

Q:
We have a remote desktop server in our building that our people log into from home. When trying to utilize the ActiveFax print driver, the phone book entry does not launch for them, instead, it launches on the console. What can we do to get around this? They will not use anything other than remote desktop, so using another software such as PCAnywhere is not an option.

A:
You need to take care to enable the option for terminal server extensions on the fax client with the menu File / Automatic Startup / Terminal Server when
connecting through a remote desktop. Take care to once log off from Windows after you changed that option. If this option is not enabled, the fax dialog
window is always displayed on the console screen, since the printer spooler is running on the console desktop.


Cornelia Wegmueller, ACTIVEFAX Customer Support
INTERTRADE ENTERPRISES LTD :: Blegistr.25 :: CH-6340 Baar/Switzerland
Phone: +41 44 5866974
Fax: +41 44 2742350
mailto:support@activefax-distribution.com
http://www.activefax-distribution.com