[Administrator]

@BillM wrote:

Okay, we got the salesman his own separate line. We have strange dialing here, and I just cannot get this to work. Some of the locations within our area code require a 1-area code-number plus our long distance acces code which is a 4 digit number. I have spent all week fooling with this and feel like a total retard as I cannot get this to dial anything but a local number. Any help would be greatly appreciated.

You need to configure a specific dialing configuration in WinFax, so it will dial any access code that you require depending if the number is long distance or not.

There are two methods of dialing in WinFax. Windows dialing and WinFax dialing. Windows dialing settings are universal to all Windows applications, WinFax dialing is specific to WinFax only.

Windows dialing is very flexible, so I would suggest trying Windows dialing first. To enable Windows dialing in WinFax,

Open the Message Manager, and then click Tools.
Click Program Setup.
Select “Dialing and Location,” and then click Properties.
On the General tab, click Advanced.
Select Windows Dialing, and then click OK.
Click Close to close the Program Setup.

You can then configure the specific dialing rules in the Windows dialing setup.

[Administrator]

@pmarsh wrote:

I’ve been digging around trying to find a solution to my problem. I just found a post on another group that states the following.

You can’t use ip addresses with either 0’s or 1’s by them selfs in an octet because WinFax will change the system MAC.

WTF are they out of their minds.

Check out this Symantec link.
http://service1.symantec.com/SUPPORT….&csm=no

WHO WAS THE BRIGHT ONE WHO DID THIS CODING????

Would someone like to call Symantec tech support and inform them of the most commonly used private ip schemes????

Man it just keeps getting funnier and funnier.

I have no idea where they get this problem with “1”s and “0”s in the IP address. How can WinFax change the system’s MAC address?

Did you try this? What is the IP address (sub-net) of your network? are you connecting with an IP address, or computer-name?

also, if your using NAV, do you have Norton Internet Security as well? Firewall, and or Worm protection turned on? That is a possible issue preventing connections to the Host machine.

[Administrator]

@Tis Sedo wrote:

Thanks for the info.
I’ve installed Conexant modem(Dell Smart HSFi V92), and so far everything works! I’ll keep you posted.
Thanks again!

Good to hear , Conexant (formally Rockwell) type modems are a good choice with WinFax.

Avoid: pcTEL, ESS type modems.

[Administrator]

@bpaspeed wrote:

I went Control Panel>Settings>Modem>Modem Properties>
Diagnostics (COM2) Generic SoftK56 Data, Fax, Voice>
More Info> Port: COM2, Address: 2F8, Identifier:
CXTVEN_14F1&DEV_2F00&SUBSYS_200514F

Then I went WinFax PRO Program Setup>Modems and Communications Devices>Properties>Generic SoftK56 Data, Fax, Voice (TAPI port active)>Properties>Fax>Regular or Cellular PCS modem>Max. trans. speed: as fast as possible. Min. trans speed: send at any rate. High-speed compression enabled (2D).
Initialization string sequence: AT&F&D2&C1+IFC+2,2;S7=55.
Flow Control AT+IFC=2,2;
Hardware flow control enabled. Reset: ATZ. [Thanks]

Problems sending to a specific fax machine is difficult to determine, you can turn DEBUG mode on in WinFax, this will generate a log to determine what exactly is happening with the communication of the modem with the fax machine.
Once you’ve turned on Debug mode, you can then start using WinFax to attempt to send the fax to the Panafax machine.

See this document for instructions on how to enable and disable debug mode in WinFax PRO 10.0x

http://service1.symantec.com/SUPPORT….3134404

Then post the results of the debug log here for further review. Remember to turn debug mode off after you are done trying to send that fax to the Panafax machine.

[Administrator]

Since you mention everything >was< working fine, did you reboot both the Host machine first and then the client (make sure you start the Host first, and then reboot the client(s)) Usually a messed up DCOM connect causes the Fax Sharing to fail, and subsequent attemps to connect will fail unless you reboot the Host and Client(s) The object exporter message is a DCOM problem making a connection from the Client to the Host. Usually this is a TCP/IP related issue, but could be anything. If you’ve rebooted and the same problem exists, is there anything that has changed with the client machines, or the Windows 2000 machine acting as the Host?

[Administrator]

If your running a small network, a few PCs , then I would recommend using Static IP addresses on each machine and configure your router to use the 192.168.0.x sub-net. Example is Router, 192.168.0.1, Host Machine 192.168.0.2, Client Machine(s) 192.168.0.3, 192.168.0.4, 192.168.0.5 etc.

Also, you should be able to share files/ping each machine using computer name and IP address from the host and client(s) using TCP/IP protocol.

[Administrator]

Shabbs,

WinFax PRO 10.02 specifically with Windows XP has a problem with the SDK and the Printer Driver. I would suggest upgrading your version of WinFax to 10.03 which has been reported to correct the problem.

[Administrator]

You can try REGACCES.EXE in the WinFax directory and see if adding permissions help… worth a try

[Administrator]

What is operating system on Host and Client machine(s)?

[Administrator]

I believe DCCDA3I.DLL is an updated file . I am not aware of other updated files. This file contains most of the MAPI (Outlook) changes.

If it doesn’t say “10.03” under Help, About WinFax then it is not version 10.03

There is no LiveUpdate for WinFax PRO

Edited By Moderator on 1124980843

[Administrator]

You had verson 10.02, performed a LiveUpdate and version 10.03 was downloaded and installed?

[Administrator]

Have you looked at the Configuration Object?

Also part of the Send Object is SetDeviceName:

SetDeviceName Specifies the name of the device you want to use for this send job. If you are not sure of the name of the device you want to use, use the Configuration object to obtain a list of available devices.

Syntax: short SetDeviceName(BSTR sDeviceName)

BSTR sDeviceName – The name of the device you want to use for this send job.

[Administrator]

I wrote some code years ago that would automatically close the WinFax Controller, it used the Windows API function FindWindow and another (can’t remember the actual function name) but if I can dig it up I will post it here. It would be easy enough to change it to close any program, providing you have the Window handle, you can do it.

[Administrator]

try double-clicking the WFXCTL32.REG file in your WINFAX directory then restart Windows / WinFax

Also did you install as Admininstrator, and log-in as Administrator when starting WinFax?

[Administrator]

WinFax used to have pretty good integration with ACT software, but when Symantec sold the ACT product line, support for the two integrated products went downhill. I am not sure what type of integration is available with ACT & WinFax PRO 10.0, but its probably limited.

If ACT has its own programming (or macro type language) it is possible to develop some sort of link to automate the process)

[Author]

Posts