Re: Received fax errors after running SFC.exe

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-innjin@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:dzFk5HjOHHA.2024@xxxxxxxxxxxxxxxxxxxxxxxxx
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)

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.



.