The purpose of this article explains some reasons why A1-Law might not connect to the A1Comm service.
Instructions
1. First, make sure you have the latest version of A1Law (click Help,
check for web updates).
2. If the problem is on ALL COMPUTERS in the office and no one can
connect:
2A Try shutting down A1Comm and start it
up again
2B Make sure the Listen button was clicked
and A1Comm is currently up and running
2C Make sure no firewalls are blocking
A1Comm. Try disabling Windows Firewall as a test and if it works you will
then need to add A1Comm to the list of exceptions.
2D At A1Comm, click Options, Enable A1-Law
for use with A1Comm.
2E Try pinging the server's IP address from
the command prompt at a workstation to make sure there are no firewalls blocking
communication. Example, ping 192.168.1.10
2F If there is more than one network card
on the server, try disabling the second network card to test and see if there is
a conflict.
2G If it works for a short time on all
workstations and later stops working then check to make sure the power
management for the network card is not in use. The network card should be
set to always on.
3. If the problem is specifically with one workstation and only that station cannot connect:
3A.Register the controls (click tools, miscellaneous,
register controls when all windows are closed in A1-Law).
You may also register the two controls manually instead while outside of
A1Law by clicking Start, Run, regsvr32 c:\lawlocal\controls\FTPX.OCX
and regsvr32 c:\lawlocal\controls\FTPX.DLL
They must both display Success when registering the controls.
3B. Try disabling the windows firewall or any other firewall and see if that resolves the problem.
3C. At the sign on screen, click Setup, Setup Locations and double click the location and make sure Never Use the A1-Comm server is UNCHECKED.
3D. Go to the Device Manager click Network Cards and check
to see if there are two network cards in the computer.
If so, try disabling one of them by right clicking it (perhaps the second
one in the list) and click Disable and see if that resolves the problem.
3F Try pinging the server's IP address from the command prompt at a workstation to make sure there are no firewalls blocking communication. Example, ping 192.168.1.10
4. See setting up the A1Comm program
article for more information on general setup and ideas.