home




Connect 32-bit Windows XP Fax Clients to 64-bit Windows Server 2008 R2 Shares

So, you install Server 2008 (or Server 2008 R2) no problem, get your fax modem installed no problem, set up fax services and share the fax so your domain clients can send a fax?

Are you getting "Error in connection" (in the Fax Manager list), "All Fax Printers are inaccessible", "Fax Server unavailable" messages or the Send a Fax wizard disappears when clicking next? Does this also happen when you connect your XP clients to the fax share? The Printer connection may be mapped successfully but opening the fax console reveals there is no connection to the fax server.

It turns out Server 2008 and Server 2008 R2 need slight modification to make their fax shares work with pre-Vista clients (e.g. Windows XP and Windows 2000), so this guide will tell you how to do such!

Pre-requisites

  • Fax Services Role is installed and configured on your Windows Server 2008 / Server 2008 R2;
  • Windows XP Clients have the Fax Services installed via Windows Component Add/Remove section;
  • Windows XP Clients are Service Pack 2 or above;
  • You have a domain security group with all of the members you want to give the ability to fax from your fax server. E.g. "Fax Users";
  • If the Server (or client) is x64 (64-bit) that the Fax Server is providing x86 and x64 "User Mode 3" client drivers in the "Additional Drivers" list of the share. If you are not providing x86 User Mode 3 drivers, click here to read the guide on how to inject native x86 Windows Server 2008 Drivers into an x64 Server share to allow the Microsoft Shared Fax drivers to operate with x86 32bit Windows XP Clients.

OK, so let's assume you've got Fax Services installed on your Windows Server 2008 or Server 2008 R2. The first thing you need to do when you've added the role is checked the Windows Firewall exceptions under the "Windows Firewall with Advanced Security".

Windows Server roles should have automatically opened up:

  • FAX Service (RPC-in)
  • FAX Service end-point mapper
  • File & Printer Sharing

Yes, Windows File & Printer Sharing is a required exception since RPC calls are routed over it for the clients, and Windows Shared Fax drivers are passed over these ports.

Next step is to obviously make sure your Fax Printer is shared (my share is called "Fax") under the sharing tab and the security tab gives permission to your security group "Fax Users" (or whatever you called the group, you could just add "Domain Members"). Make sure you don't specify a local security group but a domain security group e.g. "DOMAIN\Fax Users".
You need your desired Fax Users to have at least the "print" ability as below:


OK, lastly and most important that no-body including Microsoft seems to have documented:

Change the Fax Service "LOGON AS" from NETWORK SERVICE (the Windows Default!) to "LOCAL SYSTEM".
Do this by going to "Server Management" -> "Configuration" -> "Services" and modify the properties of "Fax" under the Services list.
It is also worth ticking the box "Interact with Desktop" under the Local System. (See picture below).

Now connect your XP Client to your Server 2008 Fax share, by adding it like any other Network Printer.

Note that if you are installing this on a 32-bit XP Client from a 64-bit server, it will install the Microsoft Shared Fax driver that you should have injected into the 64-bit Server "Additional Drivers" tab.

Now connect your client and... voila you should now see all the faxes under "Inbox" and "Sent Items" when opening the fax printer on your XP client (which opens up the "Fax Console" which has a status of "Ready"!

Related Guides:

Like what you've read? Was this of help? Contact Guru Guy to let him have your feedback!

Now why not visit Guru Guy's Vintage Computer Webshop to grab classic Vintage Computer Server Software!
 
  Copyright © Guru Guy 2009. All Rights Reserved. SITEMAP | DISCLAIMER