Security
Search result
I connected a Basler IP camera to my PC and powered on the camera. But when I use the Basler BIP Finder software, the camera is not listed. What could be wrong?
There are several common reasons why IP camera discovery using Basler's BIP Finder software program might fail:
If your PC is using a firewall, turn it off.
Make sure that all of the NICs in your PC (even wireless NICs) are configured for different subnets. For example:
NIC 1: Automatic IP address
NIC 2: 192.168.0.110 / 255.255.255.0
NIC 3: 192.168.1.110 / 255.255.255.0
etc.
Please note that if you have set a NIC in your PC to use an auto IP address and there is no DHCP server on your network, the NIC will get an IP address in the 169.254.xxx.xxx range with a 255.255.0.0 subnet mask. Make sure that any other NICs in your computer are set so that they do not have a configuration in the same subnet.
On your PC, disable all of the NICs that the camera is NOT connected to (even wireless NICs). Now try to find the camera again with the BIP Finder software. Once the BIP Finder finds your camera, the operating system will automatically correct the route. You can now enable the other NICs again.
Disable all filter drivers that may interfere with an IP camera's communication. In fact, the only thing that a camera needs to communicate successfully is "internet protocol (TCP/IP)" as shown below.
 | A Firewall is active. |
If your PC is using a firewall, turn it off.
| You have multiple network interface cards (NICs) in your PC and they are in the same subnet. |
Make sure that all of the NICs in your PC (even wireless NICs) are configured for different subnets. For example:
NIC 1: Automatic IP address
NIC 2: 192.168.0.110 / 255.255.255.0
NIC 3: 192.168.1.110 / 255.255.255.0
etc.
Please note that if you have set a NIC in your PC to use an auto IP address and there is no DHCP server on your network, the NIC will get an IP address in the 169.254.xxx.xxx range with a 255.255.0.0 subnet mask. Make sure that any other NICs in your computer are set so that they do not have a configuration in the same subnet.
| The Windows® operating system added an incorrect route to your camera. |
On your PC, disable all of the NICs that the camera is NOT connected to (even wireless NICs). Now try to find the camera again with the BIP Finder software. Once the BIP Finder finds your camera, the operating system will automatically correct the route. You can now enable the other NICs again.
| Filter drivers (for example, VPN software) are installed on the NIC to which the camera is connected. |
Disable all filter drivers that may interfere with an IP camera's communication. In fact, the only thing that a camera needs to communicate successfully is "internet protocol (TCP/IP)" as shown below.
Was this answer helpful to you?
© 2010 Basler AG | Imprint | Legal Policy
