Applies To:
  • CitectSCADA 1.00 1.01 1.10 1.11 1.20 2.00 2.01

If you are using a 3Com Etherlink III network card on a Citect Client computer, under some conditions this computer may loose communications to the Citect Servers. The Citect Client will display the error 'No server could be found' and it will continuously try to connect to the server. If this is occurring you will see error 18 being returned from the LISTEN commands in the NetBIOS windows of the Server. If you reboot the Client Citect it will attach to the Citect Server correctly as the 3Com Etherlink III drivers will be reloaded.

If the Citect Client computer has failed under the above conditions then whenever it tries to connect to the Citect Server it will consume memory on the server. After a long period of time this will cause the Servers performance to degrade and start paging to disk. If the server runs out of memory it may cause the server to generate a General Protection Fault or to crash out to the DOS prompt.

Note that the Citect Server does not have to have a 3Com Etherlink III card installed to generate this problem. This problem will occur on the server if it is using any type of network card and one or more of its clients are using 3Com Etherlink III cards with old drivers.

Install the latest version of the drivers for the 3Com Etherlink III drivers. These drivers are available on the Citect BBS and from Microsoft.

See also Q1046