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

Summary:
If you have a DEC PCI Ethernet DEC chip 21040 network adaptor or DEC PCI Ethernet DEC chip 21041 network adaptor and you power up the computer with the network cables disconnected Citect will not be able to communicate over the card. You can still communicate to the file server. 

Solution:
During testing of the LAN redundancy feature it was found that if you power up the a computer with a DEC PCI Ethernet DEC chip 21040 network adaptor and the 10 BASE T cable is removed Citect will not be able to communicate when you plug the cable back in. However you can still connect to a file server once you plug the cable back in. This was seen running Windows 95 talking to a Windows NT file server. This appears to be a problem with the auto detection of physical media of the DEC card and the booting of the NetBIOS interface on Windows 95. As the Windows 95 redirector does not use the NetBIOS API it seems to bypass this problem as that appears why you can still communicate to the network file server.

You can verify this problem by using a network protocol analyser. On startup and every 30 seconds the Citect client will try to connect to the Citect server, on a network protocol analyser you should see the calling protocol packets. When this problem occurs you will see no network packets. If you see this problem you must turn the computers power off and power on with all network cables attached.

This could also be a problem with other auto sense network cards. It is recommended that you always boot up the computer with the network cables attached. See also Q1888.

 

Keywords:
 

Attachments