Adding GPIB-ENET/1000 to Windows 10 PC

[sullivnc]

I am trying to add a GPIB-ENET/1000 to my Windows 10 PC, running LabVIEW 2018.  I have updated the firmware, and all my IP settings are correct.  The computer recognizes it nice and quickly, but when I get to the end, I keep getting the same error: "The selected interface could not be added to the system." (see attached picture).  No error message or explanation why it couldn't be added.  Has anyone experienced this before?  I've tried disabling my firewall, and I can't think of what to do from here.  Thanks in advance for any help.

Computer IP Settings

IP Address: 192.168.15.100

Subnet Mark: 255.255.0.0

Gateway: 192.168.168.1

Primary DNS Server: 192.168.168.52

GPIB-ENET/1000 Settings

IP Address: 192.168.15.101

Subnet Mark: 255.255.0.0

Gateway: 192.168.168.1

Primary DNS Server: 192.168.168.52

Hostname: System15

Comment: System 15

Firmware Version: 1.2.1f0

[nyc_(is_out_of_here)]

If you are assembling your own small Ethernet network, you can choose your own IP addresses.
The format of the IP addresses is determined by the subnet mask. You should use the same
subnet mask as the computer you are using with your GPIB-ENET/1000. If your subnet mask is
255.255.255.0, the first three numbers in every IP address on the network must be the same.
If your subnet mask is 255.255.0.0, only the first two numbers in the IP addresses on the
network must match.

For either subnet mask, numbers between 1 and 254 are valid choices for the last number of
the IP address. Numbers between 0 and 255 are valid for the third number of the IP address,
but this number must be the same as other devices on your network if your subnet mask is
255.255.255.0.
If you are setting up your own network, you probably do not have a gateway or DNS server.
If this is the case, you should set the default gateway to 0.0.0.0 and leave the two DNS server
parameters blank.

[PahlM]

Another thing to try is to ensure that you have the latest version of NI-488.2. 

[sullivnc · Accepted solution]

I figured it out.  Rather than letting NI-488.2 discover it on its own, I provided it with the IP address and it worked immediately.  Thanks for the suggestions.

[Sparks!]

Must be a Windows security thing; the device has to be "invited by IP" rather than just showing up. Nice!