I have been trying to establish a network link between a Lookout Server and a Lookout Client over a RAS dialup connection, the connection is manually enabled. Disk and file access is working ok, but all Lookout expressions are dead with red crosses through them. I have tried using the IP number of the server machine instead of its name, but this makes no difference. Has anyone any experience of doing this or any help?
Unfortunately we don't seem to be able to get our setup to work in the fashion you have described.
I will explain further the hardware and software configuration we used.
The "server" PC was running WinNT4.0 SP6a with a copy of Lookout developer/server software installed and running. The "client" PC was running WinNT4.0 SP5 with a copy of Lookout developer/server software installed and running, both PC's have ethernet interfaces and TCP/IP setup and running. The two PC's were connected together with a UTP crossover cable and it was possible to browse the network and ping the "server" PC from the "client". A lookout process was then run on the "server" PC which used absolute addresses. This was then copied across the network to the "client" PC and run. T his worked correctly, next the "expressions" were changed to use the IP number of the "server" PC instead of it's name, this to worked correctly.
Now we removed the ethernet connection and used the "Dialup Server" facility of WinNT4.0. This again provided us with the ability to browse the network and to ping the "server" from the "client". However the "expressions" shown on the "client" copy of the Lookout process were not updating and had red crosses through them.
There does seem to be something extra that the ethernet connection was providing and Lookout uses that is not available as default whilst using a RAS connection, does anyone know what this something could possibly be?
Best Regards, David Crofts. Acquisition Systems Ltd.
Khalid wrote: > > . > > Hi David, > > See if you can ping the remote machine. This will establish that the > IP networking is fully functional as needed by Lookout. > > Rgds, > > Khalid
Did you ever get this problem resolved? I am using lookout 5.1 and all my etherneted clients work great. My on call staff dial up and and connect to my scada server remotely with either a land line or celular modem on a laptop. The connects are always good, networking solid, and ping is fine. If I let the laptop on dialup alone it sometimes "syncs" to the server process right away and the red x's go away, but the other half of the time the red x's never go away and require 2 or 3 restarts of the client. Rather annoying when checking an alarm state.