Fax client setup can't see/copy FX files...?

[Guest]

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Hello,

I've setup Windows 2003 fax services on a W2K3 server and shared the
device. I've tested faxing from Word on my PC and it works fine.

However, when other users try to install the fax client, the setup
hangs asking for the fx* setup files. I've tried different XPSP2 CDs,
copying the files to a local directory, making sure that the users have
local admin rights (and even domain admin rights) but to no avail. The
files are already in the system32 directory so in theory the setup
doesn't even need to copy them. Even if I delete them, it doesn't work.
Our corporate SMS team reckons that there isn't any policy which could
cause the problem.

Anyone seen this problem before?

Thanks,

- Alan.

 

[Guest]

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Have a look at this article:

http://members.shaw.ca/bsanders/FAQFAX.htm#_Toc88835132
Why can't the XP Fax Installation Program find the Installation Files?

Hal
--
Hal Hostetler, CPBE -- hhh@kvoa.com
Senior Engineer/MIS -- MS MVP-S/U -- WA7BGX
http://www.kvoa.com -- "When News breaks, we fix it!"
KVOA Television, Tucson, AZ. NBC Channel 4
Still Cadillacin' - www.badnewsbluesband.com

<email.helpline@gmail.com> wrote in message
news:1124536261.487400.287310@g49g2000cwa.googlegroups.com...
> Hello,
>
> I've setup Windows 2003 fax services on a W2K3 server and shared the
> device. I've tested faxing from Word on my PC and it works fine.
>
> However, when other users try to install the fax client, the setup
> hangs asking for the fx* setup files. I've tried different XPSP2 CDs,
> copying the files to a local directory, making sure that the users have
> local admin rights (and even domain admin rights) but to no avail. The
> files are already in the system32 directory so in theory the setup
> doesn't even need to copy them. Even if I delete them, it doesn't work.
> Our corporate SMS team reckons that there isn't any policy which could
> cause the problem.
>
> Anyone seen this problem before?
>
> Thanks,
>
> - Alan.
>