RE: Workstations unable to use the shared fax



Hello Sam,

Thank you for posting to the SBS Newsgroup.

I understand that your Windows XP Home clients cannot send fax. If I have
misunderstood your concern, please let me know.

Please understand that SBS 2003 Shared Fax requires the client workstations
to join in domain. However, Windows XP Home Edition cannot join in SBS 2K3
domain so your client cannot use the Shared Fax service to send faxes.

We suggest customers that use Windows 2000 or upgrade to Windows XP
Professional so clients can send fax through the SBS 2003 Shared Fax
service.

For your additional information:

How to enable and configure the Fax service in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;306550

Hope this information helps. If anything is unclear, please feel free to
let me know. I am glad to be of assistance!

Best regards,

Brandy Nee

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.



--------------------
>Thread-Topic: Workstations unable to use the shared fax
>thread-index: AcXJM9zsrrqwG9iWSFKKfju3TQoEaA==
>X-WBNR-Posting-Host: 66.17.50.78
>From: =?Utf-8?B?U2Ft?= <Sam@xxxxxxxxxxxxxxxxxxxxxxxxx>
>Subject: Workstations unable to use the shared fax
>Date: Tue, 4 Oct 2005 15:35:03 -0700
>Lines: 15
>Message-ID: <C359CFEE-4CBF-4A89-83E1-DE606FA78742@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:158741
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>I have some XP Home workstations that can not send to the shared fax on
the
>server. They can view/change files on the shared folders. I have given
>'everyone' full access to the shared fax. The workstations are running
>Norton AV 2005. I have tried turning off internet worm protection. I've
>tried adding the ports (1024), adding the fxsclnt.exe to the rules etc.
Here
>is the kicker, some of the workstations can fax, some of them can not. I
>used network monitor on the server, with just one workstation running and
>captured data while sending a fax to the server. Some of the ports that
>appeared were 1044, 1034, 1045 - all added to the rules in NAV. And still
>the other wkst will not fax.
>
>How come some of them can fax? And other cannot? I can not find any
>differences between the two computers, or the two user accounts - one of
them
>works, one does not....terribly confusing. Any help is greatly
appreciated!
>Thanks much, Sam
>

.



Relevant Pages

  • RE: Event log Error - Security
    ... Thank you for posting to the SBS Newsgroup. ... computer who is running Windows 2000 or Windows XP? ... A logon type of 3 translates to Network. ...
    (microsoft.public.windows.server.sbs)
  • RE: Windows 2003 Setup fails on component 25 in add or remove prog
    ... > Welcome to SBS newsgroup. ... > I understand that you encountered some problem when running SBS wizard. ... > installation of SBS 2003 setup. ... > Please note that you also need to apply SBS 2003 SP1 not only the Windows ...
    (microsoft.public.windows.server.sbs)
  • RE: DFS & GPO Problems
    ... Thank you for posting in SBS newsgroup. ... DNS Server address is not configured correctly on the affected ... We can also try to disable the Windows Firewall on the problematic ...
    (microsoft.public.windows.server.sbs)
  • RE: Windows 2003 Setup fails on component 25 in add or remove programs
    ... Welcome to SBS newsgroup. ... I understand that you encountered some problem when running SBS wizard. ... installation of SBS 2003 setup. ... Please note that you also need to apply SBS 2003 SP1 not only the Windows ...
    (microsoft.public.windows.server.sbs)
  • RE: XP Clients getting EventIDs 14, 29 and 5719; cant process group policy
    ... Thank you for posting to the SBS Newsgroup. ... workstations is correctly configured. ... Using Windows Server 2003 in a Managed Environment ...
    (microsoft.public.windows.server.sbs)

Loading