6.5 Client Connectivity

[skibum019]

We have some very strange behavior with our 6.5 implementation.  We are running 6.5 on two physically identical Windows 2008 R2 servers.  Both servers are logging to their own Citadel databases and operate independently of each other.  This way if one server drops or is in need of maintenance, we can restore trace data from the other server and maintain continuity in the trending on each server.  On the client side, I have configured clients to monitor a tag on the "Primary" server and if the tag goes to false or bad quality, the client will automatically switch over to monitor from the "Backup" server.  In addition, I have given the clients a manual switch that allows them to override this logic and to manually switch over to the backup server.  This all works great and as expected.  The problems we are seeing are inconsistencies in the communication between clients and servers.  Some clients can connect to the primary server no problem.  Some cannot.  Some can view live data from the primary, but only view the hypertrend data from the backup.  Some can view both from the primary and after some time, they will lose that connectivity.  The only difference in software between the primary and backup server is that the primary server has Backup Exec Remote Agent installed for backing up data to a tape drive.  I have one client in particular that cannot connect to the primary server at all, I have tested with tag monitor and cannot browse the primary server, but the backup server is no problem.  Servers both have firewalls turned off and do NOT have any other protection software running (A/V, etc...) that would interfere.  I have used the "LOGOS.ini" fix that has been referenced in this forum by others, and we are still having the problem.  Logos.ini is configured on both servers and clients as below:

[logos]
Global.DisableLogosXT=True

I have tried systems with and without the above logs.ini fix but still have problems.

Anybody out there have any ideas?

[mammoth]

Sorry cant help with this

[skibum019]

Weird, this is still an issue, but I have an update.

We found a Windows XP computer that was a fresh install.  No firewall, no antivirus installed.

Computer would not enumerate tags, nor would it display values or hypertrends in Lookout.

Added the Logos.ini file to the computer and restarted.  No change.  Could not enumerate tags in Shared Variable Monitor, no values in Lookout.

Registered the IP address for the primary server in Shared Variable Monitor.  Once this was done, I could enumerate tags.  Opened Lookout and values and hypertrends were working.

Tried the same thing for the backup server, registered IP address, no luck.  Could not enumerate tags through the DNS name or the IP Address.

Lookout was still running in the background on the primary server.  After about 5 minutes, it stopped working.  With Shared Variable Monitor still open, refreshed and tried to enumerate tags under the primary server and it again failed.

What in the world is going on with the communications here???