Managed by the FaxBack Support Team
This article applies to NET SatisFAXtion 8.5 and 8.6


Client / Server Connection problems
Affects: WinFax Clients and Administration installation on a work station, usually on a segmented LAN

Attempting to log-on to the Administration program, a Server Error is presented, stating A general failure to establish a connection has occurred.


If the fax server is fully loaded, this is always a network configuration problem. If you have dual NIC's (including "virtual" NIC's, Wan adapters, etc.) in either the fax server or client, and the first one in the binding order is used to connect to the internet, not your LAN, then the order of those NIC's must be swapped, because both the server and its clients will bind to the first available NIC in the list, and search out on the internet for client/server rather than the LAN.

Note that a missing AdminData folder can cause a General Failure to establish a connection error, loading the Administration program
Check that [DRIVE]:\Program Files\NET SatisFAXtion\AdminData is present on the server or workstation where Administration is installed


Check the binding order of both the fax server and the machine on your LAN, to make sure the NIC (Network Interface Card) you are expecting to be using is the first in the binding order
If you are using Win 2000, 2003 or XP, Right click on My Network Places and select Properties.

From the top toolbar, select Advanced - Then Advanced SettingsGeneralFailure02.gif
Make sure Local Area Connection (or the one with the IP address on your flat LAN you expect to be using) is at the top
Use the arrows to the right of "Connections" to move the desired Device to the top.
Select OK and try to log-on to the fax server again

If that is not the case, then the client workstation and server must be on different subnets connected
by a router or a switch, which typically block broadcast IP packets. The server broadcasts IP packets
on the LAN to prospective clients. That is how it is found by the clients, and how connections are

To get around the blocking problem caused by a router or switch, you have to hard code the server IP
address on the client. This is set in two registry keys in the client via the registry editor at
hkey_current_user\software\faxback. Set the server's IP address for the "primary_server_ip_address"
parameter in the cas20 and logondialog keys, then reload the client (Winfax, Admin, etc.).

Note that this assumes that IP is properly installed and working on both the fax server and client
workstations. Both the server and client machines must be able to ping each other on the LAN. If
you cannot, then this is an indication that basic IP connectivity on the LAN is not functioning correctly.
This must be resolved first.

EXAMPLE: (Where is an example IP address. Enter your fax servers IP address in it's place

32 bit machines
"primary_server_ip_address" = ""

"primary_server_ip_address" = ""

64 Bit machines

"primary_server_ip_address" = ""

"primary_server_ip_address" = ""



Use this utility to set the IP address of the Fax Server on a client or 2 box 8.x E-Mail Gateway (32 bit machines only)

If, for whatever reasons, you cannot get IP working successfully on your LAN, then you can try another
protocol such as IPX/SPX, or NetBEUI. These protocols will need to be used on the Server and all the clients, as needed.

XP Internet Connection Firewall and IPv6 Internet Connection Firewall
Both of these personal firewall services can stop Administration and WinFax from logging onto the fax server, yielding a "General Failure to establish a connection" error.
Stop these service(s) (which ever ones exist on your installation) to connect to the fax server. Set these services to Manual so they do not start again next time you reboot.


Copyright © FaxBack, Inc.