NI VeriStand

Showing results for 
Search instead for 
Did you mean: 

Veristand 2010 deploy/connection error



We're wondering if it's possible the lack of a DNS server is causing the problem you see.  This pertains to a change made between NI VeriStand 2009 and 2010.


Are you using the name of the target or the IP address (


When you access the target through FTP, do you use its name or IP address?  Can you access with FTP using both name and IP?
Same question for ping.
0 Kudos
Message 11 of 13
I did the dns name test and by default I was not able to access the PXI using the name. I was able to fix this issue by manually editing the windows hosts file. After that I was able to access, ping and ftp the PXI both with the IP or the name. No change on the VS side of the problem, still no communication. As a note, I always use the ip address to identify the remote systems, never the name. Luca
0 Kudos
Message 12 of 13

I just ran into this and solved the problem. I don't know why, but if you run into this you can fix it by static'ing the target and setting the DNS and Gateway to

Stephen B
Message 13 of 13