04-12-2006 10:30 PM
04-14-2006 11:00 AM
Hi Bob,
It sounds like there may be some issue with the Firewall or the Logos Protocol being blocked. Check out the following links to see if these might help.
Setup Guidelines For The Logos Protocol Across Firewalls
http://digital.ni.com/public.nsf/websearch/F0DE7A1A88D92D6D86256D710049FB40?OpenDocument
Using Lookout, LabVIEW DSC Module, and Network-Published Shared Variables with Firewalls
http://digital.ni.com/public.nsf/websearch/8AE45BBFA1D7025E862570F200642FD8?OpenDocument
Networking Lookout or the LabVIEW DSC Module Across Firewalls
http://zone.ni.com/devzone/conceptd.nsf/webmain/7D0E7F20B1A7C8E486256A39005747F2?opendocument
Hope this helps,
Best Regards,
Steven B.
04-20-2006 05:31 PM
Steven,
Thanks for the info. The links helped me somewhat understand the Logos part of the Client/Server communications.
All systems are W200o. The Logos ver. on the Server is 4.5.1 and on the Clients it is 4.3 and 4.4 (2 systems)
I don't believe its a firewall problem. I can set it to 'Pass All' with no improvement. I can log all firewall activity and no IP or Port blocking is shown.
The VPN is intended to provide a tunnel through the firewall using encryption/decryption algorithms rather than IP/Port # blocking.
Furthermore, the Client sees the Server process and all the objects within the process. (Through the VPN) However, it does not see data from the database even for the same object names.
I'm currently tryng MAX to view databases. I can see all local databases (ie same subnet) but cannot see remote ones.
???
Bob
04-21-2006 10:39 AM
06-09-2006 12:28 PM
Well the problem had nothing to do with the VPN or firewalls. It was simply a network issue.
Adding lines such as '192.168.0.3 Look2' to the 'hosts' file solved all the issues. This allowed 'ping look2' to work correctly across the VPN.
Within the hypertrends the IP address was replaced by the computername and all worked OK.
File in question for W2000 is at C:\windows\system32\drivers\etc\hosts
Regards,
Bob
11-15-2006 12:26 AM
11-15-2006 12:06 PM
??? break again???
How so? I didn't think my problem had anything to do with Lookout or Citadel. My Client machine simply could not resolve the Servers ComputerName with its IP address. IP addresses worked OK for Lookout client to server requests for current pot values etc.
However a hypertrend requests data from Citadel. And the trace names within Citadel include the ComputerName NOT the IP address. So unless the Client knows and uses the correct ComputerName, Citadel won't have it.
Regards,
Bob
11-15-2006 08:33 PM