Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
|Source: Microsoft Shared Fax|
The Shared Fax Service failed to receive a fax. From: <caller fax number>. <caller id>. To: <receiver fax number> Pages: <pages number> Device Name: <device name>
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
Jonathan L. Green
Although I would receive this message occasionally, I started to receive this error more frequently after I installed Win2K Service Pack 4 and other updates. I finally solved the problem by changing the modem Data Connection Preferences to a Port speed of 19200. “Control Panel -> Phone and Modem Options -> Modems tab -> Properties -> Advanced tab -> Change Default Preferences -> change the Port speed to 19200”.
This event occurs when a modem is not fully compatible with Small Business Server 2000. From a newsgroup post:
"It appears that modems which are classed as Group 3, Class 1 will not work in SBS, even though they work in the W2K environment with other fax software such as Win Fax Pro, etc. I switched to a MultiTech MT5600ZDXV, and it has worked without a hitch ever since. This modem is supports both class 1 and class 2 protocols, so you have backward support and SBS Shared Fax Services works wonderfully."
This error also happens when the calling party hangs up during the initialization phase of the fax transmission.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated