I am running a data acquisition system (DAQ) on a Windows Vista machine sitting on a private network behind a Linux gateway node. The gateway node, in addition to serving as a gateway, additionally runs some first order processes on our data - namely unpacking the raw data into an intermediate state where we can start to do some analysis. We don't do this on the DAQ PC itself to save processor cycles (our readout system is CPU constrained). The Windows DAQ and the Linux gateway "consult" on this process via TCP/IP commands. When we send a command from the Windows PC to the Linux box (for example, telling the data unpacking programs to begin or stop), there is a very long wait while (I think) the Windows machine tries to look up the name of the Linux box on the public internet before giving up (because we are not connected to the public internet at all right now) and trying on the private network, where it succeeds. I believe we have the Linux box configured correctly (and am not expecting comments on it here, ha!), but cannot figure out how to tell the Windows machine to *not* do a DNS lookup, but instead to just trust the private network. I think I know the cause of these long waits because at one point we ran the system with access to the public internet where the Windows PC could quickly perform a DNS lookup using the real internet.I've tried all the "obvious" options available in the GUI menus - fiddled with the DNS addresses, gateway IP's, etc., all to no avail. Does anybody have any ideas?

When you say you want it to trust the private network, is there a DNS service running on the private network? Did you check to see if the Linux box is registered in the local DNS server? CCNA, A+, N+

Thanks for your response!We have tried both no local DNS server and having the Linux box act as a DNS server and get the same result. There is always some very long wait before we can send a TCP/IP command. I'm not sure why it is even trying to do a host name resolution since we are explicitly using IP addresses.We commissioned the system with public internet access and known DNS servers and did not see this problem. It only surfaced when we took it off the public internet.Thanks again for your time.