Received fax errors after running SFC.exe

[Nick]

We no longer seem to be able to receive faxes, the fax log reports 'Uknown
fatal error'. It may be just coincidental but this seems to have happened
after I ran System File Checker.

I recall that when SFC ran it found bad signatures in a number of MSFax
Client files and replaced them with the original versions. SFC was pointed
towards the SP1 location so should have found the most recent copy of the
files.

Any suggestions?

Nick

[Inn Jin [MSFT]]

Hi Nick,

Thank you for posting.

From the description, I understand this issue is that you cannot receive
fax and you get "unknown fatal error". If I am off base, please don't
hesitate to let me know.

Base on my knowledge, I don't think running sfc will cause this issue.
Let's try the following steps to trouble shoot the issue.

Step One
================
Please verify the following steps:

1. Verify that the latest firmware updates from the manufacturer (if
available) have been applied to the modem, and that the modem is installed
with the latest .inf file from the manufacturer. The updated firmware or
.inf file may have improved error handling for the modem.

Please to this Web Site to check HCL list:
http://www.microsoft.com/whdc/hcl/default.mspx

2. Verify that the telephone line connected to the modem is a direct
connection from the telephone company and is not running through a PBX or
other telephone switchboard.

3. If there are other devices on the same line, remove them.

4. Try connecting another telephone line to the modem to help identify
whether the telephone line is contributing to the problem.

5. Please check following settings to make sure all the configurations are
correct:

1). Launch Server Management Console and click Fax in the left panel.
2). Click Configure Fax Services.
3). Click Next,
4). Type Company fax number in the blank.
5). Press Next.
6). Select devices.
7). Follow the wizard to finish the configuration.

Step Two
=================
Please restart Fax Service to check the issue again.

1. Click Start, click Command Prompt.
2. Type "net stop fax" without the quotation marks followed by pressing
Enter.
3. Type "net start fax" without the quotation marks followed by pressing
Enter.

Step Three
==================
If none of these suggestions helps, it may be necessary to involve the
local telephone company to correct telephone line issues and certify the
telephone line. Generally, a standard telephone line is referred to by the
telephone company as "POTS" ("Plain Old Telephone Service") and is
guaranteed to handle voice communications but not necessarily digital data
tones. Your telephone company may be able to make wiring configurations to
help with line issues.

Step Four
===================
Let's try to remove the fax component and reinstall it.

Let's first make sure we have the FAX component installed correctly by
performing a manual reinstallation for it:

1. Rename the keys and files below to *.old

1) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fax
2) HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Fax
3) C:\Program Files\Microsoft Windows Small Business Server\fax
4) The ''SBSMIS-FAX.log'' file under ''C:\Program Files\Microsoft
Integration\Windows Small Business Server 2003\Logs''.
5) The ''SBSMSI-faxcfg.log'' file under ''C:\Program Files\Microsoft
Integration\Windows Small Business Server 2003\Logs''.
6) The ''faxsetup.log'' file under ''C:\WINDOWS\''.

2. Access Add/Remove Programs, Add/Remove Windows Components, uncheck ''Fax
Services'' to uninstall it.

3. Once it is uninstalled, access Add/Remove Programs to reinstall it.

4. Then, access ''Add/Remove Programs again'', this time, we will click
''Change/Remove'' on the ''Windows Small Business Server 2003'' item:

1) Click ''Next'' on the ''Microsoft Windows Small Business Server Setup''
page.
2) Click ''Next'' on the ''Windows Configuration'' page.

Note: It states that ''This will take approximately 30 minutes'', it is
referring to the total time it will take in the first SBS component
installation. For the task such as remove a specific component, it will
just take couple of minutes.

3) Now, in the ''Component Selection'' page, choose ''Remove'' before the
''Fax Services'' item.
4) Click ''Next'', and then click ''Next'' again to confirm ''Component
Summary''. You will be prompted to insert the SBS 2K3 setup Disc 1.

5. Once the removal process is completed, access ''Windows Small Business
Server setup'' again in ''Add/Remove Programs'', proceed to the ''Component
Selection'' page, and then choose ''Install'' for the ''Fax Services'' item.

Please then check if the problem is resolved

Step 5
================
If the issue persists, please kindly to gather the following information:

1. Did this issue happen on server side or client side or both?

2. If on client side, did the issue happen on some specific clients or all?

3. What is the exact brand and model of the fax modem?

4. Download and run the setup MPS report tool on the SBS 2003 server.

a. Click Start, click Server Management Console.
b. Right click Fax, and click Properties.
c. Select Event Reports tab, and set all the four options to High.
d. Reproduce the issue
e. Visit
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
15706/MPSRPT_SETUPPerf.exe to download the file.
f. Run the MPSRPT_SETUPPerf.exe on the server box.
g. Wait for 10~15 minutes.
h. Open Windows explorer, navigate to
%SYSTEMROOT%\MPSReports\Setup\Reports\cab
i. Send the .cab file directly to my working mailbox v-in...@microsoft.com

5. Activity Log

Please send all the log files located in the %alluserprofile%\Application
Data\Microsoft\Windows NT\MSFax\ActivityLog folder, and the location can be
modified. You can enable activity logging in Server Management: right-click
Fax (Local) and select Properties, click the Activity Logging tab, and
select the appropriate check boxes.

6. Please compress all the files and send to me at v-in...@microsoft.com.

I appreciate your time. I am happy to be of assistance to you and look
forward to your reply.

Have a nice day!

Best regards,

Inn Jin (MSFT)

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.

[Nick]

Hi Inn Jin,

Step one - This fax server worked fine with these modems for a couple of
years until the day I ran SFC.exe, so not a modem firmware issue. There are
two USRobotics Couriers one for incoming faxes one for outgoing.

Step two - A manual fax machine connected to the same line for testing works
fine so not a line error.

Step three - fax service has been restarted numerous times.

Step four - will try this tomorrow and let you know the result. Is the fax
component updated in service pack 1, does this need to be reinstalled after
reinstalling the fax?

Thanks,
Nick

""Inn Jin [MSFT]"" <v-in...@online.microsoft.com> wrote in message
news:FQBaOB7M...@TK2MSFTNGHUB02.phx.gbl...

> Hi Nick,
>
> Thank you for posting.
>
> From the description, I understand this issue is that you cannot receive
> fax and you get "unknown fatal error". If I am off base, please don't
> hesitate to let me know.
>
> Base on my knowledge, I don't think running sfc will cause this issue.
> Let's try the following steps to trouble shoot the issue.
>
> Step One
> ================
> Please verify the following steps:
>
> 1. Verify that the latest firmware updates from the manufacturer (if
> available) have been applied to the modem, and that the modem is installed
> with the latest .inf file from the manufacturer. The updated firmware or

[Inn Jin [MSFT]]

Hi Nick,

Thank you for upgrading,

I appreciate your effort on this issue, please take your time to follow our
suggestion, I want to inform that you don't have to re-apply SP1, there is
no update of fax component in SP1, please feel free to perform uninstall
and install. After that please install the latest driver of your fax modem,
if issue persists, please gather the information I referred in my previous
post. If you have further concerns on this issue, please feel free to let
me know!

[Nick]

Hi Inn Jin,

> Step Four
> ===================
> Let's try to remove the fax component and reinstall it.

Done that, followed your instructions completely. Still got the same
problem.

> Step 5
> ================
> If the issue persists, please kindly to gather the following information:
>
> 1. Did this issue happen on server side or client side or both?
>
> 2. If on client side, did the issue happen on some specific clients or
> all?

No clients involved, everything is being done on the server.
The issue is happening on the receiving fax server. It will not receive any
faxes regardless of whether they are sent from a modem or a standalone fax
machine.

>
> 3. What is the exact brand and model of the fax modem?
>

Two USR Couriers, one for incoming, one for outgoing. Back in the days of
NT4 SBS these were about the only modems that were recommended for SBS. The
pair that are on this server have been working fine for about two years. It
would be an extremely rare coincidence if this modem just happened to fail
on the same day day as I ran SFC.exe!

> 4. Download and run the setup MPS report tool on the SBS 2003 server.
>

Lost remote connection to the server at the moment just waiting for the
users to finish for the day before they can reboot the server. As soon as I
can get access to it again I will run this and email you the results.

>
> 5. Activity Log
>

Log files below:

InboxLog.tst:
"Status" "ErrorDesc" "ErrorCode" "StartTime" "EndTime" "Device"
"QueueFileName" "FileSize" "CSID" "TSID" "CallerID" "RoutingInfo" "Pages"
"Reception error" "The remote fax machine did not respond in time, and the
call was terminated" "0x40000802" 1/11/2007 15:40:49 1/11/2007 15:41:20
"Courier V.Everything V.90 X2 European PnP" "C:\Documents and Settings\All
Users\Application Data\Microsoft\Windows NT\MSFax\Queue\1C73596DE3BDC.tif" 0
"CompanyName" "CompanyName" "" " " 0
"Reception error" "The remote fax machine did not respond in time, and the
call was terminated" "0x40000802" 1/11/2007 15:51:22 1/11/2007 15:51:53
"Courier V.Everything V.90 X2 European PnP" "C:\Documents and Settings\All
Users\Application Data\Microsoft\Windows NT\MSFax\Queue\1C73598575AAD.tif" 0
"CompanyName" "CompanyName" "" " " 0
"Reception error" "The remote fax machine did not respond in time, and the
call was terminated" "0x40000802" 1/11/2007 16:01:54 1/11/2007 16:02:26
"Courier V.Everything V.90 X2 European PnP" "C:\Documents and Settings\All
Users\Application Data\Microsoft\Windows NT\MSFax\Queue\1C73599D07D9C.tif" 0
"CompanyName" "CompanyName" "" " " 0
"Reception error" "The remote fax machine did not respond in time, and the
call was terminated" "0x40000802" 1/11/2007 16:12:27 1/11/2007 16:12:59
"Courier V.Everything V.90 X2 European PnP" "C:\Documents and Settings\All
Users\Application Data\Microsoft\Windows NT\MSFax\Queue\1C7359B49AAC5.tif" 0
"CompanyName" "CompanyName" "" " " 0
"Reception error" "The remote fax machine did not respond in time, and the
call was terminated" "0x40000802" 1/11/2007 20:30:29 1/11/2007 20:31:08
"Courier V.Everything V.90 X2 European PnP" "C:\Documents and Settings\All
Users\Application Data\Microsoft\Windows NT\MSFax\Queue\1C735BF55CBE5.tif" 0
"CompanyName" "CompanyName" "" " " 0
"Reception error" "The remote fax machine did not respond in time, and the
call was terminated" "0x40000802" 1/11/2007 20:41:09 1/11/2007 20:41:41
"Courier V.Everything V.90 X2 European PnP" "C:\Documents and Settings\All
Users\Application Data\Microsoft\Windows NT\MSFax\Queue\1C735C0D33558.tif" 0
"CompanyName" "CompanyName" "" " " 0
"Reception error" "The remote fax machine did not respond in time, and the
call was terminated" "0x40000802" 1/11/2007 20:59:58 1/11/2007 21:00:29
"Courier V.Everything V.90 X2 European PnP" "C:\Documents and Settings\All
Users\Application Data\Microsoft\Windows NT\MSFax\Queue\1C735C374079F.tif" 0
"CompanyName" "CompanyName" "" " " 0
"Reception error" "The remote fax machine did not respond in time, and the
call was terminated" "0x40000802" 1/11/2007 21:10:32 1/11/2007 21:11:03
"Courier V.Everything V.90 X2 European PnP" "C:\Documents and Settings\All
Users\Application Data\Microsoft\Windows NT\MSFax\Queue\1C735C4EDC178.tif" 0
"CompanyName" "CompanyName" "" " " 0

OutboxLog.txt
"JobID" "ParentJobID" "SubmissionTime" "Scheduled" "Status" "ErrorDesc"
"ErrorCode" "StartTime" "EndTime" "Device" "DialedNumber" "CSID" "TSID"
"Pages" "TotalPages" "QueueFileName" "Document" "FileSize" "Retries"
"ServerCoverPage" "CoverPageSubject" "CoverPageNote" "UserName" "SenderName"
"SenderFaxNumber" "SenderCompany" "SenderStreet" "SenderCity"
"SenderZipCode" "SenderCountry/Region" "SenderTitle" "SenderDepartment"
"SenderOffice" "SenderHomePhone" "SenderOfficePhone" "SenderEMail"
"RecipientName" "RecipientFaxNumber" "RecipientCompany" "RecipientStreet"
"RecipientCity" "RecipientZipCode" "RecipientCountry/Region"
"RecipientTitle" "RecipientDepartment" "RecipientOffice"
"RecipientHomePhone" "RecipientOfficePhone" "RecipientEMail" "BillingCode"
"0x0201c73596b0ac80" "0x2001c73596b0aa0f" 1/11/2007 15:39:32 1/11/2007
15:39:32 "Transmission error" "Unknown fatal error" "0x0000000c" 1/11/2007
16:11:14 1/11/2007 16:11:48 "Courier V.Everything EXT PnP (V90-x2)" "91280
111111" "+441708222222" "St Kitts & Nevis Int" 1 2 "C:\Documents and
Settings\All Users\Application Data\Microsoft\Windows
NT\MSFax\Queue\1C73596B0AC80.FQE" "abc -
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\MSFaxConsoleTempPreview-#0000061c8e127ce5.tif"
17184 4 "confident.cov" "to 91280 01234 111111" " " "localDomain\abcAdmin"
"Administrator" "+44 (0) 1708 111111" "St Kitts & Nevis Int" "West Wing,
York House 48-50 Western Road Romford, Essex, RM1 3LP" " " " " " " " " " "
" " " " "+44 (0) 1708 111110" " " "abc" "91280 111111" " " " " " " " " " " "
" " " " " " " " " " " " "
"0x0201c73596d7873f" "0x2001c73596d784f5" 1/11/2007 15:40:38 1/11/2007
15:40:38 "Transmission error" "Unknown fatal error" "0x0000000c" 1/11/2007
16:12:17 1/11/2007 16:12:50 "Courier V.Everything EXT PnP (V90-x2)" "91280
222222" "St Kitts & Nevis Int" "St Kitts & Nevis Int" 1 2 "C:\Documents and
Settings\All Users\Application Data\Microsoft\Windows
NT\MSFax\Queue\1C73596D7873F.FQE" "abc -
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\MSFaxConsoleTempPreview-#0000061c04346041.tif"
17100 4 "confident.cov" "to 1280 01234 222222" " " "localDomain\abcAdmin"
"Administrator" "+44 (0) 1708 111111" "St Kitts & Nevis Int" "West Wing,
York House 48-50 Western Road Romford, Essex, RM1 3LP" " " " " " " " " " "
" " " " "+44 (0) 1708 111110" " " "abc" "91280 222222" " " " " " " " " " " "
" " " " " " " " " " " " "
"0x0201c735bf357abb" "0x2001c735bf357871" 1/11/2007 20:29:35 1/11/2007
20:29:35 "Transmission error" "Unknown fatal error" "0x0000000c" 1/11/2007
21:09:51 1/11/2007 21:10:24 "Courier V.Everything EXT PnP (V90-x2)" "91280
111111" "+441708222222" "St Kitts & Nevis Int" 1 2 "C:\Documents and
Settings\All Users\Application Data\Microsoft\Windows
NT\MSFax\Queue\1C735BF357ABB.FQE" "abc 91280 111111 -
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\MSFaxConsoleTempPreview-#000016a0cf0e66ea.tif"
17824 4 "confident.cov" "abc 91280 111111" " " "localDomain\abcAdmin" "St
Kitts & Nevis Int." "+44 (0) 1708 111111" "St Christopher & Nevis
International Ship Registry" "West Wing, York House 48-50 Western Road
Romford Essex, RM1 3LP" " " " " " " " " " " " " " " "+44 (0) 1708 111110"
"Ma...@Domain.com" "abc 91280 111111" "91280 111111" " " " " " " " " " " " "
" " " " " " " " " " " "
"0x0201c735bf4a7fe5" "0x2001c735bf4a7d74" 1/11/2007 20:30:10 1/11/2007
20:30:10 "Transmission error" "Unknown fatal error" "0x0000000c" 1/11/2007
21:10:24 1/11/2007 21:10:54 "Courier V.Everything EXT PnP (V90-x2)" "91280
222222" "St Kitts & Nevis Int" "St Kitts & Nevis Int" 1 2 "C:\Documents and
Settings\All Users\Application Data\Microsoft\Windows
NT\MSFax\Queue\1C735BF4A7FE5.FQE" "abc 91280 222222 -
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\MSFaxConsoleTempPreview-#000016a0eda134af.tif"
17736 4 "confident.cov" "abc 91280 222222" " " "localDomain\abcAdmin" "St
Kitts & Nevis Int." "+44 (0) 1708 111111" "St Christopher & Nevis
International Ship Registry" "West Wing, York House 48-50 Western Road
Romford Essex, RM1 3LP" " " " " " " " " " " " " " " "+44 (0) 1708 111110"
"Ma...@Domain.com" "abc 91280 222222" "91280 222222" " " " " " " " " " " " "
" " " " " " " " " " " "

Best Regards,

[Gregg Hill]

Nick,

This hotfix may not help, but it certainly won't hurt.

http://support.microsoft.com/kb/919009/en-us

Gregg Hill

"Nick" <NoS...@Nowhere.com> wrote in message
news:e%233oJrmN...@TK2MSFTNGP04.phx.gbl...

[Inn Jin [MSFT]]

Hi Nick,

Thank you for updating and thanks for Gregg's input.

I am sorry for the delay in response due to the weekend, thanks for the
understanding.

I have already check the Activity log, it is strange that the error message
came out after you reinstalled the fax component, since you have
reinstalled the fax component, all files related to the fax will be
replaced on the server, there could not be some corrupt files. Have you
tried reinstalling the fax driver? As the driver are files may be
influenced by running SFC. Please uninstall and install the latest driver
and see how everything goes on. Also I would like you to change a fax modem
just for test purpose.

If the issue persists, please gather the MPS report and send to me at
v-in...@microsoft.com

I appreciate your effort and cooperation. I'm looking forward to your reply.

[Nick]

Could it be a driver issue as you suggested?

Remember these are two US Robotics Courier V. Everythings, slightly
different models, one was original USR the other post 3COM takeover, but
both have performed fine until now..

Under driver details both modems are using the Microsoft Modem.sys
5.2.3790.0 (srv03_rtm.030324-2048). However, on the basic Driver tab they
appear to be using different drivers:
Courier V.Everything EXT PnP (V90-x2) is using 01/10/2002 5.10.1.18
but
Courier V.Everything V.90 X2 European PnP is using the older 01/06/1999
5.0.0.0!
How can this have occured, could me running SFC.exe have done this? More
importantly where would I find the 5.10.1.18 driver file to install instead
of the older 5.0.0.0? Update driver does not find anything newer.

Bearing in mind that we have never used any external drivers for these, this
server has only ever seen the default SBS drivers.

Could the drivers have always been like this and working fine, is it just
because one is a USR the other a 3COM? Is there anything I can look at on
an old backup which would tell us what drivers had been in use previously?

Regards,
Nick

""Inn Jin [MSFT]"" <v-in...@online.microsoft.com> wrote in message

news:GXwOR89N...@TK2MSFTNGHUB02.phx.gbl...

[Inn Jin [MSFT]]

Hi Nick,

Thank you for updating.

After checking your modems in our HCL site, I didn't find your modems'
model in our windows 2003 category list. I understand it is compatible in
SBS 4.5, but please notice that SBS 4.5 and SBS 2003 has different
architectures, devices compatible with SBS 4.5 may not compatible in SBS
2003. Devices are not in our HCL list means they didn't compatible with
windows 2003 and SBS 2003 or we haven't test yet, we can't guarantee that
those device will work fine on windows 2003. What I can do is try my best
to help you isolate the issue, your understanding will be appreciated.

Back to the issue, I understand this issue was occurred after running SFC,
this tool will try to retrieve the windows protected files which have
changed, that may cause some issue, especially to some old devices. I
suggest you install the driver from the fax vendors, you can download from
their website or contact them for window 2003 version. And install them or
you can click upgrade drivers… button in the properties window, and choose
the location of the driver provided by vendor, after installation, please
test the issue. Also I notice that you have tons of disk issue in your
event log, I suggest you run the check chkdsk utility on your hard disk
than test the issue.

In addition, please try another fax modem that is in the HCL windows 2003
category list just for test purpose. And see if it is the server issue or
the hardware issue.

About your different modem use different drivers, that could be, since
different devices using different drivers. For your question about how to
see the driver used by devices in backup file, I'm afraid we don't have
such feature to do so. Your understanding will be appreciated.

[Gregg Hill]

Inn Jin,

While the US Robotics and 3Com Courier V.Everything external modems are not
on the Server 2003 HCL, they are frequently recommended by Crina Li and
others as the modem of choice when receiving is a problem. I have asked
Crina to clarify why the 3Com is recommended in spite of its absence from
the HCL, but I have never gotten a response.

Gregg Hill

""Inn Jin [MSFT]"" <v-in...@online.microsoft.com> wrote in message

news:y7HvtrFO...@TK2MSFTNGHUB02.phx.gbl...

[Nick]

> After checking your modems in our HCL site, I didn't find your modems'
> model in our windows 2003 category list. I understand it is compatible in
> SBS 4.5, but please notice that SBS 4.5 and SBS 2003 has different
> architectures, devices compatible with SBS 4.5 may not compatible in SBS
> 2003. Devices are not in our HCL list means they didn't compatible with
> windows 2003 and SBS 2003 or we haven't test yet, we can't guarantee that
> those device will work fine on windows 2003. What I can do is try my best
> to help you isolate the issue, your understanding will be appreciated.

As most people who have been working with SBS for a number of years will
agree the USR Courier is simply the most stable and reliable modem
available. I would prefer not to take a backwards step and switch to
something less capable simply because it happens to be on a Microsoft
hardware list.

> Back to the issue, I understand this issue was occurred after running SFC,
> this tool will try to retrieve the windows protected files which have
> changed, that may cause some issue, especially to some old devices. I
> suggest you install the driver from the fax vendors, you can download from
> their website or contact them for window 2003 version.

These modems did not require any external drivers SBS detected them
automatically and installed native Microsoft driversfor them. They worked
fine for eighteen months or so until I ran SFC.exe of this server; never
missed a beat and often received faxes for far flung corners of the world
that manual fax machines were incapable of receiving.

I would prefer not to install any external drivers, all I want is to revert
to the Microsoft supplied drivers that SBS installed on it's own which were
in use before SFC ran!

> Also I notice that you have tons of disk issue in your
> event log, I suggest you run the check chkdsk utility on your hard disk
> than test the issue.

Chkdsk has been run numerous times and the disks are clean, including full
surface scan. These disk errors relate to a broken RAID mirror which I am
working on solving as a seperate issue.

Best regards,
Nick

[Nick]

Greg,

> While the US Robotics and 3Com Courier V.Everything external modems are
> not on the Server 2003 HCL, they are frequently recommended by Crina Li
> and others as the modem of choice when receiving is a problem. I have
> asked Crina to clarify why the 3Com is recommended in spite of its absence
> from the HCL, but I have never gotten a response.

Good to know you are of a similar opinion regarding these modems. I suggest
that the US Robotics.3COM Couriers are recomended simply because they are
the most stable and robust modems available. I have seen these things
receive faxes over bad lines that no other machine could do.

Albeit anecdotal evidence suggests the 3COM manufactured ones are not quite
as well made as the USRobotics ones were. I have seen a couple of recent
3COM ones DOA due to faulty power supplies. In all the years we were
supplying US Robotics ones I cannot recall a single failure.

Nick

[Inn Jin [MSFT]]

Hi Nick,

Thank you for updating and thank Gregg's input.

Please notice that, installing driver and changing another modem doesn't
mean that it is related to the hardware issue 100% percent. Just want to
isolate the cause which can help us to solve the issue in a efficient
manner. Both of us has the same purpose, that is to solve this issue, and
what I want to do is try all my could to help you solve the issue. Your
cooperation is appreciated. Remember, installing the driver and changing
another modem is just for test purpose and temporary!

I have found the website of your modem vendor in the URL below for your
reference, you may download the driver and installed them.

http://www.usr.com/support/s-main-menu.asp

Meanwhile please try to unplug one modem and keep just one on the line,
then test the issue. Then exchange them and try again. Please replace the
telephone line then try again. Do you have some fax software? if so, please
try to uninstall and reinstall it just for test purpose.

Also please follow the steps below to collect T30 log for further test.

a) Run regedit.exe.

b) Navigate to this key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fax\Device
Providers\{2172FD8F-11F6-11D3-90BF-006094EB630B}

c) Create new or modify values as follows:

value name: DeBugLevelEx
value type: REG_DWORD
value: 0xffffffff

value name: DebugContextEx
value type: REG_DWORD
value: 0xffffffff

value name: DeBugFormatEx
value type: REG_DWORD
value: 0xbbffffff

d) Please reproduce the issue and zip the C:\Documents and
Settings\NetworkService\Local Settings\temp folder as a .zip file.

e) Undo the registry changes.

f) Please send the file to me at v-in...@microsoft.com

[Gregg Hill]

If you really want to send and receive over crappy lines, nothing beats a
Brooktrout card.

However, as you have been running just fine in the past, you should not need
a new device, but I agree with Inn Jin to at least test with one.

Gregg Hill

"Nick" <NoS...@Nowhere.com> wrote in message

news:OZL3WmJ...@TK2MSFTNGP06.phx.gbl...

[Nick]

Hi Inn Jin,

I have modified the registry values as you suggested and sent a fax but
nothing is getting written into the T30DebugLogFile.txt or anywhere else in
that directory. Do I need to change any other settings to start this logging
working?

However I did spot some logs in the C:\Windows\System32\LogFiles\Fax
directory see below. Do they help at all?

Best regards,

Nick

Outgoing:
[15/01/2007 18:23:43]
Device name: Courier V.Everything EXT PnP (V90-x2)
Permanent TAPI line ID: A32E71D
Unimodem registry key: 0000
Job type: Send

[18:23:43][173666203][ 130173][ ] Modem initialization
[18:23:43][173666250][ 131580][ ] send:
"AT&FS0=0E0V1Q0"
[18:23:44][173666500][ 131688][ ] recv: "OK"
[18:23:44][173666546][ 131580][ ] send: "AT"
[18:23:44][173666781][ 131688][ ] recv: "OK"
[18:23:44][173666828][ 131580][ ] send:
"ATB0X4&D2&C1&H1&R2&I0&A3&M4&B1S7=255"
[18:23:44][173667062][ 131688][ ] recv: "OK"
[18:23:44][173667109][ 131580][ ] send: "ATM1L0"
[18:23:44][173667359][ 131688][ ] recv: "OK"
[18:23:44][173667359][ 330104][ ] Phase A - Call establishment
[18:23:44][173667359][ 330117][ ] Dialing...
[18:23:45][173667468][ 130698][ ] send:
"AT+FCLASS=1"
[18:23:45][173668015][ 131580][ ] send: "AT"
[18:23:45][173668250][ 131688][ ] recv: "OK"
[18:23:45][173668453][ 130872][ ] send: "ATDT
###########"
[18:24:04][173686765][ 131688][ ] recv:
"CONNECT"
[18:24:04][173686765][ 131078][ ] Response - CONNECT
[18:24:04][173686765][ 310214][ ] Phase B - Negotiation
[18:24:05][173687921][ 50750][ ] recv: HDLC
frame, 47 bytes, ff 03 20 00 00 11 80 00 80 49 10 53 4b 41 4e 52 45 47 20 20
20 20 20 20 20 20 20 00 5b 00 80 80 c0 07 02 01 00 01 01 01 01 3c b8 10 03
0d 0a
[18:24:05][173687921][ 131688][ ] recv: "OK"
[18:24:05][173687921][ 312046][ ] frame is NSF,
non-final frame
[18:24:05][173687921][ 131580][ ] send:
"AT+FRH=3"
[18:24:05][173688031][ 131688][ ] recv:
"CONNECT"
[18:24:06][173688640][ 50750][ ] recv: HDLC
frame, 29 bytes, ff 03 40 31 31 36 31 34 37 38 30 37 31 34 34 2b 20 20 20 20
20 20 20 75 80 10 03 0d 0a
[18:24:06][173688640][ 131688][ ] recv: "OK"
[18:24:06][173688640][ 312046][ ] frame is CSI,
non-final frame
[18:24:06][173688640][ 131580][ ] send:
"AT+FRH=3"
[18:24:06][173688750][ 131688][ ] recv:
"CONNECT"
[18:24:06][173689000][ 50750][ ] recv: HDLC
frame, 13 bytes, ff 13 80 00 ce 88 44 e0 9a 10 03 0d 0a
[18:24:06][173689000][ 131688][ ] recv: "OK"
[18:24:06][173689000][ 312046][ ] frame is DIS,
final frame
[18:24:06][173689000][ 370155][ ] CSI is "+441708741611"
[18:24:06][173689000][ 370256][ ] DIS specified the following
capabilities:
[18:24:06][173689000][ 380039][ ] - Supported Modulations:
V.27 ter, V.29
[18:24:06][173689000][ 380040][ ] - Ability to use fine
resolution: Yes
[18:24:06][173689000][ 380041][ ] - Ability to use 2D coding:
Yes
[18:24:06][173689000][ 380042][ ] - Supported Page Width:
1728
[18:24:06][173689000][ 380043][ ] - Supported Page Length:
Unlimited
[18:24:06][173689000][ 380044][ ] - Minimum scan line time:
20
[18:24:06][173689000][ 300116][ ] TSI is "St Kitts & Nevis
Int"
[18:24:06][173689000][ 300159][ ] DCS Composed as follows:
[18:24:06][173689000][ 380065][ ] - Session Modulation is:
9600 bps V.29
[18:24:06][173689000][ 380066][ ] - Use fine resolution: Yes
[18:24:06][173689000][ 380067][ ] - Use 2D coding: Yes
[18:24:06][173689000][ 380068][ ] - Page width is 1728
[18:24:06][173689000][ 380069][ ] - Page length is A4
[18:24:06][173689000][ 380070][ ] - Scan line time: 20
[18:24:06][173689000][ 310522][ ] Sending TSI-DCS
[18:24:06][173689062][ 131580][ ] send:
"AT+FTH=3"
[18:24:06][173689234][ 131688][ ] recv:
"CONNECT"
[18:24:06][173689234][ 200267][ ] send: TSI, 23
bytes, ff 03 43 74 6e 49 20 73 69 76 65 4e 20 26 20 73 74 74 69 4b 20 74 53
[18:24:06][173689234][ 50408][ ] send:
<dle><etx>
[18:24:08][173690984][ 131688][ ] recv:
"CONNECT"
[18:24:08][173690984][ 200267][ ] send: DCS, 6
bytes, ff 13 83 00 c6 00
[18:24:08][173690984][ 50408][ ] send:
<dle><etx>
[18:24:09][173691687][ 131688][ ] recv: "OK"
[18:24:09][173691687][ 310567][ ] Sending TCF...
[18:24:09][173691687][ 131580][ ] send:
"AT+FTM=96"
[18:24:09][173692031][ 131688][ ] recv:
"CONNECT"
[18:24:09][173692031][ 50202][ ] send: 900
zeroes
[18:24:09][173692031][ 200300][ ] send: 900
zeroes
[18:24:09][173692062][ 50354][ ] send:
<dle><etx>
[18:24:11][173693656][ 131688][ ] recv: "OK"
[18:24:11][173693656][ 310576][ ] Successfully sent TCF
[18:24:11][173693656][ 131580][ ] send:
"AT+FRH=3"
[18:24:12][173694750][ 131688][ ] recv:
"CONNECT"
[18:24:12][173695000][ 50750][ ] recv: HDLC
frame, 9 bytes, ff 13 84 ea 7d 10 03 0d 0a
[18:24:12][173695000][ 131688][ ] recv: "OK"
[18:24:12][173695000][ 312046][ ] frame is CFR,
final frame
[18:24:12][173695000][ 310626][ ] Received CFR
[18:24:12][173695000][ 310667][ ] Phase C - Page transmission
[18:24:12][173695046][ 131580][ ] send: "AT"
[18:24:12][173695281][ 131688][ ] recv: "OK"
[18:24:12][173695343][ 131580][ ] send:
"AT+FTH=3"
[18:24:13][173695515][ 131688][ ] recv:
"CONNECT"
[18:24:13][173695515][ 200210][ ] send: DCN, 3
bytes, ff 13 fb
[18:24:13][173695515][ 50408][ ] send:
<dle><etx>
[18:24:14][173696734][ 131688][ ] recv: "OK"
[18:24:14][173696734][ 130804][ ] Hanging up
[18:24:14][173696781][ 131580][ ] send: "ATH0"
[18:24:14][173697218][ 131688][ ] recv: "OK"
[18:24:14][173697265][ 131580][ ] send: "ATH0"
[18:24:15][173697500][ 131688][ ] recv: "OK"
[18:24:15][173697609][ 130698][ ] send:
"AT+FCLASS=0"
[18:24:15][173698156][ 131580][ ] send: "AT"
[18:24:15][173698390][ 131688][ ] recv: "OK"
[18:24:15][173698437][ 131580][ ] send: "AT"
[18:24:16][173698671][ 131688][ ] recv: "OK"
[18:24:17][173699906][ 321878][ERR] Failed send

Incoming:
[04/01/2007 08:52:52]
Device name: Courier V.Everything V.90 X2 European PnP
Permanent TAPI line ID: C8474D
Unimodem registry key: 0001
Job type: Receive

[08:52:52][246697437][ 130173][ ] Modem initialization
[08:52:52][246697484][ 131580][ ] send:
"AT&FS0=0E0V1Q0"
[08:52:52][246697718][ 131688][ ] recv:
"AT&FS0=0E0V1Q0"
[08:52:52][246697718][ 131688][ ] recv: "OK"
[08:52:52][246697765][ 131580][ ] send: "AT"
[08:52:53][246698000][ 131688][ ] recv: "OK"
[08:52:53][246698046][ 131580][ ] send:
"ATB0X4&D2&C1&H2&I2&R1&A3&M4&B1"
[08:52:53][246698281][ 131688][ ] recv: "OK"
[08:52:53][246698328][ 131580][ ] send: "ATM1L0"
[08:52:53][246698562][ 131688][ ] recv: "OK"
[08:52:53][246698562][ 330019][ ] Phase A - Call establishment
[08:52:53][246698562][ 330030][ ] Answering...
[08:52:53][246698609][ 131580][ ] send:
"AT+FCLASS=1"
[08:52:53][246698718][ 131688][ ] recv: "OK"
[08:52:53][246698765][ 131580][ ] send:
"AT+FAA=1"
[08:52:54][246698875][ 131688][ ] recv: "OK"
[08:52:54][246699078][ 131204][ ] send: "ATA"
[08:52:55][246700656][ 131688][ ] recv: "FAX"
[08:52:59][246703781][ 131688][ ] recv:
"CONNECT"
[08:52:59][246703781][ 310227][ ] Phase B - Negotiation
[08:52:59][246703781][ 300036][ ] CSI is "SKANReg"
[08:52:59][246703781][ 370475][ ] Composing DIS with the
following capabilities:
[08:52:59][246703781][ 380039][ ] - Supported Modulations:
V.27 ter, V.29, V.33, V.17
[08:52:59][246703781][ 380040][ ] - Ability to use fine
resolution: Yes
[08:52:59][246703781][ 380041][ ] - Ability to use 2D coding:
Yes
[08:52:59][246703781][ 380042][ ] - Supported Page Width:
1728
[08:52:59][246703781][ 380043][ ] - Supported Page Length:
Unlimited
[08:52:59][246703781][ 380044][ ] - Minimum scan line time: 0
[08:52:59][246703781][ 310930][ ] Sending CSI-DIS
[08:52:59][246703843][ 200267][ ] send: CSI, 23
bytes, ff 03 40 20 20 20 20 20 20 20 20 20 20 20 20 20 67 65 52 4e 41 4b 53
[08:52:59][246703843][ 50408][ ] send:
<dle><etx>
[08:53:00][246705531][ 131688][ ] recv:
"CONNECT"
[08:53:00][246705531][ 200267][ ] send: DIS, 6
bytes, ff 13 80 00 ee 78
[08:53:00][246705531][ 50408][ ] send:
<dle><etx>
[08:53:01][246706234][ 131688][ ] recv: "OK"
[08:53:01][246706234][ 310938][ ] Successfully sent CSI-DIS -
receiving response
[08:53:01][246706234][ 131580][ ] send:
"AT+FRH=3"
[08:53:03][246708203][ 131688][ ] recv:
"CONNECT"
[08:53:03][246708203][ 50750][ ] recv: HDLC
frame, 29 bytes, ff 03 43 33 39 36 39 36 34 20 38 32 20 34 33 20 20 20 20 20
20 20 20 e2 67 10 03 0d 0a
[08:53:03][246708203][ 131688][ ] recv: "OK"
[08:53:03][246708203][ 312046][ ] frame is TSI,
non-final frame
[08:53:03][246708203][ 131580][ ] send:
"AT+FRH=3"
[08:53:03][246708468][ 131688][ ] recv:
"CONNECT"
[08:53:03][246708468][ 50750][ ] recv: HDLC
frame, 13 bytes, ff 13 83 00 a2 98 00 73 b6 10 03 0d 0a
[08:53:03][246708468][ 131688][ ] recv: "OK"
[08:53:03][246708468][ 312046][ ] frame is DCS,
final frame
[08:53:03][246708468][ 311215][ ] Receiving TCF...
[08:53:03][246708468][ 131580][ ] send:
"AT+FRM=145"
[08:53:05][246710359][ 131688][ ] recv:
"CONNECT"
[08:53:07][246711843][ 200588][ ] recv: TCF:
0 errors in 1080 signifact bytes of 2917 total bytes
[08:53:07][246711843][ 370155][ ] TSI is "34 28 469693"
[08:53:07][246711843][ 370176][ ] Received DCS is as follows:
[08:53:07][246711843][ 380065][ ] - Session Modulation is:
14400 bps V.17
[08:53:07][246711843][ 380066][ ] - Use fine resolution: No
[08:53:07][246711843][ 380067][ ] - Use 2D coding: Yes
[08:53:07][246711843][ 380068][ ] - Page width is 1728
[08:53:07][246711843][ 380069][ ] - Page length is Unlimited
[08:53:07][246711843][ 380070][ ] - Scan line time: 5
[08:53:07][246711843][ 311284][ ] Received good TCF - sending
CFR
[08:53:07][246711843][ 131580][ ] send:
"AT+FTH=3"
[08:53:07][246712031][ 131688][ ] recv:
"CONNECT"
[08:53:07][246712031][ 200210][ ] send: CFR, 3
bytes, ff 13 84
[08:53:07][246712031][ 50408][ ] send:
<dle><etx>
[08:53:08][246713234][ 131688][ ] recv: "OK"
[08:53:08][246713234][ 311292][ ] Successfully sent CFR
[08:53:08][246713234][ 311337][ ] Phase C - Receive page
[08:53:08][246713234][ 131580][ ] send:
"AT+FRM=146"
[08:53:09][246714125][ 131688][ ] recv:
"CONNECT"
[08:53:09][246714125][ 311433][ ] Receiving page 1 data...
[08:53:09][246714171][ 131580][ ] send: "AT"
[08:53:09][246714250][ 131688][ ] recv:
"O?č "
[08:53:09][246714296][ 131580][ ] send: "AT"
[08:53:09][246714531][ 131688][ ] recv: "OK"
[08:53:09][246714531][ 130804][ ] Hanging up
[08:53:09][246714578][ 131580][ ] send: "ATH0"
[08:53:10][246714953][ 131688][ ] recv: "OK"
[08:53:10][246715000][ 131580][ ] send: "ATH0"
[08:53:10][246715234][ 131688][ ] recv: "OK"
[08:53:10][246715343][ 130698][ ] send:
"AT+FCLASS=0"
[08:53:11][246715890][ 131580][ ] send: "AT"
[08:53:11][246716125][ 131688][ ] recv: "OK"
[08:53:11][246716171][ 131580][ ] send: "AT"
[08:53:11][246716406][ 131688][ ] recv: "OK"
[08:53:12][246717093][ 322612][ERR] Failed receive

""Inn Jin [MSFT]"" <v-in...@online.microsoft.com> wrote in message

news:ul$PBoKOH...@TK2MSFTNGHUB02.phx.gbl...

[Nick]

Hello Inn Jin,

Something else I have just noticed both the incoming fax modem and the
outgoing one stopped working at the same time, when I ran sfc.exe! This
suggests that the problem is Windows System related rather than a hardware
failure. I have tried both sending to and receiving from a standalone fax
machine (which would have used two different modems), both of which failed.

Are you completely sure that there was no update to the fax component in
service pack 1. The FaxCfg.exe/.dll on the SBS CD3 are version 5.2.2651
while the ones in our C:\Program Files\Microsoft Windows Small Business
Server\fax directory are version 5.2.2893. This newer version must have
come from somewhere any idea where.

Thanks,
Nick

""Inn Jin [MSFT]"" <v-in...@online.microsoft.com> wrote in message

news:ul$PBoKOH...@TK2MSFTNGHUB02.phx.gbl...

[Nick]

Hi Inn Jin,

One other thing worth checking: are the files in
C:\WINDOWS\system32\clients\faxclient\drivers involved in the fax device in
anyway? The reason I mention these is because having searched through my
previous notes there were numerous files in here that were detected by
sfc.exe as having 'Bad Signatures' which were then restored from the
original version.

All the files I currently have in this directory are ver. 5.2.3790.1830
except fxsdrv.dll which shows as version 0.3.3790.1830 albeit Product
Version detail lists it as 5.2.3790.1830.

Regards,
Nick

"Nick" <NoS...@Nowhere.com> wrote in message

news:%23qhjMOW...@TK2MSFTNGP04.phx.gbl...

[Gregg Hill]

Did you restart the fax service first?

Gregg Hill

"Nick" <NoS...@Nowhere.com> wrote in message

news:uRBgIsVO...@TK2MSFTNGP06.phx.gbl...

[Gregg Hill]

Nick,

The 5.2.2651 version is the initial release. The 5.2.2893 matches my SP1
server. Are you running SBS 2003 SP1 or the initial release?

Also, the folder dates on your CD3 should be 12/1/03. If not, you have an
old CD3 and it should be tossed.

Gregg Hill

"Nick" <NoS...@Nowhere.com> wrote in message

news:%23qhjMOW...@TK2MSFTNGP04.phx.gbl...

[Inn Jin [MSFT]]

Hi Nick,

Thank you for your mail.

I appreciate your detailed effort on this issue and want to say the log
files you send to me is just same as T30 log (although they are not).
However, I need to inform first, as your modem is not in the HCL list, we
cannot guarantee it will completely compatible with OS, and cannot
guarantee it will completely work fine either. Also products out of HCL
list are out of my support boundary. All what I have done is to want to
help you solve your issue even it is out of my support boundary.

Following are answers to you questions:

1. For the Microsoft drivers:

Microsoft drivers are designed for industrial standards, it is general
drivers, all though most of the device vendors are design their products
base on industrial standards, but they have different specific features
which are different with our vendors, we cannot guarantee our drivers can
fulfill all the vendor specific features. That's why I asked you to change
your driver to make sure your driver can be completely suitable for you
device.

2. For the change of modem driver version

Microsoft Updates contain many fields including hardware. We upgrade our
driver, because we found some need to be change, for example we fix some
bugs, or we need to change because change of industrial standard. Moreover,
these hardware updates can be conclude in any windows updates, we make
description of every updates. You can referred to the description.

3. Files in "C:\WINDOWS\system32\clients\faxclient\drivers" folder is not
related to the driver use by server, it is related to the clients which may
related to this issue if the fax modem was shared with these clients.

Back up to the issue, after carefully analyzing your logs, and long
discussion with our specialists in fax, we agreed this issue belongs to the
driver or the hardware.

[20:30:54][000583062][ 131580][ ] send:
"AT+FRM=146"
[20:30:56][000585562][ 131688][ ] recv: "NO
CARRIER"
[20:30:57][000585765][ 131580][ ] send:
"AT+FRM=146"
[20:30:59][000588265][ 131732][WRN] failed to
receive expected response: CONNECT, +FCERROR, NO CARRIER
[20:30:59][000588265][ 131739][ ] send: "AT"
[20:30:59][000588343][ 131754][ ] recv: "OK"
[20:30:59][000588343][ 311419][WRN] Failed to receive page 1 -
receiving commands
[20:30:59][000588343][ 131580][ ] send:
"AT+FRH=3"
[20:31:05][000594343][ 131732][WRN] failed to
receive expected response: CONNECT, +FCERROR, NO CARRIER
[20:31:05][000594343][ 131739][ ] send: "AT"
[20:31:05][000594421][ 131754][ ] recv: "OK"
[20:31:05][000594421][ 311115][ERR] Failed to receive command
- aborting

This part code indicates that error are related to driver or hardware.

Here is the workaround:
1. Please copy all the files related to the fax driver, copy it to a folder
in your local hard disk
2. Restart the server into save mode (Press F8 when the server reboot)
3. When start as save mode, please run services.msc make sure fax service
is not start. If it starts, please stop it.
4. Copy all the fax driver files to the system folder which it should be.
replace them with the files in the system folder.
5. For .dll files, please type the following commands in the command prompt:

Regsvr32 <the file name>

6. Restart the server normally to check whether the issue persist.

If the issue persists, please contact the fax modem vendor and install
drivers from vendor, or change your hardware to isolate the issue. If my
suggestion don't help. I'll happy to assist you if you can try the drivers
from the vendor.

I appreciate your understanding and cooperating.

[NickC]

Yep, have now restarted the whole server but still no T30 debug fetting
written.

"Gregg Hill" <bo...@nowhere.com> wrote in message
news:ucLBosdO...@TK2MSFTNGP04.phx.gbl...

[NickC]

Hello Inn Jin, thank you for your assistance.

I have tested with two different modems (same models) and still get exactly
the same problem. I have also tested the line with standalone fax machines
which all work fine.

Have tried to update the drivers but that is not possible. The drivers
available on the 3COM site are not certified so SBS2003 will not let me
install them. Also SBS informs me that 'The Wizard could not find a better
match for your hardware than the software you currently have installed'. I
have deleted the modems from device manager and let it detect them again
which reinstalls them without using any external or third-party drivers
using purely the native Microsoft ones.

I have now found a way around this to allow installation of not certified
drivers although I still think this is more dangerous than using the native
drivers. Using the 'Have disk' button I have managed to overwrite the
native Microsoft drivers with the latest US Robotics/3COM drivers.... Still
got the same problem new drivers have made not the slightest difference.

Can you appreciate my problem with not being able to buy new modems; this
customer has been using this model of modem for the past ten years and has
never has a single problem with them. Also this particular pair of modems
have been working perfectly well for the past eighteen months or more. It
is going to be very dificult for me to try and explain to this client that
they need new modems even though there is nothing wrong with the old ones!

Windows update does not detect any updated harware drivers for the modems.

With regard to your workaround: > 1. Please copy all the files related to
the fax driver
Where do find these files? Where are all the files related to the fax
driver?

I still have tape backups of this server from when the fax was working. If
I could identify all the files that are involved in the fax system I could
restore them from that.

Regards,
Nick

""Inn Jin [MSFT]"" <v-in...@online.microsoft.com> wrote in message

news:dzFk5HjO...@TK2MSFTNGHUB02.phx.gbl...

[NickC]

Wow this is getting worrying I thought Inn Jin said that there were no
changes to the fax component in SBS service pack 1!

"Gregg Hill" <bo...@nowhere.com> wrote in message

news:u6pAHvdO...@TK2MSFTNGP02.phx.gbl...

[Gregg Hill]

Nick,

Are you running SBS 2003 SP1 or the initial release?

If you updated to SP1, did you do all the steps or just install Windows
Server 2003 SP1?

When you ran SFC, to where did you point it for the files it needed?

If you have not gone to SP1 yet, why not?

Gregg Hill

"NickC" <NoOn...@BTInternet.com> wrote in message
news:%238ncUmm...@TK2MSFTNGP04.phx.gbl...

[Nick]

Hi Greg, thank you for your continued help.

We are running SP1 and have been for a while; this was installed around a
year ago along with the SBS SP1 fix and various other updates - Sharepoint,
Exchange, etc.

Before running SFC I set/checked the following registry entries:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\SourcePath
= X:\Source\SBS2003\CD1

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SourcePath =
X:\Source\SBS2003\CD1

As you have probably guessed these both point towards an on disk copy of the
SBS installetion CD.

Any suggestions what to do next, how about the idea of restoring windows
system files from a tape backup pre SFC; when the fax was still working.
Question is what windows system files are involved in the Fax process, how
can I identify what files to restore?

Nick

"Gregg Hill" <bo...@nowhere.com> wrote in message

news:OUgj8AqO...@TK2MSFTNGP04.phx.gbl...

[Gregg Hill]

Nick,

When you pointed it to X:\Source\SBS2003\CD1, is that an SP1 CD or the
original CD? Was this an RTM that was upgraded to SP1, or an integrated SP1
installation?

It seems to me that your source when you ran SFC was the initial
installation CD files.

Have you tried re-installing SP1?

I'd wait for In Jin to answer the question of which files to restore.

Gregg Hill

"Nick" <NoS...@Nowhere.com> wrote in message

news:OgIu1jzO...@TK2MSFTNGP02.phx.gbl...

[Nick]

Gregg,

> When you pointed it to X:\Source\SBS2003\CD1, is that an SP1 CD or the
> original CD? Was this an RTM that was upgraded to SP1, or an integrated
> SP1 installation?

Yep that was the original CD (pre-sp1).

> It seems to me that your source when you ran SFC was the initial
> installation CD files.

Yes but apparently that is alright; SFC supposedly uses the following
registry key to look after service pack updates doesn't it?

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePackSourcePath
= c:\windows\ServicePackFiles

> Have you tried re-installing SP1?

No I have to admin that I have not resinatalled SP1 because I am not sure
what post SP1 fixes may also than need to be run, maybe none but I am not
sure. The post service pack 1 fixes that I ran after the original SP1
install were:
Sharepoint services 2.0 service pack 1

KB891193 windows XP SP2 for client deployment

Exchange Server 2003 service pack 1

KB885918

SBS 2003 service pack 1

Exchange Server 2003 service pack 2

Do you think I should reapply SP1? This might be pushing it a bit but I
wonder if I can run it remotely, if so I can run it this evening and see
what happens.

All the best,
Nick

"Gregg Hill" <bo...@nowhere.com> wrote in message

news:ut5ceJ5O...@TK2MSFTNGP02.phx.gbl...

[Inn Jin [MSFT]]

Hi Nick,

Thank you for updating and thanks Greg's input.

Sorry for the delay due to personal affair.

The file related to the fax drive is located in
C:\windows\system32\spool\drivers\w32x86\3. And the files are fxsapi.dll,
fxsdrv.dll, fxsres.dll, fxstiff.dll, fxsui.dll and fxswzrd.dll. If you have
clients which share this fax modem, you need also replace the files located
in C:\WINDOWS\system32\clients\faxclient\drivers.

NOTE: The replacement should be perform in safe mode, and only register the
.dll files in C:\windows\system32\spool\drivers\w32x86\3.

Also you may contact your vendor for the fax driver designed for 2003, as
the new default fax driver may not compatible for your fax modem.

I appreciate your time and effort.

[Nick]

Inn Jin thanks for the information. As I am not on-site with the server at
the moment but connecting to it remotely I cannot have accesss to the server
in safe mode at the moment, I will try to get into the office tommorrow and
copy these in safe mode as you suggest.

I have recovered all of these files from a previous backup but they appear
to be the same size, date and version as those currently installed. However
I do seem to recall seeing these series of Fxs* files as having bad
signatures and being replaced with the originals when I ran sfc.exe.

Still using the current files I tried to reregister them with RegSvr32
Fxs....dll they all fail with the error:
'FXS. was loaded, but the DLLRegisterServer entry point was not found.
This file can not be registered'
Does this indicate that they are corrupt or that some other dependent file
is faulty?

Don't know if it will work because system file protection might overwright
them again but I am about to try recovering these from tape and letting
NTBackup overwrite them, do you think that will work?

Regards,
Nick

""Inn Jin [MSFT]"" <v-in...@online.microsoft.com> wrote in message

news:tjYt4b9O...@TK2MSFTNGHUB02.phx.gbl...

> Hi Nick,
>
> Thank you for updating and thanks Greg's input.
>
> Sorry for the delay due to personal affair.
>
> The file related to the fax drive is located in
> C:\windows\system32\spool\drivers\w32x86\3. And the files are fxsapi.dll,
> fxsdrv.dll, fxsres.dll, fxstiff.dll, fxsui.dll and fxswzrd.dll. If you
> have
> clients which share this fax modem, you need also replace the files
> located
> in C:\WINDOWS\system32\clients\faxclient\drivers.
>
> NOTE: The replacement should be perform in safe mode, and only register
> the

[Nick]

Hello again Inn Jin,

Something else I have just noticed in C:\WINDOWS\system32\dllcache there is
a whole series of files FXS_fxs*.* is that normal, are they supposed to be
there?

Nick

""Inn Jin [MSFT]"" <v-in...@online.microsoft.com> wrote in message

news:tjYt4b9O...@TK2MSFTNGHUB02.phx.gbl...

> Hi Nick,
>
> Thank you for updating and thanks Greg's input.
>
> Sorry for the delay due to personal affair.
>
> The file related to the fax drive is located in
> C:\windows\system32\spool\drivers\w32x86\3. And the files are fxsapi.dll,
> fxsdrv.dll, fxsres.dll, fxstiff.dll, fxsui.dll and fxswzrd.dll. If you
> have
> clients which share this fax modem, you need also replace the files
> located
> in C:\WINDOWS\system32\clients\faxclient\drivers.
>
> NOTE: The replacement should be perform in safe mode, and only register
> the

[NickC]

Hi Inn Jin,

Well I am onsite at the moment and have restored these files from an old
tape backup. Unfortunately still got the same error:
fxs....dll was loaded but the DllRegisterServer entry point was not found.
This file can not be registered.

If I try to unregister it I get a similar error:
fxs....dll was loaded but the DllUnregisterServer entry point was not found.

Help :)

Nick

"Nick" <NoS...@Nowhere.com> wrote in message

news:%23cWbqbA...@TK2MSFTNGP06.phx.gbl...

[NickC]

Gregg,

Well I have now reinstalled Win2003 Service pack 1. I also found I needed
to reinstall SBS Service pack 1 along with various mofcomp.exe commands to
fix eventid: 9097. However all running with a clean event log again now.
Problem is faxes still don't work.

However we might be getting closer to identifying the problem with this
inability to reregister the fxs*.dll\ - see other branch of the thread. I
would be interested if anyone else can reregister these dlls without getting
the same error.

Nick

"Gregg Hill" <bo...@nowhere.com> wrote in message

news:ut5ceJ5O...@TK2MSFTNGP02.phx.gbl...

[Gregg Hill]

I have those files on my SBS 2003 RTM that has SP1 installed. They are all
dated 3/24/05.

Gregg Hill

"Nick" <NoS...@Nowhere.com> wrote in message

news:%237U2dlI...@TK2MSFTNGP04.phx.gbl...

[Gregg Hill]

Nick,

Have you re-installed the fax service according to Inn Jin's first reply,
and did you do it using the SP1 files?

What are your fax file version numbers now? They should be 5.2.2893.0.

Here is what I would do right now. Remove the modems and do it using Server
Management > Fax > Configure Phone and Modem Options. Then follow Inn Jin's
instructions to remove the fax service, reboot re-install it, making sure it
uses the SP1 setup files. An actual SP1 installation CD3 has 5/12/05 folder
dates and fax files with version 5.2.2893.0.

Something bugs me about your statement that "The FaxCfg.exe/.dll on the SBS

CD3 are version 5.2.2651 while the ones in our C:\Program Files\Microsoft
Windows Small Business Server\fax directory are version 5.2.2893. This

newer version must have come from somewhere...." This leads me to believe
that the CD you are using to run SFC and re-install the fax service is still
the RTM CD and not the SP1 CD.

Gregg Hill

"NickC" <NoOn...@BTInternet.com> wrote in message

news:%23N5YbaL...@TK2MSFTNGP06.phx.gbl...

[Nick]

Gregg, yep mine are the same date, thanks for checking those for me.

Nick

"Gregg Hill" <bo...@nowhere.com> wrote in message

news:uCRMLoOP...@TK2MSFTNGP04.phx.gbl...

[Nick]

Hi Gregg,

You are correct I am reinstalling from original RTM media (on hard disk
copy) I have no other option. I do not have slipstreamed SBS CDs and as far
as I know cannot obtain one; this is an OEM copy and here in the UK
Microsoft will not supply slipstreamed CDs for OEM licences. If anyone can
point me towards a copy of SBS CDs with SP1 slipstreamed which I can
download that would be most appreciated. Real email is
...@AssociatedData.co.uk, that is NickC at.

Yes all our fax files are ver. 5.2.2893, except the fxs*.dll files in
C:\Win\Sys32\Spool\Drivers\W32x86\3 which are version 5.2.3790.

I did follow Inn Jin's instructions to reinstall to the letter but will try
it again but removing the modems first this time. In the absence of
slipstreamed media the best I can think of is to extract the Win2003 SP1
files and the SBSSP1 files, then copy the original media to disk, copy
Win2003SP1 files over the top, then copy SBS2003 files over the top of that.
Then when I get asked for the SBS CD point to that directory. Recon that
might work?

Well here goes...

Nick

"Gregg Hill" <bo...@nowhere.com> wrote in message

news:%239U8L5O...@TK2MSFTNGP02.phx.gbl...

[Nick]

Ahh... found a problem.

Add/Remove Prigrams - Add/Remove Windows Components - Fax Service is not
installed! No error message but it just doesn't seem to install.
Retrieving C:\Windows\Faxsetup.log to look for errors, found this:
[01/21/07 16:47:28] [0x11e4] [ ] Installing Fax Service...

[01/21/07 16:47:28] [0x11e4] [ ] fxocSvc_Install (fax - Fax.CleanInstall)

[01/21/07 16:47:28] [0x11e4] [ ] {

[01/21/07 16:47:28] [0x11e4] [ERR] Failed to install the services section in
section 'Fax.CleanInstall', rc = 0x436

[01/21/07 16:47:28] [0x11e4] [ ] } (1078)

[01/21/07 16:47:28] [0x11e4] [ERR] Failed to install fax service. This is a
fatal error, abandoning fax install...rc=0x436

[01/21/07 16:47:28] [0x11e4] [ERR] Complete Fax Install failed, rc = 0x436

Any ideas?

Nick

"Nick" <NoS...@Nowhere.com> wrote in message

news:%23qQsgNX...@TK2MSFTNGP04.phx.gbl...

[Gregg Hill]

Nick,

You should be able to download or get CDs of a trial version of SBS 2003 R2,
which is just SBS 2003 SP1 with an R2 Technologies CD. The fax files are the
same.

Also, did you follow Inn Jin's remove/reinstall directions to the letter?

Here they are again.

Step Four
===================
Let's try to remove the fax component and reinstall it.

Let's first make sure we have the FAX component installed correctly by
performing a manual reinstallation for it:

1. Rename the keys and files below to *.old

1) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fax
2) HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Fax
3) C:\Program Files\Microsoft Windows Small Business Server\fax
4) The ''SBSMIS-FAX.log'' file under ''C:\Program Files\Microsoft
Integration\Windows Small Business Server 2003\Logs''.
5) The ''SBSMSI-faxcfg.log'' file under ''C:\Program Files\Microsoft
Integration\Windows Small Business Server 2003\Logs''.
6) The ''faxsetup.log'' file under ''C:\WINDOWS\''.

2. Access Add/Remove Programs, Add/Remove Windows Components, uncheck ''Fax
Services'' to uninstall it.

3. Once it is uninstalled, access Add/Remove Programs to reinstall it.

4. Then, access ''Add/Remove Programs again'', this time, we will click
''Change/Remove'' on the ''Windows Small Business Server 2003'' item:

1) Click ''Next'' on the ''Microsoft Windows Small Business Server Setup''
page.
2) Click ''Next'' on the ''Windows Configuration'' page.

Note: It states that ''This will take approximately 30 minutes'', it is
referring to the total time it will take in the first SBS component
installation. For the task such as remove a specific component, it will
just take couple of minutes.

3) Now, in the ''Component Selection'' page, choose ''Remove'' before the
''Fax Services'' item.
4) Click ''Next'', and then click ''Next'' again to confirm ''Component
Summary''. You will be prompted to insert the SBS 2K3 setup Disc 1.

5. Once the removal process is completed, access ''Windows Small Business
Server setup'' again in ''Add/Remove Programs'', proceed to the ''Component
Selection'' page, and then choose ''Install'' for the ''Fax Services'' item.

Please then check if the problem is resolved

"Nick" <NoS...@Nowhere.com> wrote in message

news:%23FqePOY...@TK2MSFTNGP03.phx.gbl...

[Inn Jin [MSFT]]

Hi Nick,

Thank you for updating and thanks Gregg's input.

Sorry for the delay due to the weekend, thanks for the understanding.

The error 0x436 means duplicate service name. So please follow the steps
below to install the Fax Services again.

After install the fax service, please try to register the .dll files again,
also please re-apply the SP1. for the CD problem you can refer to Gregg's
opinion or you can contact your OEM vendor for further assistance.

I appreciate your effort and time.

[Nick]

Ok Gregg will try to obtain a trial version but don't know if they are
available in the UK. Have just tried via the Microsoft Website but the
bloody thing wants a .Net Passport whatever that is! ... Just been through
an awfully tortuous sign-up process for a 'Windows Live'??? ID (during which
I had to use Firefox at a number of points because Internet explorer
wouldn't work with this Microsoft site) and now I find that SBS trial is not
in the list, I guess it is not available in the UK!

I can see no option but to continue using the install files I created on
disk as previously mentioned; 'copy the original media to disk, copy

Win2003SP1 files over the top, then copy SBS2003 files over the top of

that'.

Yes, I did follow Inn Jin's instructions _exactly_ to the letter but after:

> 3. Once it is uninstalled, access Add/Remove Programs to reinstall it.

I get a message saying that Fax Services has installed correctly, however I
find the check box for Fax Services if unchecked.

Will continue this in the other branch replying to Inn Jin so as to keep the
thread clean.

Nick

"Gregg Hill" <bo...@nowhere.com> wrote in message

news:%23nkywhZ...@TK2MSFTNGP04.phx.gbl...

[Nick]

Inn Jin,

I have followed your instructions _exactly_ to the letter but after:

> 3. Once it is uninstalled, access Add/Remove Programs to reinstall it.

I get a message saying that Fax Services has installed correctly, however I
find the check box for Fax Services if unchecked. When I then look in
C:\Windows\Faxsetup.log for errors, I find this:

[01/21/07 16:47:28] [0x11e4] [ ] Installing Fax Service...
[01/21/07 16:47:28] [0x11e4] [ ] fxocSvc_Install (fax - Fax.CleanInstall)
[01/21/07 16:47:28] [0x11e4] [ ] {
[01/21/07 16:47:28] [0x11e4] [ERR] Failed to install the services section in
section 'Fax.CleanInstall', rc = 0x436
[01/21/07 16:47:28] [0x11e4] [ ] } (1078)
[01/21/07 16:47:28] [0x11e4] [ERR] Failed to install fax service. This is a
fatal error, abandoning fax install...rc=0x436
[01/21/07 16:47:28] [0x11e4] [ERR] Complete Fax Install failed, rc = 0x436

I am beginning to wish that I have never uninstalled the Win2003 Fax
Services component because it does not seem to want to reinstall.

Other unresolved items that might help:
1). Why did the T30 logging not work, is there anything else we can do to
make this work in the hope that it might shed some light on the cause of the
problem.
2). Where exactly are the driver files for the fax modems, can I copy these
back from a previous backup? Remember this setup worked fine for 18 mths
until I ran SFC.exe so if I can restore the relevent file to that time
surely everything should start working again, shouldn't it?

Nick

""Inn Jin [MSFT]"" <v-in...@online.microsoft.com> wrote in message

news:iXPv1DiP...@TK2MSFTNGHUB02.phx.gbl...

[Inn Jin [MSFT]]

Hi Nick,

Thank you for updating.

One thing I want to say, as our hardware drives will change with the change
of the industry standard, it is not support to use the hardware out of the
HCL list. I strongly suggest you to contact your hardware vendor for
further troubleshooting.

After a long time further research, 0x436 occurs because SCM (Service
Control Manager) remembers the image path keys etc and hence accesses the
renamed key.

Let's try the follow steps be re-install it:

1. Delete the file from the %temp% directory.

2. Export and then delete the keys and files below to *.old:

1) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fax

2) HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Fax

3) C:\Program Files\Microsoft Windows Small Business Server\fax

4) The "SBSMIS-FAX.log"file under "C:\Program Files\Microsoft
Integration\Windows Small Business Server 2003\Logs".

5) The "SBSMSI-faxcfg.log"file under "C:\Program Files\Microsoft
Integration\Windows Small Business Server 2003\Logs".

6) The "faxsetup.log"file under "C:\WINDOWS\".

3. Delete the registry keys that were previously renamed to *.old:

1) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fax.old

2) HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Fax.old

3) C:\Program Files\Microsoft Windows Small Business Server\fax.old

4. Access Add/Remove Programs, Add/Remove Windows Components, uncheck "Fax
Services" to uninstall it.

5. Once it is uninstalled, access Add/Remove Programs to reinstall it.

6. Then, access "Add/Remove Programs again", this time, we will click

"Change/Remove" on the "Windows Small Business Server 2003" item:

1) Click "Next" on the "Microsoft Windows Small Business Server Setup"
page.

2) Click "Next" on the "Windows Configuration" page.

Note: It states that "This will take approximately 30 minutes", it is
referring to the total time it will take in the first SBS component
installation. For the task such as remove a specific component, it will
just take couple of minutes.

3) Now, in the "Component Selection" page, choose "Remove" before the "Fax
Services" item.

4) Click "Next", and then click "Next" again to confirm "Component
Summary". You will be prompted to insert the SBS 2K3 setup Disc 1.

7. Once the removal process is completed, access "Windows Small Business

Server setup" again in "Add/Remove Programs", proceed to the "Component
Selection" page, and then choose "Install" for the "Fax Services" item.

Then please try re-apply SP1 then test the issue. For your two questions:

1) Why did the T30 logging not work, is there anything else we can do to

make this work in the hope that it might shed some light on the cause of
the problem.

I'm not sure why T30 logging not work, some unknown errors may happen.
However, you don't have to collect T30 log, as the previous log you send to
me which locate in C:\Windows\System32\LogFiles\Fax folder is just as same
as T30 log. The T30 log contains some deeply error code which you can not
seen in other log, it can helps developer to track the connection and
isolate issue.

2). Where exactly are the driver files for the fax modems, can I copy these
back from a previous backup? Remember this setup worked fine for 18 mths

until I ran SFC.exe so if I can restore the relevant file to that time

surely everything should start working again, shouldn't it?

The fax driver files are fxsapi.dll, fxsdrv.dll, fxsres.dll, fxstiff.dll,
fxsui.dll and fxswzrd.dll. You can copy them back, but you may need to
register them.

Thank you for understanding and cooperating.

[Nick]

Hello Inn Jin, thank you for your reply. I have tried the steps you suggest
but find that Fax Service component will still not install!

However, I have now found an alternative way of getting it reinstalled. It
appears to be a SP1 issue whereby after installing SP1 the SBS fax component
will not reinstall, AFAIK due to a problem with the later Microsoft
Installer, the solution I used was

Delete the following from \winnt\system32:
msi.dll
msihnd.dll
msiexec.exe
Reboot
Install InstMSIw.exe - from Original (pre SP1) SBS2003 CD1 \I386\ADMT\PWDMIG

Try to install Win2003 Fax component again... Eureka! Installed no error.

___WARNING___ to anyone watching this thread, DO NOT uninstall the Windows
Fax Component in the hope of reinstalling it if you have service pack 1
installed. This has cost me virtually two weeks solid and I still haven't
got any closer to the real cause of the Unknown fatal Error 0x0000000C.

Will reply as seperate branch of the thread regarding ongoing problems.

Best regards,
Nick

""Inn Jin [MSFT]"" <v-in...@online.microsoft.com> wrote in message

news:$gMvo%237PHH...@TK2MSFTNGHUB02.phx.gbl...

[Nick]

Hello Inn Jin,

Seperate message regarding ongoing "Unknown fatal Error" "0x0000000C",
eventId: 32092.

""Inn Jin [MSFT]"" <v-in...@online.microsoft.com> wrote in message

news:$gMvo%237PHH...@TK2MSFTNGHUB02.phx.gbl...

> One thing I want to say, as our hardware drives will change with the
> change
> of the industry standard, it is not support to use the hardware out of the
> HCL list. I strongly suggest you to contact your hardware vendor for
> further troubleshooting.

Inn Jin, I do not understand what you are saying here. The ITU fax
standards (V.27, V.29, V.17, V.34) have not changed since 1994 they are
written in stone. What is this change of industry standard that you keep
refering to?

With regard to the hardware vendor, that is me! Thank you for your
suggestion but this issue is not hardware related.

Further to your suggestion I have now tried a completely different modem and
that suffers from exactly the same error. This replacement modem is usually
in daily use on another site sending and receiving faxes all day without a
problem. It installed using the Microsoft certified driver which ship with
SBS, so again no external drivers are involved.

I have also done some digging regarding the driver file and it appears that
our original modem is using the MdmWHQL0.inf file which came with SBS, this
is a Microsoft signed driver file. The WHQl part of the name I suggest
means Windows Hardware QuaLified! No external drivers involved purely
Microsoft Certified drivers only.

> The fax driver files are fxsapi.dll, fxsdrv.dll, fxsres.dll, fxstiff.dll,
> fxsui.dll and fxswzrd.dll. You can copy them back, but you may need to
> register them.

I still get the error: 'FXS. was loaded, but the DLLRegisterServer entry
point was not found. This file can not be registered' when I try to
register any of these dlls. I have also tried this on another Win2003
machine and get the same error. Are you sure that these files should
register in this way? Could you (or someone else who is watching this
thread) try to see if they register correctly on your server. Is there a
different way that these should be registered?

It is possible that solving the reregistering issue might be these

Searching the Internet I find a number of others have had this "Unknown
fatal Error" "0x0000000C" problem but never solved. Has anyone ever found a
solution to this MSFax bug?

Nick

""Inn Jin [MSFT]"" <v-in...@online.microsoft.com> wrote in message

news:$gMvo%237PHH...@TK2MSFTNGHUB02.phx.gbl...

[Nick]

"Nick" <NoS...@Nowhere.com> wrote in message news:...

[Gregg Hill]

Nick,

Just to throw another wrench into your mix, I must tell you that I have a
server installed with the RTM version of SBS 2003, i.e., the original
release. I updated to SP1 quite a while ago. In November, I removed the fax
service because I thought it was my problem in getting a new modem
recognized by the fax service. I re-installed the fax service with NO
PROBLEM, so you have something else going on that caused that problem.

When you installed your modem after re-installing the fax service, did you
just let Windows recognize it, or did you install it using the Fax wizard? I
could not get my modem to work if I just let Windows recognize it when it
was first connected. I had to go through Server Management > Fax > Configure
Phone and Modem Options to remove it and reinstall it, then re-ran the
Configure Fax Services wizard.

Can you re-register wizchain.dll in the C:\Program Files\Windows for Small
Business Server\Administration folder?

Just a thought.

Gregg Hill

"Nick" <NoS...@Nowhere.com> wrote in message

news:%2326RV0H...@TK2MSFTNGP05.phx.gbl...

[Nick]

Hi Gregg thanks for your continuing suggestions,

"Gregg Hill" <bo...@nowhere.com> wrote in message

news:eAGfx6JQ...@TK2MSFTNGP03.phx.gbl...

> Just to throw another wrench into your mix, I must tell you that I have a
> server installed with the RTM version of SBS 2003, i.e., the original
> release. I updated to SP1 quite a while ago. In November, I removed the
> fax service because I thought it was my problem in getting a new modem
> recognized by the fax service. I re-installed the fax service with NO
> PROBLEM, so you have something else going on that caused that problem.

Well I picked-up the info about the windows installer from the internet
somewhere and it seemed to work for me. Maybe it will not work for
everybody, perhaps Inn Jin's suggestion (>>> 1. Delete the file from the
%temp% directory. - which file? I deleted all of them.) will work for
others. At least my experiences are here in the archive in case they help
someone else.

> When you installed your modem after re-installing the fax service, did you
> just let Windows recognize it, or did you install it using the Fax wizard?
> I could not get my modem to work if I just let Windows recognize it when
> it was first connected. I had to go through Server Management > Fax >
> Configure Phone and Modem Options to remove it and reinstall it, then
> re-ran the Configure Fax Services wizard.

Can't say I actually removed them from this wizard but have certainly
removed then from device manager many times. Will remove it using this
wizard and re-run the Fax Services wizard... Just done that but fax wizard
will not run now, fax service will not restart either, will reboot later
when all the users are off and let you know tomorrow if that has worked.

> Can you re-register wizchain.dll in the C:\Program Files\Windows for Small
> Business Server\Administration folder?

Yep, wizchain.dll registers fine.

Nick

> Nick,

[Inn Jin [MSFT]]

Hi Nick,

Thank you for upgrading,

I'm glad that you found your own solution, also thank you for sharing you
information. Please notice that as your fax modem is not in our HCL list,
we cannot guarantee that it will work perfectly, besides it is out of
support boundary. I suggest you contact your hardware vendor for further
troubleshooting. Thank you for your understanding and cooperating.

[Gregg Hill]

Nick,

I had a client with those errors and others. I was fighting with their
problem at the same time you were posting (I posted six days earlier). I
have finished my testing.

At first, one of the employees told me they had no problems with their
manual fax machine receiving, but claimed that the problems started only
after the new SBS 2003 R2 server was installed and faxing was switched to
it. It had a USR Courier V.Everything 3CP3453 external modem on it. After
several weeks of trying various things, including modems on the HCL, I
contacted Cantata (formerly Brooktrout) and got a loaner TruFax 200 with
which to test faxing. During testing with that loaner Brooktrout card on my
own server, the owner's wife told me they have a horrible fax line that
doesn't even work when it rains. What were the results? See the following.

Please see this thread "Brooktrout TruFax card questions" for
recommendations on what device to use.

In particular, the results of extensive testing are posted on Thursday,
January 11, 2007 10:37 PM and on Monday, January 15, 2007 6:05 PM.

Also, the following is from a response to another post with subject "Fex
help!! (please!!)" from Thursday, January 18, 2007 9:00 AM.

********************************************************
Something may very well have changed with a Microsoft Update, because I
could fax outbound from my USR Courier external several months ago (around
October) but could not reliably fax out any more until I installed the
Brooktrout card.

They have two cards specifically for Microsoft Shared Fax, and they are
certified by GFi to work with FAXmaker if you need more ponies. They are the
TruFax and the TR1034 boards noted here:
http://www.cantata.com/products/shared_fax/.

If you want the cheaper of the two, it is the TruFax board. Click on this
link http://www.cantata.com/products/part_no._guide/index.cfm for part
numbers, then click on one of the two choices below. Note that the web page
is misleading when it states that a board is "for Europe only" or "for
non-Europe countries only." The "Europe only" boards just mean that they are
RoHS-compliant. The same board can be used in the USA. The webmaster has
been informed but has not changed it yet.

TR1034 for Microsoft Shared Fax RoHS
TruFax for Microsoft Shared Fax RoHS (for Europe only)

The most current part numbers for the TruFax series all start with 999-169,
so just figure out how many ports you want and use the corresponding number.
CALL THEM to make sure you get the right board, since the UK appears to have
slight differences.

GFi FAXmaker http://www.gfi.com/faxmaker/ and supported Brooktrout cards
http://kbase.gfi.com/showarticle.asp?id=KBID001227.

*********************************************************

Also, see "Best fax modem settings to receive from multifunction devices?"
dated Monday, December 18, 2006 11:03 AM.

Did you ever run the hotfix I mentioned here
http://support.microsoft.com/kb/919009/en-us?

My "final answer" to my client...use a Brooktrout TruFax card (or the TR1034
at four times the price). They previously had about an 80% receive failure
rate with their USR modem (and the others I tried). With the TruFax card,
they have had 100% success rate for two weeks, both sending and receiving. I
ordered them their own TruFax 100 Card yesterday. Cantata is letting me keep
the loaner TruFax 200 card that I used for testing.

I, too, could fax fine with my USR Courier V.Everything external modem for a
few months prior to November or December, then outbound crapped out on me. I
could not receive from anyone with a Brother MFC device. Testing with the
Brooktrout card showed 100% success receiving.

Gregg Hill

"Nick" <NoS...@Nowhere.com> wrote in message

news:eN152PIQ...@TK2MSFTNGP02.phx.gbl...

[Nick]

"Gregg Hill" <bo...@nowhere.com> wrote in message

news:O8Zt0$WQHHA...@TK2MSFTNGP05.phx.gbl...

>
> Did you ever run the hotfix I mentioned here
> http://support.microsoft.com/kb/919009/en-us?
>

Hi Gregg,

No didn't run the hotfix because I could not find out how to obtain it. It
looked like Microsoft will only release if you pay them for a support
incident, is that correct? We have had problems before where M$ insist on
taking a credit card number becare they will even talk to us, then when we
finally prove the problem was a Microsoft bug all along they still charge us
and refuse to refund that charge. Is there any way of obtaining this fix
without paying a Microsoft tax!

Nick

[Nick]

Inn Jin,

Sorry but you seem to have missunderstood; I have not solved the problem
only part of it. I have now managed to reinstall Windows Fax Service but I
am still unable to send or receive any faxes due the the ongoing "Unknown
fatal Error" "0x0000000C" problem.

I am still unable to register any of the FXS*.dll files as you suggest I
should be able to do. due to the error:

'FXS. was loaded, but the DLLRegisterServer entry point was not found.
This file can not be registered'

Have you tried to see if you can register these on your server?

The T30 log is still not being written, why not. Surely you are not going
to tell me that that is due to the modem hardware as well!!

> I suggest you contact your hardware vendor for further troubleshooting

Did you read my previous message? I am the hardware vendor!!

Best regards,
Nick

""Inn Jin [MSFT]"" <v-in...@online.microsoft.com> wrote in message

news:pN2ScUVQ...@TK2MSFTNGHUB02.phx.gbl...

[Gregg Hill]

Call them and push the buttons to get to the hotfix queue. There is no
charge for hotfixes.

800-936-4900 in the USA.

Gregg Hill

"Nick" <NoS...@Nowhere.com> wrote in message

news:%23KmUQeY...@TK2MSFTNGP05.phx.gbl...

[Nick]

Thanks for reminding me about this fix Gregg, I will call them on Monday and
get this hotfix.

Nick

"Gregg Hill" <bo...@nowhere.com> wrote in message

news:OHFPfkcQ...@TK2MSFTNGP05.phx.gbl...

[Gregg Hill]

I tried to register my fxs files and some succeeded, some failed. I did not
write down the specifics. The point is that my fax service works in spite of
not being able to register them.

Have you had the phone company check your lines?

Gregg Hill

"Nick" <NoS...@Nowhere.com> wrote in message

news:e11p56g...@TK2MSFTNGP02.phx.gbl...

[Nick]

Not had the lines checked but standalone fax machines send and receive fine
on the same lines so don't think there is anything wrong with them.

"Gregg Hill" <bo...@nowhere.com> wrote in message

news:um7GMKlQ...@TK2MSFTNGP04.phx.gbl...

[Gregg Hill]

You haven't read my other threads I mentioned, have you? Stand-alone fax vs.
modem is a whole different ball game.

Gregg Hill

"Nick" <NoS...@Nowhere.com> wrote in message

news:ez1$FJtQH...@TK2MSFTNGP02.phx.gbl...

[Robert Li [MSFT]]

Hi Nick,

Thanks for updating.

This is Robert Li, Inn Jin is temporarily out of the Newsgroups and I am
his backup.

From previous posts, I noticed that your modem is not in the HCL List, We
don’t provide support of this kind hardware according to our newsgroup
policy. Thanks for understanding. I would suggest you replace this modem
with one that is in the HCL list. If the problem even could be reproduced,
I am very glad to help on it.

Thank you again.

Best Regards,

Robert Li

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

====================================================

PLEASE NOTE: The partner managed newsgroups are provided to
assist with break/fix issues and simple how to questions.
We also love to hear your product feedback! Let us know what you think by
posting
from the web interface: Partner Feedback
from your newsreader: microsoft.private.directaccess.partnerfeedback.

We look forward to hearing from you!

====================================================

When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from this issue.

====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

====================================================

--------------------
<Reply-To: "Gregg Hill" <bo...@nowhere.com>
<From: "Gregg Hill" <bo...@nowhere.com>
<References: <#1AqSB0M...@TK2MSFTNGP04.phx.gbl>
<uSznWhJO...@TK2MSFTNGP03.phx.gbl>
<ul$PBoKOH...@TK2MSFTNGHUB02.phx.gbl>
<#qhjMOWO...@TK2MSFTNGP04.phx.gbl>
<u6pAHvdO...@TK2MSFTNGP02.phx.gbl>
<#8ncUmmO...@TK2MSFTNGP04.phx.gbl>
<OUgj8AqO...@TK2MSFTNGP04.phx.gbl>
<OgIu1jzO...@TK2MSFTNGP02.phx.gbl>
<ut5ceJ5O...@TK2MSFTNGP02.phx.gbl>
<#N5YbaLP...@TK2MSFTNGP06.phx.gbl>
<#9U8L5OP...@TK2MSFTNGP02.phx.gbl>
<#qQsgNXP...@TK2MSFTNGP04.phx.gbl>
<#FqePOYP...@TK2MSFTNGP03.phx.gbl>
<#nkywhZP...@TK2MSFTNGP04.phx.gbl>
<iXPv1DiP...@TK2MSFTNGHUB02.phx.gbl>
<O55UBQjP...@TK2MSFTNGP03.phx.gbl>
<$gMvo#7PHHA...@TK2MSFTNGHUB02.phx.gbl>
<eN152PIQ...@TK2MSFTNGP02.phx.gbl>
<O8Zt0$WQHHA...@TK2MSFTNGP05.phx.gbl>
<#KmUQeYQ...@TK2MSFTNGP05.phx.gbl>
<OHFPfkcQ...@TK2MSFTNGP05.phx.gbl>
<e11p56g...@TK2MSFTNGP02.phx.gbl>
<um7GMKlQ...@TK2MSFTNGP04.phx.gbl>
<ez1$FJtQH...@TK2MSFTNGP02.phx.gbl>
<Subject: Re: Received fax errors after running SFC.exe
<Date: Sun, 28 Jan 2007 10:57:05 -0800
<Lines: 74
<X-Priority: 3
<X-MSMail-Priority: Normal
<X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
<X-RFC2646: Format=Flowed; Response
<Message-ID: <urW$a4wQHH...@TK2MSFTNGP04.phx.gbl>
<Newsgroups: microsoft.public.windows.server.sbs
<NNTP-Posting-Host: rrcs-24-199-41-114.west.biz.rr.com 24.199.41.114
<Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
<Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:13326
<X-Tomcat-NG: microsoft.public.windows.server.sbs

[Nick]

> From previous posts, I noticed that your modem is not in the HCL List, We
> don’t provide support of this kind hardware according to our newsgroup
> policy

Robert, have you read any of the previous posts? This issue is not hardware
related! It is related to running sfc.exe. The USRobotics Courier External
is probably the most popular and most used business class fax modem in the
world.

How can you possibly claim that this modem is not compatible with SBS2003?
It is listed in the Microsoft supplied MdmWHQL0.inf file which shipped with
SBS, this
is a Microsoft certified driver file(WHQL=Windows Hardware QuaLified!). No
external drivers are involved only Microsoft Certified drivers.

> If the problem even could be reproduced, I am very glad to help on it.

The problem can be reproduced, all the time. This is not an intermittant
problem ALL faxes both incoming and outgoing fail all of the time.

Regards,
Nick

"Robert Li [MSFT]" <v-ro...@online.microsoft.com> wrote in message
news:rL0n8W6...@TK2MSFTNGHUB02.phx.gbl...

[Nick]

Hi Gregg,

Well I tried to obtain the hotfix but without sucess, Microsoft here in the
UK are quite different to Microsoft in the US. Microsoft UK will not even
accept an email from me requesting this hotfix unless I pay them £70! Sorry
but this is a stich-up £70 just to read one email requesting something that
users in other countries can get for free.

If anyone out there has access to hotfix 919009 I would very much appreciate
a copy (even though it may still not solve the problem). My personal email
is xxx at AssociatedData.co.uk where xxx is NickC.

"Gregg Hill" <bo...@nowhere.com> wrote in message

news:urW$a4wQHH...@TK2MSFTNGP04.phx.gbl...

> You haven't read my other threads I mentioned, have you? Stand-alone fax
> vs. modem is a whole different ball game.

Well I have to admit that that the time I hadn't read them. They had
dropp[ed off the bottom of my Outlook Express and I couldn't find them in
google groups, sorry :(. I have now found an online archive of all these
newsgroup posts and am pleased to say have read your previous posts fully.
Very informative, thanks. In our case these USR Couriers had been getting
better transmition rates than the standalone machines, that was until this
total failure to send or receive anything.

I realise that you favour a Brooktrout fax board as the prefered solution
but in our case that is simply not an option, there is no accesible PCI slot
available on this server.

All the best,
Nick

"Nick" <NoS...@Nowhere.com> wrote in message

news:e11p56g...@TK2MSFTNGP02.phx.gbl...

[Nick]

Something else to add to the clues is a log of modem communications during a
failed send. This is a mixture of the outgoing and incoming logs mixed
togethrt on the same timeline. Does this give any clues as to why this
fails?

Nick

**** Start Fax modem communication log ****

Sending modem:
[11:29:30][139929265][ 130173][ ] Modem initialization
[11:29:30][139929312][ 131580][ ] send:
"AT&FS0=0E0V1Q0"
[11:29:31][139929562][ 131688][ ] recv: "OK"
[11:29:31][139929609][ 131580][ ] send: "AT"
[11:29:31][139929843][ 131688][ ] recv: "OK"
[11:29:31][139929890][ 131580][ ] send:
"ATB0X4&D2&C1&H1&R2&I0&A3&M4&B1S7=255"
[11:29:31][139930125][ 131688][ ] recv: "OK"
[11:29:31][139930171][ 131580][ ] send: "ATM1L0"
[11:29:31][139930421][ 131688][ ] recv: "OK"
[11:29:31][139930421][ 330104][ ] Phase A - Call establishment
[11:29:31][139930421][ 330117][ ] Dialing...
[11:29:31][139930531][ 130698][ ] send:
"AT+FCLASS=1"
[11:29:32][139931078][ 131580][ ] send: "AT"
[11:29:32][139931312][ 131688][ ] recv: "OK"
[11:29:32][139931515][ 130872][ ] send: "ATDT
#######"

Receiveing modem:
[11:29:38][139937546][ 130173][ ] Modem initialization
[11:29:39][139937593][ 131580][ ] send:
"AT&FS0=0E0V1Q0"
[11:29:39][139937843][ 131688][ ] recv:
"AT&FS0=0E0V1Q0"
[11:29:39][139937843][ 131688][ ] recv: "OK"
[11:29:39][139937890][ 131580][ ] send: "AT"
[11:29:39][139938125][ 131688][ ] recv: "OK"
[11:29:39][139938171][ 131580][ ] send:
"ATB0X4&D2&C1&H2&I2&R1&A3&M4&B1"
[11:29:39][139938406][ 131688][ ] recv: "OK"
[11:29:39][139938453][ 131580][ ] send: "ATM1L0"
[11:29:40][139938687][ 131688][ ] recv: "OK"
[11:29:40][139938687][ 330019][ ] Phase A - Call establishment
[11:29:40][139938687][ 330030][ ] Answering...
[11:29:40][139938796][ 130698][ ] send:
"AT+FCLASS=1"
[11:29:40][139939343][ 131580][ ] send: "AT"
[11:29:41][139939578][ 131688][ ] recv: "OK"
[11:29:41][139939687][ 130698][ ] send:
"AT+FCLASS=1"
[11:29:41][139940234][ 131580][ ] send: "AT"
[11:29:41][139940468][ 131688][ ] recv: "OK"
[11:29:42][139940671][ 131283][ ] send: "ATA"
[11:29:47][139945984][ 131688][ ] recv: "CONNECT"
[11:29:47][139945984][ 131306][ ] Response - CONNECT
[11:29:47][139945984][ 310227][ ] Phase B - Negotiation
[11:29:47][139945984][ 300036][ ] CSI is "Company Name."
[11:29:47][139945984][ 370475][ ] Composing DIS with the
following capabilities:
[11:29:47][139945984][ 380039][ ] - Supported Modulations:
V.27 ter, V.29, V.33, V.17
[11:29:47][139945984][ 380040][ ] - Ability to use fine
resolution: Yes
[11:29:47][139945984][ 380041][ ] - Ability to use 2D coding:
Yes
[11:29:47][139945984][ 380042][ ] - Supported Page Width:
1728
[11:29:47][139945984][ 380043][ ] - Supported Page Length:
Unlimited
[11:29:47][139945984][ 380044][ ] - Minimum scan line time: 0
[11:29:47][139945984][ 310930][ ] Sending CSI-DIS
[11:29:47][139946046][ 200267][ ] send: CSI, 23
bytes, ff 03 40 20 2e 74 6e 49 20 76 65 4e 20 26 20 73 74 74 69 4b 20 74 53
[11:29:47][139946046][ 50408][ ] send:
<dle><etx>

Sending modem:
[11:29:48][139947187][ 131688][ ] recv: "CONNECT"
[11:29:48][139947187][ 131078][ ] Response - CONNECT
[11:29:48][139947187][ 310214][ ] Phase B - Negotiation

Receiveing modem:
[11:29:49][139947734][ 131688][ ] recv: "CONNECT"
[11:29:49][139947734][ 200267][ ] send: DIS, 6
bytes, ff 13 80 00 ee 78
[11:29:49][139947734][ 50408][ ] send:
<dle><etx>

Sending modem:
[11:29:49][139947859][ 50750][ ] recv: HDLC
frame, 29 bytes, ff 03 40 20 2e 74 6e 49 20 76 65 4e 20 26 20 73 74 74 69 4b
20 74 53 25 be 10 03 0d 0a
[11:29:49][139947859][ 131688][ ] recv: "OK"
[11:29:49][139947859][ 312046][ ] frame is CSI,
non-final frame
[11:29:49][139947859][ 131580][ ] send:
"AT+FRH=3"
[11:29:49][139948343][ 131688][ ] recv: "CONNECT"

Receiveing modem:
[11:29:49][139948437][ 131688][ ] recv: "OK"
[11:29:49][139948437][ 310938][ ] Successfully sent CSI-DIS -
receiving response
[11:29:49][139948437][ 131580][ ] send:
"AT+FRH=3"

Sending modem:
[11:29:50][139948593][ 50750][ ] recv: HDLC
frame, 12 bytes, ff 13 80 00 ee 78 01 02 10 03 0d 0a
[11:29:50][139948593][ 131688][ ] recv: "OK"
[11:29:50][139948593][ 312046][ ] frame is DIS,
final frame
[11:29:50][139948593][ 370155][ ] CSI is "Company Name."
[11:29:50][139948593][ 370256][ ] DIS specified the following
capabilities:
[11:29:50][139948593][ 380039][ ] - Supported Modulations:
V.27 ter, V.29, V.33, V.17
[11:29:50][139948593][ 380040][ ] - Ability to use fine
resolution: Yes
[11:29:50][139948593][ 380041][ ] - Ability to use 2D coding:
Yes
[11:29:50][139948593][ 380042][ ] - Supported Page Width:
1728
[11:29:50][139948593][ 380043][ ] - Supported Page Length:
Unlimited
[11:29:50][139948593][ 380044][ ] - Minimum scan line time: 0
[11:29:50][139948593][ 300116][ ] TSI is "Company Name."
[11:29:50][139948593][ 300159][ ] DCS Composed as follows:
[11:29:50][139948593][ 380065][ ] - Session Modulation is:
14400 bps V.17
[11:29:50][139948593][ 380066][ ] - Use fine resolution: Yes
[11:29:50][139948593][ 380067][ ] - Use 2D coding: Yes
[11:29:50][139948593][ 380068][ ] - Page width is 1728
[11:29:50][139948593][ 380069][ ] - Page length is A4
[11:29:50][139948593][ 380070][ ] - Scan line time: 0
[11:29:50][139948593][ 310522][ ] Sending TSI-DCS
[11:29:50][139948656][ 131580][ ] send:
"AT+FTH=3"
[11:29:50][139948828][ 131688][ ] recv: "CONNECT"
[11:29:50][139948828][ 200267][ ] send: TSI, 23
bytes, ff 03 43 20 2e 74 6e 49 20 76 65 4e 20 26 20 73 74 74 69 4b 20 74 53
[11:29:50][139948828][ 50408][ ] send:
<dle><etx>
[11:29:52][139950578][ 131688][ ] recv: "CONNECT"
[11:29:52][139950578][ 200267][ ] send: DCS, 6
bytes, ff 13 83 00 e2 70
[11:29:52][139950578][ 50408][ ] send:
<dle><etx>

Receiveing modem:
[11:29:52][139950687][ 131688][ ] recv: "CONNECT"
[11:29:52][139950687][ 50750][ ] recv: HDLC
frame, 29 bytes, ff 03 43 20 2e 74 6e 49 20 76 65 4e 20 26 20 73 74 74 69 4b
20 74 53 91 e7 10 03 0d 0a
[11:29:52][139950687][ 131688][ ] recv: "OK"
[11:29:52][139950687][ 312046][ ] frame is TSI,
non-final frame
[11:29:52][139950687][ 131580][ ] send:
"AT+FRH=3"

Sending modem:
[11:29:52][139951281][ 131688][ ] recv: "OK"
[11:29:52][139951281][ 310567][ ] Sending TCF...
[11:29:52][139951281][ 131580][ ] send:
"AT+FTM=145"

Receiveing modem:
[11:29:52][139951390][ 131688][ ] recv: "CONNECT"
[11:29:52][139951390][ 50750][ ] recv: HDLC
frame, 12 bytes, ff 13 83 00 e2 70 24 02 10 03 0d 0a
[11:29:52][139951390][ 131688][ ] recv: "OK"
[11:29:52][139951390][ 312046][ ] frame is DCS,
final frame
[11:29:52][139951390][ 311215][ ] Receiving TCF...
[11:29:52][139951390][ 131580][ ] send:
"AT+FRM=145"

Sending modem:
[11:29:54][139952781][ 131688][ ] recv: "CONNECT"
[11:29:54][139952781][ 50202][ ] send: 1350
zeroes
[11:29:54][139952781][ 200300][ ] send: 1350
zeroes
[11:29:54][139952812][ 50354][ ] send:
<dle><etx>

Receiveing modem:
[11:29:54][139953078][ 131688][ ] recv: "CONNECT"

Sending modem:
[11:29:55][139954406][ 131688][ ] recv: "OK"
[11:29:55][139954406][ 310576][ ] Successfully sent TCF
[11:29:55][139954406][ 131580][ ] send:
"AT+FRH=3"

Receiveing modem:
[11:29:56][139954609][ 200588][ ] recv: TCF:
0 errors in 1080 signifact bytes of 3006 total bytes
[11:29:56][139954609][ 370155][ ] TSI is "Company Name."
[11:29:56][139954609][ 370176][ ] Received DCS is as follows:
[11:29:56][139954609][ 380065][ ] - Session Modulation is:
14400 bps V.17
[11:29:56][139954609][ 380066][ ] - Use fine resolution: Yes
[11:29:56][139954609][ 380067][ ] - Use 2D coding: Yes
[11:29:56][139954609][ 380068][ ] - Page width is 1728
[11:29:56][139954609][ 380069][ ] - Page length is A4
[11:29:56][139954609][ 380070][ ] - Scan line time: 0
[11:29:56][139954609][ 311284][ ] Received good TCF - sending
CFR
[11:29:56][139954609][ 131580][ ] send:
"AT+FTH=3"
[11:29:56][139954796][ 131688][ ] recv: "CONNECT"
[11:29:56][139954796][ 200210][ ] send: CFR, 3
bytes, ff 13 84
[11:29:56][139954796][ 50408][ ] send:
<dle><etx>

Sending modem:
[11:29:57][139955984][ 131688][ ] recv: "CONNECT"

Receiveing modem:
[11:29:57][139956015][ 131688][ ] recv: "OK"
[11:29:57][139956015][ 311292][ ] Successfully sent CFR
[11:29:57][139956015][ 311337][ ] Phase C - Receive page
[11:29:57][139956015][ 131580][ ] send:
"AT+FRM=146"

Sending modem:
[11:29:57][139956234][ 50750][ ] recv: HDLC
frame, 9 bytes, ff 13 84 ea 7d 10 03 0d 0a
[11:29:57][139956234][ 131688][ ] recv: "OK"
[11:29:57][139956234][ 312046][ ] frame is CFR,
final frame
[11:29:57][139956234][ 310626][ ] Received CFR
[11:29:57][139956234][ 310667][ ] Phase C - Page transmission
[11:29:57][139956281][ 131580][ ] send: "AT"
[11:29:57][139956515][ 131688][ ] recv: "OK"
[11:29:58][139956578][ 131580][ ] send:
"AT+FTH=3"
[11:29:58][139956750][ 131688][ ] recv: "CONNECT"
[11:29:58][139956750][ 200210][ ] send: DCN, 3
bytes, ff 13 fb
[11:29:58][139956750][ 50408][ ] send:
<dle><etx>
[11:29:59][139957968][ 131688][ ] recv: "OK"
[11:29:59][139957968][ 130804][ ] Hanging up
[11:29:59][139958015][ 131580][ ] send: "ATH0"
[11:29:59][139958453][ 131688][ ] recv: "OK"
[11:29:59][139958500][ 131580][ ] send: "ATH0"
[11:30:00][139958734][ 131688][ ] recv: "OK"

Receiveing modem:
[11:30:00][139958812][ 131688][ ] recv: "NO
CARRIER"

Sending modem:
[11:30:00][139958843][ 130698][ ] send:
"AT+FCLASS=0"

Receiveing modem:
[11:30:00][139959015][ 131580][ ] send:
"AT+FRM=146"

Sending modem:
[11:30:00][139959390][ 131580][ ] send: "AT"
[11:30:01][139959625][ 131688][ ] recv: "OK"
[11:30:01][139959671][ 131580][ ] send: "AT"
[11:30:01][139959906][ 131688][ ] recv: "OK"
[11:30:02][139961140][ 321878][ERR] Failed send

Receiveing modem:
[11:30:02][139961218][ 131732][WRN] failed to
receive expected response: CONNECT, +FCERROR, NO CARRIER
[11:30:02][139961218][ 131739][ ] send: "AT"
[11:30:02][139961296][ 131754][ ] recv: "OK"
[11:30:02][139961296][ 311419][WRN] Failed to receive page 1 -
receiving commands
[11:30:02][139961296][ 131580][ ] send:
"AT+FRH=3"
[11:30:08][139967296][ 131732][WRN] failed to
receive expected response: CONNECT, +FCERROR, NO CARRIER
[11:30:08][139967296][ 131739][ ] send: "AT"
[11:30:08][139967375][ 131754][ ] recv: "OK"
[11:30:08][139967375][ 311115][ERR] Failed to receive command -
aborting
[11:30:08][139967375][ 130804][ ] Hanging up
[11:30:08][139967421][ 131580][ ] send: "ATH0"
[11:30:09][139967781][ 131688][ ] recv: "OK"
[11:30:09][139967828][ 131580][ ] send: "ATH0"
[11:30:09][139968062][ 131688][ ] recv: "OK"
[11:30:09][139968171][ 130698][ ] send:
"AT+FCLASS=0"
[11:30:10][139968718][ 131580][ ] send: "AT"
[11:30:10][139968953][ 131688][ ] recv: "OK"
[11:30:10][139969000][ 131580][ ] send: "AT"
[11:30:10][139969234][ 131688][ ] recv: "OK"
[11:30:11][139969921][ 322612][ERR] Failed receive

**** end log ***

[Gregg Hill]

Robert,

Please pardon my intrusion, but your own people (Brandy Nee and Crina Li)
continually recommend the 3Com (US Robotics) Courier V. Everything external
modem as the best one to receive faxes, in spite of it not being on the HCL.

Brandy Nee
http://groups.google.com/groups/search?lr=&safe=off&num=100&q=%22brandy+nee%22+courier+everything&safe=off

Crina Li
http://groups.google.com/groups/search?lr=&safe=off&num=100&q=%22crina+li%22+courier+everything&safe=off

You are also ignoring the fact that the OP's modems worked perfectly before
he ran SFC.

I wish you folks would make up your minds as to whether or not you want to
continue recommending the Courier V.Everything external modem..

Gregg Hill

"Robert Li [MSFT]" <v-ro...@online.microsoft.com> wrote in message
news:rL0n8W6...@TK2MSFTNGHUB02.phx.gbl...

[Robert Li [MSFT]]

Hi Nick,

Thanks for updating.

Because your modem in not in the HCL list, we don't provide support of this
kind according to our newsgroup policy. Thanks for understanding. Please
ask the modem manufacture for more support.

Best regards,

Robert Li(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

====================================================

PLEASE NOTE: The partner managed newsgroups are provided toassist with

break/fix issues and simple how to questions.
We also love to hear your product feedback! Let us know what you think by
posting from the web interface: Partner Feedback
from your newsreader: microsoft.private.directaccess.partnerfeedback.

We look forward to hearing from you!

====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.

====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

====================================================

--------------------
<From: "Nick" <NoS...@Nowhere.com>
<References: <#1AqSB0M...@TK2MSFTNGP04.phx.gbl>
<FQBaOB7M...@TK2MSFTNGHUB02.phx.gbl>
<e67ctlBN...@TK2MSFTNGP02.phx.gbl>
<SF#tnEMNH...@TK2MSFTNGHUB02.phx.gbl>
<e#3oJrmNH...@TK2MSFTNGP04.phx.gbl>
<GXwOR89N...@TK2MSFTNGHUB02.phx.gbl>
<O5TTUABO...@TK2MSFTNGP04.phx.gbl>
<y7HvtrFO...@TK2MSFTNGHUB02.phx.gbl>

<uSznWhJO...@TK2MSFTNGP03.phx.gbl>
<ul$PBoKOH...@TK2MSFTNGHUB02.phx.gbl>
<#qhjMOWO...@TK2MSFTNGP04.phx.gbl>
<u6pAHvdO...@TK2MSFTNGP02.phx.gbl>
<#8ncUmmO...@TK2MSFTNGP04.phx.gbl>
<OUgj8AqO...@TK2MSFTNGP04.phx.gbl>

<Subject: Re: Received fax errors after running SFC.exe

<Date: Mon, 29 Jan 2007 21:11:42 -0000
<Lines: 303
<X-Priority: 3
<X-MSMail-Priority: Normal
<X-Newsreader: Microsoft Outlook Express 6.00.3790.2826
<X-RFC2646: Format=Flowed; Response
<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
<Message-ID: <#J#6Vo#QHHA...@TK2MSFTNGP04.phx.gbl>
<Newsgroups: microsoft.public.windows.server.sbs
<NNTP-Posting-Host: host81-155-9-103.range81-155.btcentralplus.com
81.155.9.103
<Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
<Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:13566
<X-Tomcat-NG: microsoft.public.windows.server.sbs

[Nick]

Well can you tell me what external modems are on this infamous HCL list
please? I cannot seem to find any that are.

Thanks,
Nick

"Robert Li [MSFT]" <v-ro...@online.microsoft.com> wrote in message

news:l$SQFrFRH...@TK2MSFTNGHUB02.phx.gbl...

[Robert Li [MSFT]]

Hi Nick,

Both PCI modem and External modem may be in the HCL list. If your device is
not in the HCL list, we don't provide technical support according to our
policy. Thanks for understanding.

Best regards,

Robert Li(MSFT)

Get Secure! - www.microsoft.com/security

====================================================

====================================================

====================================================

====================================================

<#J#6Vo#QHHA...@TK2MSFTNGP04.phx.gbl>
<l$SQFrFRH...@TK2MSFTNGHUB02.phx.gbl>

<Subject: Re: Received fax errors after running SFC.exe

<Date: Tue, 30 Jan 2007 12:29:49 -0000
<Lines: 470

<X-Priority: 3
<X-MSMail-Priority: Normal
<X-Newsreader: Microsoft Outlook Express 6.00.3790.2826

<X-RFC2646: Format=Flowed; Original

<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826

<Message-ID: <ePfnYpG...@TK2MSFTNGP05.phx.gbl>
<Newsgroups: microsoft.public.windows.server.sbs
<NNTP-Posting-Host: host86-138-107-107.range86-138.btcentralplus.com
86.138.107.107
<Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
<Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:13733
<X-Tomcat-NG: microsoft.public.windows.server.sbs

[NickC]

Yes Robert there _may_ be PCI and external modems in the 2003 HCL but ARE
there ANY? I cannot even find a Win2003 HCL let alone an SBS2003 one!

Best I can find is a Win2K HCL but that only seems to contain internal
modems, I could not find any External ones. Could you please tell me what
_External_ modems are compatible with SBS2003, according to your newsgroup
policy?

Nick

"Robert Li [MSFT]" <v-ro...@online.microsoft.com> wrote in message

news:Uyb7qmTR...@TK2MSFTNGHUB02.phx.gbl...

[Gregg Hill]

Nick,

Per Microsoft's own web site, "The HCLs are no longer maintained as a
comprehensive reference." They have been replaced by the Windows Catalogs
here http://www.microsoft.com/whdc/hcl/default.mspx with a server-specific
Windows Server Catalog here
http://www.windowsservercatalog.com/default.aspx.

I notice that Robert completely ignored my question as to why Crina Li and
Brandy Nee keep recommending the same non-HCL modem that you already have as
the one to use if you have fax problems.

Robert, in case you missed it, here it is again:
**************************
Robert,

Please pardon my intrusion, but your own people (Brandy Nee and Crina Li)
continually recommend the 3Com (US Robotics) Courier V. Everything external
modem as the best one to receive faxes, in spite of it not being on the HCL.

Brandy Nee
http://groups.google.com/groups/search?lr=&safe=off&num=100&q=%22brandy+nee%22+courier+everything&safe=off

Crina Li
http://groups.google.com/groups/search?lr=&safe=off&num=100&q=%22crina+li%22+courier+everything&safe=off

You are also ignoring the fact that the OP's modems worked perfectly before
he ran SFC.

I wish you folks would make up your minds as to whether or not you want to
continue recommending the Courier V.Everything external modem.

Gregg Hill
**************************

Nick,

Good luck with your problem. My recommendation still is to go with
Brooktrout. As much as it hurts, **cut your losses** and put it behind you
(see my other threads previously mentioned). Per their part number guide
http://www.cantata.com/products/part_no._guide/, you can use a low-end
TruFax board, or their high-end TR1034 board. You have two lines, so the
2-port TruFax should do well. In my testing, it fixed all my problems. Yes,
it is expensive, but how much more time are you willing to spend on
something that perhaps NO modem may be able to fix? I told my client I would
sell the Brooktrout to them for my cost and install it for no charge, and
they are happy with that. All I lost was about 30 hours of time testing
various modems. Never again!

I think this is the one you should consider, but call them to make sure.

999-169-15
Trufax 200-R PCI UK MSF
Microsoft Shared Fax support for2 Channel Loop Start; Half Size
Universal PCI for the UK

***As long as you have the fax service installed properly*** and it answers
calls or tries to send, I think the Brooktrout will help you. You can always
call them and ask if they can loan you a board for testing purposes (see my
threads again).

Personally, I will not use a modem again after the experiences I have had.
Clients can either pop for a Brooktrout, or they can stick with their manual
fax machine.

Gregg Hill

"NickC" <NoOn...@BTInternet.com> wrote in message
news:%23xw$BJVRHH...@TK2MSFTNGP02.phx.gbl...

[Robert Li [MSFT]]

Hi Nick,

Thanks for updating.

I will discuss with Crina Li and Brandy Nee and will give you reply.

Thanks for understanding.

Best regards,

Robert Li(MSFT)

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.

--------------------

<Reply-To: "Gregg Hill" <bo...@nowhere.com>
<From: "Gregg Hill" <bo...@nowhere.com>

<References: <#1AqSB0M...@TK2MSFTNGP04.phx.gbl>
<FQBaOB7M...@TK2MSFTNGHUB02.phx.gbl>
<e67ctlBN...@TK2MSFTNGP02.phx.gbl>
<SF#tnEMNH...@TK2MSFTNGHUB02.phx.gbl>
<e#3oJrmNH...@TK2MSFTNGP04.phx.gbl>
<GXwOR89N...@TK2MSFTNGHUB02.phx.gbl>
<O5TTUABO...@TK2MSFTNGP04.phx.gbl>
<y7HvtrFO...@TK2MSFTNGHUB02.phx.gbl>
<uSznWhJO...@TK2MSFTNGP03.phx.gbl>
<ul$PBoKOH...@TK2MSFTNGHUB02.phx.gbl>
<#qhjMOWO...@TK2MSFTNGP04.phx.gbl>
<u6pAHvdO...@TK2MSFTNGP02.phx.gbl>
<#8ncUmmO...@TK2MSFTNGP04.phx.gbl>
<OUgj8AqO...@TK2MSFTNGP04.phx.gbl>
<#J#6Vo#QHHA...@TK2MSFTNGP04.phx.gbl>
<l$SQFrFRH...@TK2MSFTNGHUB02.phx.gbl>

<ePfnYpG...@TK2MSFTNGP05.phx.gbl>
<Uyb7qmTR...@TK2MSFTNGHUB02.phx.gbl>
<#xw$BJVRHH...@TK2MSFTNGP02.phx.gbl>

<Subject: Re: Received fax errors after running SFC.exe

<Date: Wed, 31 Jan 2007 09:28:27 -0800
<Lines: 705
<X-Priority: 3
<X-MSMail-Priority: Normal
<X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
<X-RFC2646: Format=Flowed; Response
<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
<Message-ID: <urKS50VR...@TK2MSFTNGP03.phx.gbl>
<Newsgroups: microsoft.public.windows.server.sbs
<NNTP-Posting-Host: rrcs-67-52-120-131.west.biz.rr.com 67.52.120.131
<Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
<Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:14194
<X-Tomcat-NG: microsoft.public.windows.server.sbs

[Gregg Hill]

Robert,

Thank you for getting back to me on this subject. They have recommended the
3Com Courier V.Everything external modem. Depending upon when one bought
that modem, it was either boxed in a 3Com package or a US Robotics package,
since USR was bought by 3Com, then split from 3Com again, taking that modem
with them. I actually bought two "3Com" packaged modems that had US Robotics
on the front and on the part number labels.

Gregg Hill

"Robert Li [MSFT]" <v-ro...@online.microsoft.com> wrote in message

news:UoYyCdgR...@TK2MSFTNGHUB02.phx.gbl...

[Robert Li [MSFT]]

Hi Nick,

I made a discussion with our engineers. The product which is not in the HCL
is the one Microsoft hasn't fully tested. We can not guarantee it will work
familiarly with Microsoft products. So we don't provide technical support
for hardware which is not in the HCL list. Thanks for understanding.

Best regards,

Robert Li(MSFT)

Get Secure! - www.microsoft.com/security

=====================================================

=====================================================

<urKS50VR...@TK2MSFTNGP03.phx.gbl>
<UoYyCdgR...@TK2MSFTNGHUB02.phx.gbl>

<Subject: Re: Received fax errors after running SFC.exe

<Date: Thu, 1 Feb 2007 10:17:26 -0800
<Lines: 871

<X-Priority: 3
<X-MSMail-Priority: Normal
<X-Newsreader: Microsoft Outlook Express 6.00.2900.3028

<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028

<X-RFC2646: Format=Flowed; Original
<Message-ID: <ut7o70iR...@TK2MSFTNGP02.phx.gbl>

<Newsgroups: microsoft.public.windows.server.sbs
<NNTP-Posting-Host: rrcs-67-52-120-131.west.biz.rr.com 67.52.120.131

<Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
<Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:14447
<X-Tomcat-NG: microsoft.public.windows.server.sbs

[Nick]

Hello Robert, thank you for your reply.

> Thanks for understanding.
I do not understand, whatever gave you the idea that I understand!

If I have interpreted this correctly the most popular Business class modem
in the world is not on this ('no longer maintained as a
comprehensive reference') HCL because 'Microsoft hasn't fully tested' it,
why not? This is an incredibly perverse decision, why have Microsoft not
fully tested it?

You have still ignored my question, following, to which I would be grateful
for an answer:

> Could you please tell me what _External_ modems are compatible with
> SBS2003, according to your newsgroup policy?

You have also ignored Gregg's question:

> Please pardon my intrusion, but your own people (Brandy Nee and Crina Li)
> continually recommend the 3Com (US Robotics) Courier V. Everything
> external
> modem as the best one to receive faxes, in spite of it not being on the
> HCL.
>
> Brandy Nee

> http://groups.google.com/groups/search?lr=&safe=off&num=100&q=%22brandy+nee%22+courier+everything&safe=off
>
> Crina Li
> http://groups.google.com/groups/search?lr=&safe=off&num=100&q=%22crina+li%22+courier+everything&safe=off
>

> You are also ignoring the fact that the OP's modems worked perfectly
> before
> he ran SFC.
>
> I wish you folks would make up your minds as to whether or not you want to
> continue recommending the Courier V.Everything external modem.

Perhaps Brandy Nee or Crina Li might like to comment at this point if either
are watching this thread...

By the way I have just sent a fax sucessfully by connecting one of these fax
modems to a different Win2003 server on which it worked perfectly first
time. This is a WIN/SBS2003 problem, IT IS NOT a HARDWARE ISSUE.

Best regards,
Nick

"Robert Li [MSFT]" <v-ro...@online.microsoft.com> wrote in message

news:i9TPQ4rR...@TK2MSFTNGHUB02.phx.gbl...

[Gregg Hill]

Robert,

Once again, you have ignored my question. Yes, I **UNDERSTAND** that you do
not "provide technical support" for non-HCL modems. That was not my question
nor my point of posting. My point is that two of your MSFTs, Brandy Nee and
Crina Li, **RECOMMEND USING** the 3Com Courier V.Everything external modem,
**even though it is not on the HCL** and apparently never has been.

WHY DO MICROSOFT PEOPLE keep recommending a non-HCL modem, then tell us that
you do not support its use? That is the question I keep asking and that you
keep failing to answer.

Please read the following threads so that YOU understand that the modem
keeps being recommended in spite of not being on the HCL. There are more
examples of MSFT recommending it than just the two links below.

Brandy Nee
http://groups.google.com/groups/search?lr=&safe=off&num=100&q=%22brandy+nee%22+courier+everything&safe=off

Crina Li
http://groups.google.com/groups/search?lr=&safe=off&num=100&q=%22crina+li%22+courier+everything&safe=off

Please have Crina Li or Brandy Nee explain themselves.

Thank you.

Gregg Hill

"Robert Li [MSFT]" <v-ro...@online.microsoft.com> wrote in message

news:i9TPQ4rR...@TK2MSFTNGHUB02.phx.gbl...

[Gregg Hill]

Nick,

The only way they are even going to begin supporting you is if you use a
modem listed in the HCL. So you will need to buy one of those, install it,
have it not work, then ask again for help.

Yes, Robert has once again ignored my question.

The Windows Server Catalog of Tested Products is a HORRIBLE reference, as it
cannot be searched for products that specifically work on Server 2003. I
just looked at bunch of external modems, and they are listed as working with
XP and 2000 Server, but none so far listed with Windows Server 2003 as an
approved product.

Not to Microsoft: please make your Windows Server Catalog of Tested Products
searchable in more detail, sort of like a Google search where we can drill
down to get specific listings rather than wade through 800 modems to find
the one you support on 2003.

Gregg Hill

"Nick" <NoS...@Nowhere.com> wrote in message

news:uRhR8ntR...@TK2MSFTNGP04.phx.gbl...

[Gregg Hill]

Nick,

Look at these
http://multitech.com/PRODUCTS/Categories/Device_Networking/external_modems/
to satisfy their requirement of being on the 2003 list. We know it is most
likely not hardware (duh), but if you want help, they will force you to use
one on the list.

MultiTech is a great brand, but sometimes has problems receiving from USR
modems, so be careful how you do your testing. In other words, send from
your problem server to a manual fax, and from a manual fax to your server.
Just do not use any of the manual fax machines that Brandy and Crina
recommend using the 3Com Courier to receive from them!

Gregg Hill

"Nick" <NoS...@Nowhere.com> wrote in message
news:uRhR8ntR...@TK2MSFTNGP04.phx.gbl...

[Nick]

Robert,

Why do you keep sending these nosensical messages. Please simply address
the questions!

You have still not provided any examples of an External Fax/Modem that would
satisfy your requirement of being on the SBS2003 HCL, which modem do you
suggest?

You have also still failed to address Greggs's questions.

Nick

"Robert Li [MSFT]" <v-ro...@online.microsoft.com> wrote in message

news:mUfKowRS...@TK2MSFTNGHUB02.phx.gbl...

> Hi Nick,
>
> Thanks for updating.
>

> Please understand we only provide technical support for hardware in the
> HCL
> list. That's our newsgroup policy.

> <ut7o70iR...@TK2MSFTNGP02.phx.gbl>
> <i9TPQ4rR...@TK2MSFTNGHUB02.phx.gbl>
> <uRhR8ntR...@TK2MSFTNGP04.phx.gbl>

> <Subject: Re: Received fax errors after running SFC.exe

> <Date: Fri, 2 Feb 2007 10:04:08 -0800
> <Lines: 1246

> <X-Priority: 3
> <X-MSMail-Priority: Normal
> <X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
> <X-RFC2646: Format=Flowed; Response
> <X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028

> <Message-ID: <eyHtKSvR...@TK2MSFTNGP02.phx.gbl>

> <Newsgroups: microsoft.public.windows.server.sbs
> <NNTP-Posting-Host: rrcs-67-52-120-131.west.biz.rr.com 67.52.120.131
> <Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl

> <Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:14659
> <X-Tomcat-NG: microsoft.public.windows.server.sbs

[Gregg Hill]

Nick,

Unless you have a modem on the now-defunct HCL, or perhaps one in the
Windows Catalog, you will get no further help from them. As I said before,
you will need to buy one of those approved modems, install it, have it not
work, then ask again for help. I understand that you are convinced it is not
hardware, and I believe you, but they are not going to budge. Get an
approved modem (or a Brooktrout board).

Look at these modems
http://www.windowsservercatalog.com/results.aspx?&bCatID=1459&cpID=1415&ocID=0&OR=1.
MultiTech is a good brand, and they are "Designed for Microsoft Windows
Server 2003."

Good hunting!

Gregg Hill

"Nick" <NoS...@Nowhere.com> wrote in message

news:%237nAAET...@TK2MSFTNGP02.phx.gbl...

[Gregg Hill]

Robert,

I am curious why you keep referring to the HCL, when your link flips over to
this page http://www.microsoft.com/whdc/hcl/default.mspx that says, "The

HCLs are no longer maintained as a comprehensive reference."

When you refer to finding "hundreds" of external modems, did you find that
by searching the Internet, by searching the old HCL, or by searching the
HCL's replacement at http://www.windowsservercatalog.com/default.aspx?

When using the replacement for the HCL, i.e., the Windows Server Catalog at
http://www.windowsservercatalog.com/default.aspx, I click on Modems under
the Hardware Testing Status column, then I click on "Designed for Windows
Server 2003 - Hardware" under the "By Compatibility" heading. It lists 24
modems, not hundreds, and most of those are internal PCI modems, not
external ones.

Please show us where any of the ones you listed are compatible ***with
Windows Server 2003***, according to a Microsoft web site.

The only modems listed as Designed for Microsoft Windows Server 2003 are the
following 24 modems, and most are PCI modems.

U.S. Robotics Corporation (9)
Multi-Tech Systems Incorporated (7)
Eicon Networks Corporation (3)
Conexant Systems, Inc. (2)
4G Systems GmbH (1)
Broadcom Corporation (1)
TRENDCHIP Technologies Corporation (1)

Can you back up your claim that you found "hundreds" of external modems in
the HCL or on any MICROSOFT web site that are designed for ***Windows Server
2003*** and not just Windows 2000 Server?

Gregg Hill

"Robert Li [MSFT]" <v-ro...@online.microsoft.com> wrote in message

news:$8zaybeS...@TK2MSFTNGHUB02.phx.gbl...

> Hi Nick,
>
> Thanks for updating.
>

> After search the web, I found hundreds of foumous External Modems in the
> HCL, For example:
>
> Rockwell DPF External Modem
> GVC External 28800 Fax Modem
> Logicode 9624 Data-Fax External
> Rockwell DPF External Modem
>
> Please understand we only provide technical support for the hardware in
> HCL
> list.
>
> If you need further assistance, please don't hesitate to let me know.

> <e#3oJrmNH...@TK2MSFTNGP04.phx.gbl>
> <GXwOR89N...@TK2MSFTNGHUB02.phx.gbl>
> <O5TTUABO...@TK2MSFTNGP04.phx.gbl>
> <y7HvtrFO...@TK2MSFTNGHUB02.phx.gbl>
> <uSznWhJO...@TK2MSFTNGP03.phx.gbl>
> <ul$PBoKOH...@TK2MSFTNGHUB02.phx.gbl>
> <#qhjMOWO...@TK2MSFTNGP04.phx.gbl>
> <u6pAHvdO...@TK2MSFTNGP02.phx.gbl>
> <#8ncUmmO...@TK2MSFTNGP04.phx.gbl>
> <OUgj8AqO...@TK2MSFTNGP04.phx.gbl>
> <#J#6Vo#QHHA...@TK2MSFTNGP04.phx.gbl>
> <l$SQFrFRH...@TK2MSFTNGHUB02.phx.gbl>
> <ePfnYpG...@TK2MSFTNGP05.phx.gbl>
> <Uyb7qmTR...@TK2MSFTNGHUB02.phx.gbl>
> <#xw$BJVRHH...@TK2MSFTNGP02.phx.gbl>
> <urKS50VR...@TK2MSFTNGP03.phx.gbl>
> <UoYyCdgR...@TK2MSFTNGHUB02.phx.gbl>
> <ut7o70iR...@TK2MSFTNGP02.phx.gbl>
> <i9TPQ4rR...@TK2MSFTNGHUB02.phx.gbl>
> <uRhR8ntR...@TK2MSFTNGP04.phx.gbl>

> <eyHtKSvR...@TK2MSFTNGP02.phx.gbl>
> <mUfKowRS...@TK2MSFTNGHUB02.phx.gbl>
> <#7nAAETS...@TK2MSFTNGP02.phx.gbl>

> <Subject: Re: Received fax errors after running SFC.exe

> <Date: Mon, 5 Feb 2007 13:23:40 -0800
> <Lines: 1501

> <X-Priority: 3
> <X-MSMail-Priority: Normal
> <X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
> <X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028

> <X-RFC2646: Format=Flowed; Response
> <Message-ID: <O2qLpvW...@TK2MSFTNGP04.phx.gbl>

> <Newsgroups: microsoft.public.windows.server.sbs
> <NNTP-Posting-Host: rrcs-67-52-120-131.west.biz.rr.com 67.52.120.131

> <Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
> <Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:15081
> <X-Tomcat-NG: microsoft.public.windows.server.sbs

[Gregg Hill]

Robert,

Why do you repeatedly fail to answer the question that I asked?

Let us clear up this question. YES, ***WE BOTH UNDERSTAND*** that you do not
provide ***tech support*** for non-HCL modems. I GET IT!!!

That is NOT what I asked! What I asked was WHY DO CRINA LI AND BRANDY NEE
KEEP RECOMMENDING the ***non-HCL*** 3Com Courier V.Everything external
modem? WHY DO THEY RECOMMEND using a non-HCL modem if Microsoft will not
support it?

You HAVE NOT answered that question yet!

Once again, please read these posts where they RECOMMEND the very modem that
you say is not supported!

Your own people (Brandy Nee and Crina Li) continually recommend the 3Com
(identical to US Robotics) Courier V. Everything external modem as the best
one to receive faxes, ***in spite of it not being on the HCL.***

Brandy Nee
http://groups.google.com/groups/search?lr=&safe=off&num=100&q=%22brandy+nee%22+courier+everything&safe=off

Crina Li
http://groups.google.com/groups/search?lr=&safe=off&num=100&q=%22crina+li%22+courier+everything&safe=off

I wish you folks would make up your minds as to whether or not you want to
continue ***recommending*** the Courier V.Everything external modem in spite
of it not being on the "HCL" to which you refer.

By the way, where EXACTLY is this mystery HCL for Server 2003?

Gregg Hill

"Robert Li [MSFT]" <v-ro...@online.microsoft.com> wrote in message

news:i9TPQ4rR...@TK2MSFTNGHUB02.phx.gbl...

[NickC]

Robert,

Do you have a different HCL than I do? I cannot find any of these modems
you mention in the HCL that I am looking at
http://www.windowsservercatalog.com/results.aspx?&bCatID=1459&cpID=0&ocID=0&OR=1.

Nick

"Robert Li [MSFT]" <v-ro...@online.microsoft.com> wrote in message

news:$8zaybeS...@TK2MSFTNGHUB02.phx.gbl...

> Hi Nick,
>
> Thanks for updating.
>

> After search the web, I found hundreds of foumous External Modems in the
> HCL, For example:
>
> Rockwell DPF External Modem
> GVC External 28800 Fax Modem
> Logicode 9624 Data-Fax External
> Rockwell DPF External Modem
>
> Please understand we only provide technical support for the hardware in
> HCL
> list.
>
> If you need further assistance, please don't hesitate to let me know.
>
>

> <e#3oJrmNH...@TK2MSFTNGP04.phx.gbl>
> <GXwOR89N...@TK2MSFTNGHUB02.phx.gbl>
> <O5TTUABO...@TK2MSFTNGP04.phx.gbl>
> <y7HvtrFO...@TK2MSFTNGHUB02.phx.gbl>
> <uSznWhJO...@TK2MSFTNGP03.phx.gbl>
> <ul$PBoKOH...@TK2MSFTNGHUB02.phx.gbl>
> <#qhjMOWO...@TK2MSFTNGP04.phx.gbl>
> <u6pAHvdO...@TK2MSFTNGP02.phx.gbl>
> <#8ncUmmO...@TK2MSFTNGP04.phx.gbl>
> <OUgj8AqO...@TK2MSFTNGP04.phx.gbl>
> <#J#6Vo#QHHA...@TK2MSFTNGP04.phx.gbl>
> <l$SQFrFRH...@TK2MSFTNGHUB02.phx.gbl>
> <ePfnYpG...@TK2MSFTNGP05.phx.gbl>
> <Uyb7qmTR...@TK2MSFTNGHUB02.phx.gbl>
> <#xw$BJVRHH...@TK2MSFTNGP02.phx.gbl>
> <urKS50VR...@TK2MSFTNGP03.phx.gbl>
> <UoYyCdgR...@TK2MSFTNGHUB02.phx.gbl>
> <ut7o70iR...@TK2MSFTNGP02.phx.gbl>
> <i9TPQ4rR...@TK2MSFTNGHUB02.phx.gbl>
> <uRhR8ntR...@TK2MSFTNGP04.phx.gbl>

> <eyHtKSvR...@TK2MSFTNGP02.phx.gbl>
> <mUfKowRS...@TK2MSFTNGHUB02.phx.gbl>
> <#7nAAETS...@TK2MSFTNGP02.phx.gbl>

> <Subject: Re: Received fax errors after running SFC.exe

> <Date: Mon, 5 Feb 2007 13:23:40 -0800
> <Lines: 1501

> <X-Priority: 3
> <X-MSMail-Priority: Normal
> <X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
> <X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028

> <X-RFC2646: Format=Flowed; Response
> <Message-ID: <O2qLpvW...@TK2MSFTNGP04.phx.gbl>

> <Newsgroups: microsoft.public.windows.server.sbs
> <NNTP-Posting-Host: rrcs-67-52-120-131.west.biz.rr.com 67.52.120.131

> <Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
> <Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:15081
> <X-Tomcat-NG: microsoft.public.windows.server.sbs
> <

[Alberta Peach]

Hi, I have a problem with the MS Fax, as it does not seem to startup properly
afer computer reboot. The only way I can get it to work is to uncheck MS Fax
in Add/Remove Windows Component, restart PC, then check MS Fax box in
Add/Remove Windows Component. It will work in that one session. However, it
will not work again after computer restart. The Fax Console keeps on saying
refreshing. And the status is "Stopping" in Admin Tools> Services. The
options for start, pause, stop, resume are all grayed out.

I use XP Home, SP2, IE7 and have been using the Microsoft Fax function to
send faxes in the past with no problems. However about a month ago when I
tried to send a fax (print a webpage to the fax printer in IE7), the "Send
Fax Wizard" opens, but when I click on "Next", nothing happens, and then the
program does not respond.
I tried checking the "Printers and Faxes", the "Fax Console" opens OK, but
the Status at the bottom of the Fax Console says "Refreshing". Then later an
error message said that the "Microsoft SHared Fax printer" driver is not
installed.

I tried removing the Fax component in Control Panel> Add Remove Programs>
Add Remove Windows Components> unchecked the "Fax Service" box. Restart
computer. Then check back the "Fax service box". Still have same problem.

The last time that I recall being able to successfully print to a fax was at
the beginning of Dec. 2006, and since then I had only done Windows Automatic
Update which included a couple of Windows XP Security Updates. I have Zone
Alarm, but I have not changed anything in it, and I was able to successfully
print before with Zone Alarm installed.

When I was trying to install and uninstall Fax today, there was a time when
I was able to open Fax Console and the status at bottom of page showed
"online", and I was able to send and receive faxes. However, after
restarting computer, cannot send faxes again, and still get the error message
for printer driver not installed.
A couple of times Zone Alarm said that Fax Console tried to act as Server,
and I granted it permission. I have also tried disabling Zone Alarm, but
still fax problem.

How can I reinstall the Fax Component besides checking and unchecking the
box in Add/Remove Windows Component? I don't want to have to reinstall
Windows XP.

Thanks in advance for any advice on the above.

I saw in a post in March 2005 that "Davidosom" had basically an identical
problem as mine. However, no solution was posted in that thread...

""Inn Jin [MSFT]"" wrote:

> Hi Nick,
>
> Thank you for your mail.
>
> I appreciate your detailed effort on this issue and want to say the log
> files you send to me is just same as T30 log (although they are not).
> However, I need to inform first, as your modem is not in the HCL list, we
> cannot guarantee it will completely compatible with OS, and cannot
> guarantee it will completely work fine either. Also products out of HCL
> list are out of my support boundary. All what I have done is to want to
> help you solve your issue even it is out of my support boundary.
>
> Following are answers to you questions:
>
> 1. For the Microsoft drivers:
>
> Microsoft drivers are designed for industrial standards, it is general
> drivers, all though most of the device vendors are design their products
> base on industrial standards, but they have different specific features
> which are different with our vendors, we cannot guarantee our drivers can
> fulfill all the vendor specific features. That's why I asked you to change
> your driver to make sure your driver can be completely suitable for you
> device.
>
> 2. For the change of modem driver version
>
> Microsoft Updates contain many fields including hardware. We upgrade our
> driver, because we found some need to be change, for example we fix some
> bugs, or we need to change because change of industrial standard. Moreover,
> these hardware updates can be conclude in any windows updates, we make
> description of every updates. You can referred to the description.
>
> 3. Files in "C:\WINDOWS\system32\clients\faxclient\drivers" folder is not
> related to the driver use by server, it is related to the clients which may
> related to this issue if the fax modem was shared with these clients.
>
> Back up to the issue, after carefully analyzing your logs, and long
> discussion with our specialists in fax, we agreed this issue belongs to the
> driver or the hardware.
>
> [20:30:54][000583062][ 131580][ ] send:
> "AT+FRM=146"
> [20:30:56][000585562][ 131688][ ] recv: "NO
> CARRIER"
> [20:30:57][000585765][ 131580][ ] send:
> "AT+FRM=146"
> [20:30:59][000588265][ 131732][WRN] failed to

> receive expected response: CONNECT, +FCERROR, NO CARRIER

> [20:30:59][000588265][ 131739][ ] send: "AT"
> [20:30:59][000588343][ 131754][ ] recv: "OK"
> [20:30:59][000588343][ 311419][WRN] Failed to receive page 1 -
> receiving commands
> [20:30:59][000588343][ 131580][ ] send:
> "AT+FRH=3"
> [20:31:05][000594343][ 131732][WRN] failed to

> receive expected response: CONNECT, +FCERROR, NO CARRIER

> [20:31:05][000594343][ 131739][ ] send: "AT"
> [20:31:05][000594421][ 131754][ ] recv: "OK"
> [20:31:05][000594421][ 311115][ERR] Failed to receive command
> - aborting
>
> This part code indicates that error are related to driver or hardware.
>
> Here is the workaround:
> 1. Please copy all the files related to the fax driver, copy it to a folder
> in your local hard disk
> 2. Restart the server into save mode (Press F8 when the server reboot)
> 3. When start as save mode, please run services.msc make sure fax service
> is not start. If it starts, please stop it.
> 4. Copy all the fax driver files to the system folder which it should be.
> replace them with the files in the system folder.
> 5. For .dll files, please type the following commands in the command prompt:
>
> Regsvr32 <the file name>
>
> 6. Restart the server normally to check whether the issue persist.
>
> If the issue persists, please contact the fax modem vendor and install
> drivers from vendor, or change your hardware to isolate the issue. If my
> suggestion don't help. I'll happy to assist you if you can try the drivers
> from the vendor.
>
> I appreciate your understanding and cooperating.
>
> Have a nice day!
>
> Best regards,
>
> Inn Jin (MSFT)

[Gregg Hill]

You need to start a fresh thread of your own. Hijacking this thread is a
dead end.

Gregg Hill

"Alberta Peach" <Albert...@discussions.microsoft.com> wrote in message
news:0CAC0B83-DCB7-4713...@microsoft.com...

[Gregg Hill]

In addition to starting a new thread, you should post it in the
"microsoft.public.windowsxp.print_fax " newsgroup. This newsgroup is for
Small Business Server issues.

Gregg Hill

"Alberta Peach" <Albert...@discussions.microsoft.com> wrote in message
news:0CAC0B83-DCB7-4713...@microsoft.com...

[Nick]

Robert,

This thread here suggests that changing the hardware to a Brooktrout card is
not likely to solve the problem, don't you agree?
http://groups.google.co.uk/group/microsoft.public.windows.server.sbs/browse_frm/thread/4711ee7d01bff7b0/d8224dd6a6d07120?lnk=st&q=how+to+remove+modem+driver+in+win2003&rnum=21&hl=en&utoken=ZElwh0YAAACAT_kPml7nPanGq5_khmjXgP-tS31hakRaUqJOki041naBZu94Po8QWbRPOoFxT_ADYOl41A09E2ElUryCiI5HDUSQru1mlltfqxY-gvDaEg

Can your SBSFax developers supply us with a registry file containing all the
registry entries for Win2003 Fax and SBSFax?

Also still waiting for your reply to my last message.

> "NickC" <NoOn...@BTInternet.com> wrote in message

> news:%23VanDms...@TK2MSFTNGP02.phx.gbl...

> Do you have a different HCL than I do? I cannot find any of these modems
> you mention in the HCL that I am looking at
> http://www.windowsservercatalog.com/results.aspx?&bCatID=1459&cpID=0&ocID=0&OR=1.

Best regards,
Nick

[Nick]

But what modems are in the list? As per my earlier post, that you have not
answered, where do I get a list of all EXTERNAL modems that are compatible
with SBS2003. Judging by the modems you quoted, you obviously have a
different list to the public one on the Microsoft Website -
http://www.windowsservercatalog.com/results.aspx?&bCatID=1459&cpID=0&ocID=0&OR=1.

Nick

"Robert Li [MSFT]" <v-ro...@online.microsoft.com> wrote in message

news:Y9H1TE3T...@TK2MSFTNGHUB02.phx.gbl...

> Hi Nick,
>
> Thanks for updating.
>

> Since your modem is not in the HCL list, that means the product is not
> fully tested by Microsoft Engineer and we cannot guarantee it will work
> familiarly with our software. You can change the modem in the HCL list to
> narrow down the problem. If it works, the problem is caused by hardware.
> If
> it doesn't work, it's caused by software and in this condition, we will
> try
> our best to help you. Thanks for understanding.

> <From: "Nick" <NoS...@Nowhere.com>
> <References: <#1AqSB0M...@TK2MSFTNGP04.phx.gbl>

> <y7HvtrFO...@TK2MSFTNGHUB02.phx.gbl>
> <uSznWhJO...@TK2MSFTNGP03.phx.gbl>
> <ul$PBoKOH...@TK2MSFTNGHUB02.phx.gbl>
> <#qhjMOWO...@TK2MSFTNGP04.phx.gbl>
> <u6pAHvdO...@TK2MSFTNGP02.phx.gbl>
> <#8ncUmmO...@TK2MSFTNGP04.phx.gbl>
> <OUgj8AqO...@TK2MSFTNGP04.phx.gbl>
> <#J#6Vo#QHHA...@TK2MSFTNGP04.phx.gbl>
> <l$SQFrFRH...@TK2MSFTNGHUB02.phx.gbl>
> <ePfnYpG...@TK2MSFTNGP05.phx.gbl>
> <Uyb7qmTR...@TK2MSFTNGHUB02.phx.gbl>
> <#xw$BJVRHH...@TK2MSFTNGP02.phx.gbl>
> <urKS50VR...@TK2MSFTNGP03.phx.gbl>
> <UoYyCdgR...@TK2MSFTNGHUB02.phx.gbl>
> <ut7o70iR...@TK2MSFTNGP02.phx.gbl>
> <i9TPQ4rR...@TK2MSFTNGHUB02.phx.gbl>
> <uRhR8ntR...@TK2MSFTNGP04.phx.gbl>
> <eyHtKSvR...@TK2MSFTNGP02.phx.gbl>
> <mUfKowRS...@TK2MSFTNGHUB02.phx.gbl>
> <#7nAAETS...@TK2MSFTNGP02.phx.gbl>

> <O2qLpvW...@TK2MSFTNGP04.phx.gbl>
> <$8zaybeS...@TK2MSFTNGHUB02.phx.gbl>
> <#VanDmsS...@TK2MSFTNGP02.phx.gbl>

> <Subject: Re: Received fax errors after running SFC.exe

> <Date: Fri, 9 Feb 2007 17:28:40 -0000
> <Lines: 22

> <X-Priority: 3
> <X-MSMail-Priority: Normal
> <X-Newsreader: Microsoft Outlook Express 6.00.3790.2826
> <X-RFC2646: Format=Flowed; Response
> <X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826

> <Message-ID: <O8xNA$GTHHA...@TK2MSFTNGP06.phx.gbl>
> <Newsgroups: microsoft.public.windows.server.sbs
> <NNTP-Posting-Host: host81-155-165-192.range81-155.btcentralplus.com
> 81.155.165.192
> <Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl
> <Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:16093
> <X-Tomcat-NG: microsoft.public.windows.server.sbs

[Gregg Hill]

Some modems "Designed for Microsoft Windows Server 2003" are here
http://www.windowsservercatalog.com/results.aspx?&bCatID=1459&cpID=1415&ocID=0&OR=1

External
http://multitech.com/PRODUCTS/Families/MultiModemZBA/

http://multitech.com/PRODUCTS/Families/MultiModemZDX/

Gregg Hill

"Nick" <NoS...@Nowhere.com> wrote in message

news:eZargm4T...@TK2MSFTNGP06.phx.gbl...

[Gregg Hill]

Robert,

Would you please answer my post from 2/6/07 at 3:45PM regarding your claim
of finding hundreds of modems in the HCL?

You claimed that, "After search the web, I found hundreds of foumous

External Modems in the HCL, For example:"

Rockwell DPF External Modem
GVC External 28800 Fax Modem
Logicode 9624 Data-Fax External
Rockwell DPF External Modem

I replied and asked the following, but never got an answer:

Robert,

I am curious why you keep referring to the HCL, when your link flips over to

this page http://www.microsoft.com/whdc/hcl/default.mspx that says, "The

HCLs are no longer maintained as a comprehensive reference."

When you refer to finding "hundreds" of external modems, did you find that

by searching the Internet, by searching the old HCL, or by searching the
HCL's replacement at http://www.windowsservercatalog.com/default.aspx?

When using the replacement for the HCL, i.e., the Windows Server Catalog at
http://www.windowsservercatalog.com/default.aspx, I click on Modems under
the Hardware Testing Status column, then I click on "Designed for Windows
Server 2003 - Hardware" under the "By Compatibility" heading. It lists 24
modems, not hundreds, and most of those are internal PCI modems, not
external ones.

Please show us where any of the ones you listed are compatible ***with
Windows Server 2003***, according to a Microsoft web site.

The only modems listed as Designed for Microsoft Windows Server 2003 are the
following 24 modems, and most are PCI modems.

U.S. Robotics Corporation (9)
Multi-Tech Systems Incorporated (7)
Eicon Networks Corporation (3)
Conexant Systems, Inc. (2)
4G Systems GmbH (1)
Broadcom Corporation (1)
TRENDCHIP Technologies Corporation (1)

Can you back up your claim that you found "hundreds" of external modems in
the HCL or on any MICROSOFT web site that are designed for ***Windows Server
2003*** and not just Windows 2000 Server?

Gregg Hill

"Robert Li [MSFT]" <v-ro...@online.microsoft.com> wrote in message
news:uqYvhWDU...@TK2MSFTNGHUB02.phx.gbl...
> Hi Nick,
>
> Thanks for updating and also for Gregg's input.
>
> Please select an External Modem in the following link according to you
> environment.
>
> http://www.windowsservercatalog.com/results.aspx?&bCatID=1459&cpID=1415&ocID
> =0&OR=1
>
> I am looking forward to hear from you.

> <Reply-To: "Gregg Hill" <bo...@nowhere.com>
> <From: "Gregg Hill" <bo...@nowhere.com>
> <References: <#1AqSB0M...@TK2MSFTNGP04.phx.gbl>

> <#qhjMOWO...@TK2MSFTNGP04.phx.gbl>
> <u6pAHvdO...@TK2MSFTNGP02.phx.gbl>
> <#8ncUmmO...@TK2MSFTNGP04.phx.gbl>
> <OUgj8AqO...@TK2MSFTNGP04.phx.gbl>
> <#J#6Vo#QHHA...@TK2MSFTNGP04.phx.gbl>
> <l$SQFrFRH...@TK2MSFTNGHUB02.phx.gbl>
> <ePfnYpG...@TK2MSFTNGP05.phx.gbl>
> <Uyb7qmTR...@TK2MSFTNGHUB02.phx.gbl>
> <#xw$BJVRHH...@TK2MSFTNGP02.phx.gbl>
> <urKS50VR...@TK2MSFTNGP03.phx.gbl>
> <UoYyCdgR...@TK2MSFTNGHUB02.phx.gbl>
> <ut7o70iR...@TK2MSFTNGP02.phx.gbl>
> <i9TPQ4rR...@TK2MSFTNGHUB02.phx.gbl>
> <uRhR8ntR...@TK2MSFTNGP04.phx.gbl>
> <eyHtKSvR...@TK2MSFTNGP02.phx.gbl>
> <mUfKowRS...@TK2MSFTNGHUB02.phx.gbl>
> <#7nAAETS...@TK2MSFTNGP02.phx.gbl>
> <O2qLpvW...@TK2MSFTNGP04.phx.gbl>
> <$8zaybeS...@TK2MSFTNGHUB02.phx.gbl>
> <#VanDmsS...@TK2MSFTNGP02.phx.gbl>

> <O8xNA$GTHHA...@TK2MSFTNGP06.phx.gbl>
> <Y9H1TE3T...@TK2MSFTNGHUB02.phx.gbl>
> <eZargm4T...@TK2MSFTNGP06.phx.gbl>

> <Subject: Re: Received fax errors after running SFC.exe

> <Date: Tue, 13 Feb 2007 13:34:54 -0800
> <Lines: 162
> <X-Priority: 3
> <X-MSMail-Priority: Normal
> <X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
> <X-RFC2646: Format=Flowed; Response
> <X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
> <Message-ID: <eAivOb7T...@TK2MSFTNGP06.phx.gbl>

> <Newsgroups: microsoft.public.windows.server.sbs
> <NNTP-Posting-Host: rrcs-67-52-120-131.west.biz.rr.com 67.52.120.131

> <Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl
> <Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:16859
> <X-Tomcat-NG: microsoft.public.windows.server.sbs

[Nick]

Thanks to a reminder from 'SBS USer123' I am now running both modems on
Microsoft standard 56000bps drivers and guess what, exactly the same
problem! Does that suggest the issue is an SBSFax problem not fax modem
driver related?

Nick

""Inn Jin [MSFT]"" <v-in...@online.microsoft.com> wrote in message
news:ul$PBoKOH...@TK2MSFTNGHUB02.phx.gbl...
> Hi Nick,
>
> Thank you for updating and thank Gregg's input.
>
> Please notice that, installing driver and changing another modem doesn't
> mean that it is related to the hardware issue 100% percent. Just want to
> isolate the cause which can help us to solve the issue in a efficient
> manner. Both of us has the same purpose, that is to solve this issue, and
> what I want to do is try all my could to help you solve the issue. Your
> cooperation is appreciated. Remember, installing the driver and changing
> another modem is just for test purpose and temporary!
>
> I have found the website of your modem vendor in the URL below for your
> reference, you may download the driver and installed them.
>
> http://www.usr.com/support/s-main-menu.asp
>
> Meanwhile please try to unplug one modem and keep just one on the line,
> then test the issue. Then exchange them and try again. Please replace the
> telephone line then try again. Do you have some fax software? if so,
> please
> try to uninstall and reinstall it just for test purpose.
>
> Also please follow the steps below to collect T30 log for further test.
>
> a) Run regedit.exe.
>
> b) Navigate to this key:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fax\Device
> Providers\{2172FD8F-11F6-11D3-90BF-006094EB630B}
>
> c) Create new or modify values as follows:
>
> value name: DeBugLevelEx
> value type: REG_DWORD
> value: 0xffffffff
>
> value name: DebugContextEx
> value type: REG_DWORD
> value: 0xffffffff
>
> value name: DeBugFormatEx
> value type: REG_DWORD
> value: 0xbbffffff
>
> d) Please reproduce the issue and zip the C:\Documents and
> Settings\NetworkService\Local Settings\temp folder as a .zip file.
>
> e) Undo the registry changes.
>
> f) Please send the file to me at v-in...@microsoft.com
>
> I appreciate your effort and cooperation. I'm looking forward to your
> reply.

>
> Have a nice day!
>
> Best regards,
>
> Inn Jin (MSFT)
>

[Robert Li [MSFT]]

Hi Nick,

Thanks for updating.

Some hardware not in the HCL can use Microsoft standard drive. But that
doesn't mean that hardware can work familarly with Microsoft software.
Please kindly change your modem which is in the HCL list. If the problem
still exists, I will try my best help you. Thanks for understanding.

Best regards,

Robert Li(MSFT)

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.

--------------------

<From: "Nick" <NoS...@Nowhere.com>
<References: <#1AqSB0M...@TK2MSFTNGP04.phx.gbl>

<FQBaOB7M...@TK2MSFTNGHUB02.phx.gbl>
<e67ctlBN...@TK2MSFTNGP02.phx.gbl>
<SF#tnEMNH...@TK2MSFTNGHUB02.phx.gbl>
<e#3oJrmNH...@TK2MSFTNGP04.phx.gbl>
<GXwOR89N...@TK2MSFTNGHUB02.phx.gbl>
<O5TTUABO...@TK2MSFTNGP04.phx.gbl>
<y7HvtrFO...@TK2MSFTNGHUB02.phx.gbl>
<uSznWhJO...@TK2MSFTNGP03.phx.gbl>
<ul$PBoKOH...@TK2MSFTNGHUB02.phx.gbl>

<Subject: Re: Received fax errors after running SFC.exe

<Date: Thu, 15 Feb 2007 11:35:13 -0000
<Lines: 104

<X-Priority: 3
<X-MSMail-Priority: Normal
<X-Newsreader: Microsoft Outlook Express 6.00.3790.2826

<X-RFC2646: Format=Flowed; Original

<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826

<Message-ID: <OieoeVPU...@TK2MSFTNGP04.phx.gbl>
<Newsgroups: microsoft.public.windows.server.sbs
<NNTP-Posting-Host: host86-145-13-211.range86-145.btcentralplus.com
86.145.13.211
<Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
<Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:17229
<X-Tomcat-NG: microsoft.public.windows.server.sbs

[Gregg Hill]

Nick,

You have been fighting with this problem for almost a month and a half.
Whether you like it or not, you will continue to waste time and lose money
until you meet their terms. Buy an approved modem!!! and then they will help
you.

You are most likely correct that it is not a hardware issue, but unless you
use an approved modem, they DO NOT CARE to try any further. So, what are
your choices? You could re-install SBS from scratch, or upgrade to SBS R2 so
you have the latest disks and can remove/reinstall whatever you need, or buy
a $110(USD) external modem of which they approve and get the support you
need. Hmm...which is cheapest and takes the least time?

STOP WASTING YOUR TIME AND MONEY trying to convince them that it is a fax
service issue and not caused by hardware. Just meet their requirement of an
approved modem, then work from there. It will cost you a whole lot less than
you have already wasted in time lost when you could have been billing.

As I said before, you will need to buy one of those approved modems, install
it, have it not work, then ask again for help. I understand that you are
convinced it is not hardware, and I believe you, but they are not going to
budge. Get an approved modem (or a Brooktrout board).

Look at these modems
http://www.windowsservercatalog.com/results.aspx?&bCatID=1459&cpID=1415&ocID=0&OR=1.

MultiTech is a good brand, and they are "Designed for Microsoft Windows
Server 2003."

You need to stop fighting a battle you cannot win, buy an approved modem,

then ask again for help.

One more note about the Brooktrout board. Have you read my posts to which I
referred a few weeks ago? I had a huge failure rate using any of three
models of USR Courier V.Everything external modems (002806-00, 3CP3453, and
3453B), or a MultiTech MT5634ZPX-PCI modem, and an off-brand external modem.
NOTHING worked well. I then installed a Brooktrout TruFax board and it has
****not failed to receive or send**** a fax since the day it was installed
on January 13th.

Stop pounding your head against a brick wall...the wall is going to win
every time. Buy one of those approved modems, install it, and if it fails to
work, then ask again for help. You can jump up and down yelling "I told you
so" after that if it makes you feel better, but you still need to do it to
get any more help.

Gregg Hill

"Nick" <NoS...@Nowhere.com> wrote in message

news:OieoeVPU...@TK2MSFTNGP04.phx.gbl...

[Gregg Hill]

No, it does not.

See "Re: Best fax modem settings to receive from multifunction devices?"
dated 12/21/06 at 12:09AM.

Then read the rest of the thread, as well as this one "Brooktrout TruFax
card questions."

Gregg Hill

"Nick" <NoS...@Nowhere.com> wrote in message
news:OieoeVPU...@TK2MSFTNGP04.phx.gbl...

[Robert Li [MSFT]]

Hi Nick,

Thanks for updating.

Please kindly change a new modem in HCL. I will try my best helping.

Have a nice weekend.

Best regards,

Robert Li(MSFT)

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.

--------------------

<Reply-To: "Gregg Hill" <bo...@nowhere.com>
<From: "Gregg Hill" <bo...@nowhere.com>

<References: <#1AqSB0M...@TK2MSFTNGP04.phx.gbl>
<FQBaOB7M...@TK2MSFTNGHUB02.phx.gbl>
<e67ctlBN...@TK2MSFTNGP02.phx.gbl>
<SF#tnEMNH...@TK2MSFTNGHUB02.phx.gbl>
<e#3oJrmNH...@TK2MSFTNGP04.phx.gbl>
<GXwOR89N...@TK2MSFTNGHUB02.phx.gbl>
<O5TTUABO...@TK2MSFTNGP04.phx.gbl>
<y7HvtrFO...@TK2MSFTNGHUB02.phx.gbl>
<uSznWhJO...@TK2MSFTNGP03.phx.gbl>
<ul$PBoKOH...@TK2MSFTNGHUB02.phx.gbl>

<OieoeVPU...@TK2MSFTNGP04.phx.gbl>

<Subject: Re: Received fax errors after running SFC.exe

<Date: Thu, 15 Feb 2007 11:13:53 -0800
<Lines: 122
<X-Priority: 3
<X-MSMail-Priority: Normal

<X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
<X-RFC2646: Format=Flowed; Response

<Message-ID: <euCqvVTU...@TK2MSFTNGP06.phx.gbl>

<Newsgroups: microsoft.public.windows.server.sbs
<NNTP-Posting-Host: rrcs-67-52-120-131.west.biz.rr.com 67.52.120.131
<Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl

<Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:17350
<X-Tomcat-NG: microsoft.public.windows.server.sbs