I have a datasocket based OPC client written in LabVIEW 8.6.1 that behaves a bit strangely; if I run the server on PC "A" and the client on PC "B" everything runs fine. The OPC Client can connect to the server on the other PC...as well as local OPC servers. If however the client runs on PC A and the server on PC B...the OPC client can browse the OPC tags on the remote server, but it is not able to read them.
At first this might sound as a DCOM or firewall issue, but the firewalls are disabled and OPC clients from other suppliers (Matrikon and others) are able to read data in the scenario where the datasocket client fails....so it does not seem like a DCOM issue.
I ran an OPC security settings analyzer to see if I could fine any differences - and I do; the PC that is unable to run the client reports that it does not get access to the remote registry...and this access is fine the other way around. I found this knowledge base entry here that talks about just this kind of problem: http://digital.ni.com/public.nsf/allkb/5C8A90CD57B279F286256C2C006F1EB4
The thing though is that if I check the access rights there does not seem to be a difference - I cannot find what is restricting the access....and another question is whether this can still be the problem when there is no problem browsing the OPC tags(?).
Does anyone have any tips on how to find and fix the problem...and/or are there any changes in LV2009 that would make the OPC client behave more like the clients from other suppliers?
