I switched from (2) 12$ el-cheapo modems to a 8 Port digi modem card. My old modem cards misread probably 1 in 50 faxes. With this Digi board probably 3/4 of them are only partialy recieved. I fixed the baud rate to a lower speed, that has not fixed the problem. Any suggestions?
I am having the same problem. I am running windows server 2003 sp1 with standard windows fax services. I get the following error:
An incoming fax could not be received due to a reception error. Only part of the incoming fax was received. Contact the sender and request that the fax be resent. File Name: C:\Documents and Settings\All Users\Application Data\Microsoft\Windows NT\MSFax\Queue\1C6AF6C9722B2.tif. From: Special Promotion. CallerId: . To: Mazer Corporation. Recovered Pages: 1. Total Pages: 2. Transmission time: 0:00:43. Device Name: Digi AccelePort RAS Modem.
This is typical. Some of the testing that I have done has been to send from another fax. I get the entire fax but I still see the event log error. It says two pages when All I really sent was one. What’s up with that? I have reduced modem speed. and I am running the current driver version. I am going to update the firmware in the morning to see if that will help
I too am having the same problem. As the data below shows, I’ve lowered the baud rate as low as 9600, but it’s currently set at 19200. Occassionally a fax will come through with no errors, but I don’t see the difference (in logs) from a good one or a bad one - and what’s more frustrating is that I don’t actually see anything wrong with the faxes, but I also don’t like a log full of error messages. Anybody have ideas?
OS Name Microsoft(R) Windows(R) Server 2003, Enterprise Edition
Version 5.2.3790 Build 3790
The driver for the modem is Digi 5.0.314.0
The other modems share this same configuration (other than addresses, of course):
Name Equinox V.90 MultiModem
Description Equinox V.90 MultiModem
Device ID Modem1
Device Type External Modem
Attached To COM4
Answer Mode Not Available
PNP Device ID Not Available
Provider Name Equinox
Modem INF Path oem2.inf
Modem INF Section MultiModem
Blind Off X4
Blind On X3
Compression Off %C
Compression On %C3
Error Control Forced \N2
Error Control Off \N
Error Control On \N3
Flow Control Hard &K3
Flow Control Off &K
Flow Control Soft &K4
DCB
Default <
Inactivity Timeout 0
Modulation Bell B1
Modulation CCITT B
Prefix AT
Pulse P
Reset ATZ
Responses Key Name Equinox V.90 MultiModem::Equinox::Equinox
Speaker Mode Dial M1
Speaker Mode Off M0
Speaker Mode On M2
Speaker Mode Setup M3
Speaker Volume High L3
Speaker Volume Low L1
Speaker Volume Med L2
String Format Not Available
Terminator
Tone T
A snippet from the modem log shows:
08-08-2006 14:30:29.846 - 19200,8,N,1, ctsfl=1, rtsctl=2
08-08-2006 14:30:29.846 - Initializing modem.
08-08-2006 14:30:29.861 - Send: AT
08-08-2006 14:30:30.033 - Recv: OK
08-08-2006 14:30:30.033 - Interpreted response: OK
08-08-2006 14:30:30.049 - Send: AT &F E0 V1 &D2 &C1 S0=0 S95=41
08-08-2006 14:30:30.221 - Recv: OK
08-08-2006 14:30:30.221 - Interpreted response: OK
08-08-2006 14:30:30.236 - Send: ATS7=60S30=0L0M1\N3%C3&K3B0N1X4
08-08-2006 14:30:30.408 - Recv: OK
08-08-2006 14:30:30.408 - Interpreted response: OK
08-08-2006 14:30:30.408 - Waiting for a call.
08-08-2006 14:30:30.424 - Send: ATS0=0
08-08-2006 14:30:30.596 - Recv: OK
08-08-2006 14:30:30.596 - Interpreted response: OK
08-08-2006 14:30:43.283 - 19200,8,N,1, ctsfl=1, rtsctl=2
08-08-2006 14:30:43.314 - Initializing modem.
08-08-2006 14:30:43.330 - Send: AT
08-08-2006 14:30:43.501 - Recv: OK
08-08-2006 14:30:43.501 - Interpreted response: OK
08-08-2006 14:30:43.517 - Send: AT &F E0 V1 &D2 &C1 S0=0 S95=41
08-08-2006 14:30:43.705 - Recv: OK
08-08-2006 14:30:43.705 - Interpreted response: OK
08-08-2006 14:30:43.720 - Send: ATS7=60S30=0L0M1\N3%C3&K3B0N1X4
08-08-2006 14:30:43.908 - Recv: OK
08-08-2006 14:30:43.908 - Interpreted response: OK
08-08-2006 14:30:43.908 - Waiting for a call.
08-08-2006 14:30:43.923 - Send: ATS0=0
08-08-2006 14:30:44.079 - Recv: OK
08-08-2006 14:30:44.079 - Interpreted response: OK
08-08-2006 14:31:57.483 - Recv: RING
08-08-2006 14:31:57.483 - Interpreted response: Ring
08-08-2006 14:31:57.483 - TSP(0000): LINEEVENT: LINE_NEWCALL
08-08-2006 14:31:57.483 - TSP(0000): LINEEVENT: LINECALLSTATE_OFFERING
08-08-2006 14:31:57.483 - TSP(0000): LINEEVENT: LINEDEVSTATE_RINGING(0x1)
08-08-2006 14:31:57.483 - TSP(0000): Entering Passthrough Mode
08-08-2006 14:31:57.483 - Passthrough On
08-08-2006 14:31:57.483 - TSP Completing Async Operation(0x000101d0) Status 0x00000000
08-08-2006 14:31:57.483 - TSP(0000): LINEEVENT: LINECALLSTATE_CONNECTED
08-08-2006 14:32:49.169 - TSP(0000): Dropping Call
08-08-2006 14:32:49.169 - Passthrough Off
08-08-2006 14:32:49.169 - 19200,8,N,1, ctsfl=1, rtsctl=2
08-08-2006 14:32:49.169 - Initializing modem.
08-08-2006 14:32:49.185 - Send: AT
08-08-2006 14:32:49.341 - Recv: OK
08-08-2006 14:32:49.341 - Interpreted response: OK
08-08-2006 14:32:49.357 - Send: AT &F E0 V1 &D2 &C1 S0=0 S95=41
08-08-2006 14:32:49.529 - Recv: OK
08-08-2006 14:32:49.529 - Interpreted response: OK
08-08-2006 14:32:49.544 - Send: ATS7=60S30=0L0M1\N3%C3&K3B0N1X4
08-08-2006 14:32:49.732 - Recv: OK
08-08-2006 14:32:49.732 - Interpreted response: OK
08-08-2006 14:32:49.732 - Waiting for a call.
08-08-2006 14:32:49.747 - Send: ATS0=0
08-08-2006 14:32:49.904 - Recv: OK
08-08-2006 14:32:49.904 - Interpreted response: OK
08-08-2006 14:32:49.904 - TSP(0000): LINEEVENT: LINECALLSTATE_DISCONNECTED(0x1)
08-08-2006 14:32:49.904 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE
08-08-2006 14:32:49.904 - TSP Completing Async Operation(0x00010169) Status 0x00000000
08-08-2006 14:32:49.919 - TSP(0000): Closing Call
The event log in Windows reports:
An incoming fax could not be received due to a reception error. Only part of the incoming fax was received. Contact the sender and request that the fax be resent. File Name: C:\Documents and Settings\All Users\Application Data\Microsoft\Windows NT\MSFax\Queue\1C6BB244C366D.tif. From: 5555555555. CallerId: . To: COMPANYNAME. Recovered Pages: 3. Total Pages: 4. Transmission time: 0:01:07. Device Name: Digi AccelePort RAS Modem #4.
Thanks again for your anticipated help.
What operating system? What version of driver? What does “ATI3” done on the Digi modem output back? Also, what fax software are you using?
ATI1 - 255
ATI2 - OK
ATI3 - V80006691_M3P-K56_DS
ATI4 - DIGI56K_RAS
ATI5 - 022
ATI6 - 3.29K1/5.60A
ATI7 - 000
Windows 2003, Standard MS Fax Software,windows driver 3.10.225.0
Please download and install the latest drivers. The driver which ship with Windows are drivers we gave Microsoft in 2002 (or earlier). The current driver version is 5.0.314.0 and can be obtained here:
http://www.digi.com/support/productdetl.jsp?pid=1488&osvid=58&tp=1&s=10
Be sure to follow the installation instructions in the readme.txt file precisely.
This will also install a newer firmware version automatically.
When setting up the Fax program be sure to configure for Class 2 and 2.0 only. The modems do NOT support Class 1 faxing.
For rdoherty and millarar,
This behavior was the norm in Windows 2000. The version of MS fax included in Windows 2000 was written and tested using a modem which implemented a non-standard end of page function for received faxes. When using an AccelePort RAS modem, the fax would be received, but an error was generated indicating that the fax was not completely received.
I have not seen this error in Windows Xp or Windows Server 2003.
In you Windows Server 2003 installations, did you upgrade from Windows 2000 or are these fresh installations?
When you installed the newer drivers, did you uninstall the old drivers, run the dgarcln.cmd utility and then reinstall the new driver?
If any shortcuts were taken, the new drivers may not be completely installed. Also, since these drivers are not signed, you have to install the new driver for the adapter, for each serial port and for each modem.
You must always select do NOT install from the internet, install from a specified location (Advanced) and select the directory with the newer drivers in it. I would recommend that you go through the driver installation again.
Please note: I do not know if you performed an upgrade from Windows 2000 to Windows Server 2003, if the problem with the MS Fax program will be resolved.
async-man,
In my case, this is a “clean” 2003 install, I quote that because it’s on a installation CD that comes with the server from Dell. Out of curiosity, I’ve tested this on a clean (straight off 2003 CD, then fully patched (sans R2) machine and received the same results. After R2 installation, again, the results persisted.
I, to be sure, went back and uninstalled each device on our initial machine, ran dgarcln.cmd, rebooted, and installed the new devices by hand, selecting the three proper drivers one by one; and the results are the same.
I think the phrase “gg” comes into play here, as I’m at a total loss. I’d write it up to hardware failure, but as of now there aren’t any actual problems with the faxes, and another person seems to be having the same problem.
Any other suggestions?
And thanks, again.
You could check the for shared hardware resources or resouce conflicts. The easiest way is to go to Start Run winmsd , hardware resources, shared/coflicts.
What is model of Dell system you are using?
It is probably best if you contact Tech Support and open a case. You can do it online here:
http://www.digi.com/support/eservice/eservicelogin.jsp
Please include the serial number and the country in which the adapter is installed, as we make different hardware versions for various countries and regions.
I was searching google and found this thread. We are seeing the exact same problem as you are. About 70% of the incoming faxes show as not receiving the entire fax. None of my users have complained, but I dont like the errors. I have tested this on 3 completely seperate systems at different locations all using this the Accelerport RAS 4 port fax card. Latest drivers and firmware. Funny thing is a cheap of Conxeant modem installed by Dell has no problems.