Re: sbs 2003 fax services

Hi Loane,

Thanks for your update.

I am sorry for the delayed response due to weekend and New Year holiday.
Please understand that the newsgroups are staffed weekdays by Microsoft
Support professionals to answer your systems and applications questions.
Your understanding is greatly appreciated!

>From your description, I think the problem should be lies in that the
shared fax client application failed to install.

I. You can try to manually install the shared fax client application on the
client computer to see if the issue be fixed. You can refer to the
following steps:

1. Logon on one client workstation with domain admin account, then copy the
SBSDefault.prf file under the folder: \\%sbsserver%\clients\Setup on the
server box to the following folders on the client computers:
-- C:\Program Files\Microsoft Windows Small Business Server\Clients'' and
-- %FaxTransport%
2. And then logoff the user account and then relogon with one domain user
account, Can the shared fax client installation be launched? Do it be
installed successfully? If the shared fax client is installed properly, you
should find the shared fax console in Start -> Printers and Faxes.

The SBS shared fax is different with Windows fax service, it is based on
Windows Fax service. If you had not connected a modem on the workstation,
there is no fax instance in Accessories > Communication > Fax. It is normal
on your workstation.

II. If the issue persists, I suggest you use outlook 2003 on the client
computer to send fax as test to see if the issue still exists or not, you
can follow the steps below:

We can use outlook on client side to send fax, in this way you can add the
all kinds of address as you like. You can refer to the following section
for detailed steps:

A. Open Outlook.

B. Type ''[FAX:xxxxxx]'' (without the quotation marks) in To bar. Input a
subject of the new fax and then edit the content. (xxxx is the destination
fax number)

C. Click ''Send'' button to send the fax.

NOTE: To use this method, please make sure ''Fax Mail Transport'' account
is in the E-mail accounts list. Click ''Tools''-->''E-mail Accounts''.
Select ''View or change existing e-mail accounts'' and click ''Next''.
''Fax Mail Transport'' should be listed in the account list.

III. If the shared fax client still can not be installed on workstation, I
suggest you try to re-join one workstation to domain to see if the issue be
fixed. You can refer to the following steps:

1. Quit one workstation from the domain. To do so, see:

Locate in Client Computers in Server Management console and choose the
computer the customer has in right panel. Click Remove from network link to
delete the computer from domain.

2. Setup the client computer by running Setup Client Computer wizard to
setup computer account.

3. In the client computer, try to join it to domain by running
http://servername/connectcomputer. And assign appropriate user accounts to
the computer.

Note: Please ensure you have added the SBS Site (http://FQDN/*) in trusted
site in IE of the laptop. You can refer to the following steps:

a. Start Internet Explorer.
b. On the Tools menu, click Internet Options.
c. On the Security tab, click Local intranet zone, and then click Sites.
d. Click Advanced.
e. In the Add this Web site to the zone box, type the ConnectComputer
server's IP address or the ConnectComputer server's FQDN, and then click
Add.

4. Assign client applications to the client computers by Deploy Client
Application wizard.

1). Go to Server Management console -> Client Computers -> Assign
Applications to Client computers.
2). Click it to start Assign Application wizard, follow guide to assign fax
client to the client computer.
3). When users logon to domain from the client computers next time, to see
if the fax client will be launched to install.

Try to test, let me know the result.

Additionally please ensure your modem lists in Microsoft production catalog
list to ensure it is compatible with Windows 2003. Please check it in the
home page: www.micrsofot.com/hcl

And please go to the modem vendor homepage to get the latest driver for
Windows 2003. And then re-test the issue.

If the issue persists, please help me collect some screen shots when
reproduced the issue on client computer.

Hope above information helps. I am happy to be assistance to you!

Have a nice day!

Sincerely,

Jenny Wu
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.

The partner mail content:
===================
Hi Jenny
Please see my additional post on microsoft.public.windows.server.sbs
(repeated below):
Best regards
Loane

Hi there

I setup the shared fax service for the first time on a machine that has SBS
2003 SP1 applied. (On MSDN I see that there are potential issues that arise
when the shared fax service is installed AFTER SP1 is applied, so this may
make a difference.) I have experienced some problems on both the server and
clients.

Network setup: Our server has one network card connected to a wireless
access point/internet router device, which in turn is connected over a DSL
line to the Internet. The internal fax modem is directly connected to the
same DSL line, and the voice and data streams on the DSL line are separated
using a line filter following the hardware manufacturers' instructions.
Clients are connected to the server using a wireless LAN.

Server problem: After the intial setup (closely following the instructions
in SBSFax.doc located at
http://www.microsoft.com/downloads/details.aspx?FamilyID=1b7510a0-1595-4776-
a101-c3bec7512594&displaylang=en),
the server itself could send faxes (from, say,
wordpad using the fax printer) and also receive faxes. To stress-test the
server-side fax capability, I sent 10 faxes to the server in succession from
a remote/independent fax location, waiting each time for about a minute
between sends (this should be about the maximum for our business purposes).
On the third send I got a communication error back from the server, and
somehow the telephone line was jammed up: the server's telephone number gave
a "busy" signal when dialed, and the server could no longer be accessed over
the internet (using Remote Desktop and RPC/HTTP for Outlook, for instance).
The server needed to be cold-booted, and trying the stress-test again the
same jammed-up result obtained.

Client problem: After setting up shared fax service on the server, logging
on to the client computers for the first time correctly prompted for setup
of the fax service. The SBS fax service setup began, and at the appropriate
time the Windows XP fax component setup began, and when asked I pointed to
the appropriate location on the server for the client setup .dlls. At the
very end I got a message that said "Applications not configured: Shared fax
service"; in Windows components the Fax service was unchecked, and the
Accessories > Communication > Fax menu was <Empty>. In the Application event
log, I found a message for Microsoft Fax with Event ID 32045 that read: "Fax
Service failed to initialize because it could not initialize the TAPI
devices. Verify that the fax modem was installed and configured correctly.
Win32 error code: 31." Following the suggested link, I got the following
message: "We're sorry. There is no additional information about this issue
.." (Incidentally the client machines do not have fax-capable modems.)

I'm assuming that the problem could arise from several sources:
(a) the fax modem and drivers may not be correctly installed on the server -
but if so, how could I send and receive faxes from the server itself?

(b) the shared fax service may not be correctly setup on the server - but if
so, how could the client computers be prompted to setup shared fax service
when logging on if the server-side setup was incorrect? (Incidentally, I
uninstalled the fax service from Windows Server 2003 components and then
installed the fax service from SBS 2003 setup)

(c) the DSL line may be problematic - but if so, how could clients connect
to the Internet (from within the local network) and to the server via VPN
and RDP (from outside the local network)?

Perhaps I've missed some other potential sources of the problem?

Please help!

Best regards
Loane
===================

--------------------
>From: "Loane Sharp" <look_sharp_not@xxxxxxxxxxx>
>References: <#5hK$3MDGHA.628@xxxxxxxxxxxxxxxxxxxx>
<h8Ph5uODGHA.4092@xxxxxxxxxxxxxxxxxxxxx>
>Subject: Re: sbs 2003 fax services
>Date: Fri, 30 Dec 2005 13:28:50 +0200
>Lines: 1497
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
>X-RFC2646: Format=Flowed; Original
>Message-ID: <u1PI3QTDGHA.3208@xxxxxxxxxxxxxxxxxxxx>
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: dsl-165-247-67.telkomadsl.co.za 165.165.247.67
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:233151
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>Hi Jenny
>
>Thank you for your reply.
>
>> 1. What is the exact error message the user received when the RDP session
>> is disconnected? Please help me collect a screen shot when you reproduce
>> the issue.
>The user does not receive an error message, they are simply disconnected.
>When the user logs on again, the previous RDP session is reflected as
>"Disconnected" in Task Manager > Networking.
>
>> 2. Can domain users send/receive faxes successfully on client computers
>> with shared fax client (Start -> Printers and faxes)?
>
>The server can receive and send faxes correctly, but users cannot add the
>shared fax printer to their client machines.
>
>>
>> 3. Could you find any related error event logged in Event Viewer (System/
>> Application) on the server box and the computer that the user RDP from?
If
>> yes, please paste the detailed error information in the newsgroup. You
can
>> run command "eventvwr.msc" (no quotation marks) to launch the Event
>> Viewer.
>> Or you can save a copy of system and application logs on the server box
>> and
>> the client computer for me and I will analyze it.
>>
>
>This is the error message in the application log of a client machine. The
>client is using a Thinkpad T41 with an Agere Systems AC'97 modem.
>
>
>
>Thank you very much.
>
>Best regards
>Loane
>
>
>

.

Loading