Lookout

cancel
Showing results for 
Search instead for 
Did you mean: 

Lookout 6.2, no hypertrend traces on remote clients

I've looked over numerous threads & posts, but can't figure this out.  This is the same problem that many have reported before.  I cannot see hypertrend traces in my client process for remotely running clients.  When the client is on the same computer as my server, the traces appear just fine.  Right now, I have firewalls turned off.  Running MAX on my remote client won't display my server computer, therefore I can't access the citadel database.  Also, I can log remote client data into the database just fine (a slider pot on the remote client will log data to the database on the server machine).  So, I know I've specified the correct database name for the client.

 

Hopefully, someone (Ryan Smiley Wink) can send me a checklist of things to verify/try.

 

Thanks,

Ken

0 Kudos
Message 1 of 7
(6,649 Views)

If you don't see the server computer in MAX from client computer, you can register the server manually. RIght click on "Network" and register.

 

And then try to expand the server computer. Do you see the databases on it? Do you see the traces in the database?

 

The broken connection to remote database is usually caused by the firewall.

Ryan Shi
National Instruments
0 Kudos
Message 2 of 7
(6,623 Views)

Ken,

 

Can you please post the URL in the trend.  (Just realized I didn't read it correctly, may disregard.)

 

Also, is this the same Ken working at Cal-Poly?

 

Thanks,

Mike

-----------------------------------------------------------------------
Forshock - Consult.Develop.Solve.
0 Kudos
Message 3 of 7
(6,604 Views)

 

Yes-sir-ree, I am at Cal-Poly.  Should be finishing up soon.  Have we met?

 

-Ken

0 Kudos
Message 4 of 7
(6,591 Views)

Hi Ryan,

 

I did register all computers.  The firewalls are disabled on both computers.  Also, I can ping (from command windows) between computers just fine.  And they are on the same sub-network.  I'm fairly certain that the client is attaching to the database on the server correctly:  If I start the client process while the network is down, it puts up a message that the database is unavailable and Lookout changes to the default database created on the client system.  I don't get this message when the network is up, and I've reset to use the database on the server computer.  I think I'll test again with new, minimal client & server processes, similar to the tutorial exercise.

 

Any other ideas?

 

thanks,

Ken

 

0 Kudos
Message 5 of 7
(6,589 Views)

Ken,

Yes we've met quickly, at Cal-Poly I work with Destek/DTS.

 

(Sorry back to topic)

 

Mike

-----------------------------------------------------------------------
Forshock - Consult.Develop.Solve.
0 Kudos
Message 6 of 7
(6,559 Views)

When you browse the remote database from client in MAX, does the database appear under the registered server computer? Can you see all the traces?

 

Are both server and client Lookout 6.2?

 

What if you browse the database on client computer from the server computer in MAX? There is the default database on client.

 

I think the first step is to make the browsing work in MAX. If you can browse the remote database and see all the traces, the Citadel communication is good.

Ryan Shi
National Instruments
0 Kudos
Message 7 of 7
(6,548 Views)