by
wss » Wed Apr 05, 2023 9:17 pm
So comms between the PC and instrument seem to be okay at a hardware level (ping checks out) so most probably a Chemstation software issue, not communicating with the GC...
I know that if the interface metric is not set high enough (i.e. to '1') on the interface that is connected to the GC-MS, then that can sometimes cause problems with comms - here's a guide I just Googled:
https://www.windowscentral.com/how-change-priority-order-network-adapters-windows-10N.b. I assume you're using Windows...
There's also the firewall log you can check (usually at C:\Windows\System32\LogFiles\Firewall\pfirewall.log). Open it in Notepad and look for entries logging activity to the GC's IP address. If there's a lot of 'fails' (can't remember the exact word that MS uses to indicate a blocked connection in their logs) then you or your IT people will need to make some modifications to your firewall rules to allow GC traffic...
If you're running Windows 10 with E.02.02 I've spent many hours dealing with various weird compatibility issues. It's possible to get E.02.02 working fine, but for some reason different issues (mostly with networking as you've described) crop up on more or less identical installations. If you can upgrade to a currently supported version I'd recommend it, but obviously not the easiest or cheapest option.
Another thing that you might want to try if the above fails is to load up the “Agilent Connection Expert” (under Agilent IO libraries Suite) and select the LAN device under Instrument I/O. Click “Change Properties” and change the default protocol to SICL-LAN. I've found this has restored a system I'd given up on to working order in the past.