Appendix B
Troubleshooting and Common Questions
©
National Instruments Corporation
B-3
I have an application using the GPIB-ENET. Can I replace the
GPIB-ENET with a GPIB-ENET/100?
Yes. You do not need to rewrite your application code to replace
a GPIB-ENET with a GPIB-ENET/100. However, you do need to
configure the GPIB-ENET/100 to have the same network identity as the
GPIB-ENET you are replacing. First, acquire network parameters for the
GPIB-ENET/100 using DHCP or the NI Ethernet Device Configuration
utility. Then use
ibconf
to remove the GPIB-ENET information and
reassociate the same entry with the numerical IP address, hostname, or
hostname alias for the GPIB-ENET/100. For example, if your application
code refers to the GPIB-ENET as
gpib1
, reconfigure
gpib1
to refer to the
GPIB-ENET/100.
Why does the NI Ethernet Device Configuration utility list my box as
*BUSY*
when I know my network uses DHCP?
For up to one minute, the GPIB-ENET/100 attempts to retrieve network
parameters from a DHCP server. During this time,
*BUSY*
appears in the
utility display. If this status does not change, there are several reasons why
DHCP may fail to respond. One of the most likely reasons is that your
subnet has no more available addresses to assign using DHCP. Consult
your network administrator to determine the specific reason for the
problem.
I just added a GPIB-ENET/100 to the network, but it does not show up
in the NI Ethernet Device Configuration utility. What is the problem?
Allow at least 15 seconds for the GPIB-ENET/100 to complete its
power-on self tests before launching the utility or refreshing the display.
Communication between the NI Ethernet Device Configuration utility and
the GPIB-ENET/100 is not guaranteed. Though unlikely, it is possible that
the communication gets lost in the network. Refresh the display more than
once before concluding the device is not discovered.
Verify that the GPIB-ENET/100 shares the same subnet as the computer
running the NI Ethernet Device Configuration utility. The utility cannot
communicate with devices through gateways on the network and will not
discover Ethernet devices on another subnet.
