Exe built on one machine won't work correctly on another.

Question

Hello list!
I have two identical PC's. Both run Windows 2000. Both have two NIC cards, one on the motherboard, the other in physical PCI slot 3. The 2nd NIC on both machines is the same make & model. The NIC on the motherboard on each is configured for DHCP to talk to the company network. The other has a fixed I.P. address to talk to my Fieldpoint and instrumentation. The Fixed I.P. NIC of each PC is connected to a FP2010, an Keithley 2701 and a Tektronix TDS-3012. Both FP controllers have the same address, both DMMs have the same address and both scopes have the same address. Each PC has Labview 7 installed.
In short, all of the hardware is identical between the two installs.
My source code for my application is on the company network. My IAK file for the Fieldpoint is on the network, and the source code points to it's location. Both machines log into the network, but with different login names. Both machines are local admins of their logins. Both machines map the same network drives to the same drive letters.
If I run the source code (from the network) in either machine, it works fine and talks to all of the ethernet I/O just fine.
If I build an EXE in machine A and try to run that EXE in machine A, it works fine and talks to the ethernet I/O, but if I try to run that EXE in machine B, it will run but won't talk to the ethernet I/O .
If I build an EXE in machine B and try to run that EXE in machine B, it works fine and talks to the ethernet, but if I try to run that EXE in machine B, it will run fine but won't talk to the ethernet I/O .
The only thing different between the two machines is this minor configuration difference...
If you do a START->Settings->Network and Dialup Connections->Select the 2nd NIC, then Properties->Configure. In the "General" tab is the name of the card (3Com....), the "Device type" (Network Adapters), "Manufacturer" (3Com), and "Location:"
On one machine the "Location:" is PCI Slot 4 (PCI bus 1, device 13, function 0).
On the other machine, the "Location" is PCI Slot 5 (PCI bus 2, device 13, function 0).
I'm pretty sure this is the issue, but how do I fix it?  Is there some way to get Labview to find the ethernet card no matter what PCI Slot or bus it's using? Is there something I should be including in the build that I'm missing?
Any suggestions would be appreciated.
Mike

Answer 1

hi there
hmm, ok, sounds like a similar problem i once had with more than one NICs in my system. In my case the app searched for a device with a given IP address, but it wasn't found because the device was connected to the second NIC in the systems list of NICs and the first NIC gave a timo error.
You could try to connect both networks with a single NIC. You can set the NIC to default DHCP (automatically retrieve IP address from your company network) and give it an "Alternative network settings" (sorry, i have german Win, so i don't know the english expression). By doing so ONE single NIC can connect to TWO IP addresses from different sub-Networks (i know that this works with XP, don't know about Win2000).
Then there'll be no conflicts in the search orders (but be aware that one NIC has to handle all the traffic).
Best regards
chris
CL(A)Dly bending G-Force with LabVIEW
famous last words: "oh my god, it is full of stars!"