Appendix B
Troubleshooting and Common Questions
GPIB-ENET/100 for Windows Me/98/95
B-6
ni.com
How should I check for errors in my GPIB application?
Examine the value of
ibsta
after each NI-488 or NI-488.2 call. If a call
fails, the ERR bit of
ibsta
is set and an error code is stored in
iberr
.
For more information about global status variables, refer to Chapter 3,
Developing Your Application
, in the
NI-488.2 User Manual for Windows.
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
NI Ethernet Device Configuration 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. Please 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 clicking
Refresh
.
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. Click
Refresh
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 devices on another subnet.
I have GPIB-ENET interfaces as well as GPIB-ENET/100 interfaces.
Why can’t I see the GPIB-ENET interfaces in the NI Ethernet Device
Configuration utility?
The GPIB-ENET/100 uses a configuration protocol that can communicate
with the NI Ethernet Device Configuration utility. Because GPIB-ENET
interfaces are not compatible with this configuration protocol, the utility
does not recognize them on the network.