LabVIEW Web Server and GPIB-ENET/100

[RLD]

I'm having difficulty with the LabVIEW Web Server handling VI F/P snapshots when operating with the GPIB-ENET/100. Browser "pings" from a remote computer when both computers are on the same network switch work just fine. When the remote computer is "further out" on the network, but still inside the company firewall, the LabVIEW application locks for 5 seconds when a browser qery comes in. After the lock period the LabVIEW app resumes normal operation. If I replace all GPIB related VI's with dummy VI's to separate the app from the ENET box, the app runs with negliglible interference from remote browser queries.

Is there anything I can tell the company IT guy to do for us?

Rich

[JoshuaP]

One thing that you didn't mention was whether or not you were using one NIC or two. If you are using two NIC devices, I would suggest connecting both to the default NIC. Do you have a separate IP for each NIC? If so are you pinging the one connected to the external network or the one connected to the ENET. Try reducing your system to one NIC and see how this affects everything. It�s possible that you are pinging the NIC that is connected to the ENET device. In this case the ENET will be busy sending data while in operation and it will take time for the ping to come in one NIC to the other for a response and then back.

I hope this helps,
-Josh

[RLD]

The problem seems to be associated with UI thread operations in my application. I can eliminate the acquisition loop lockup by removing a sub VI which has a property node reading the strings of a enum control.

This system is using two NIC's, one dedicated exclusively to the ENET-GPIB. Each NIC has it's own IP. We resently have learned from IT that the "remote" computers (in the offices) are isolated from the lab with an internal firewall. The servers are NT.