Quantcast
Channel: Spiceworks Community - Latest topics
Viewing all articles
Browse latest Browse all 184239

Spiceworks sees IP Camera but says that there are no open ports responding

$
0
0

I have just setup Spiceworks 6.2 on my network. Everything seems to be working fine. So far all computers being scanned with no problems.

The only problem that I have run into is that I have an IP Camera. The IP Camera is a Wireless Camera with WPA2 security. To access this IP Camera (while on the network) you have to enter the camera's IP address and port (i.e.: 192.168.1.196:1028) into the URL address bar and then enter the username and password.

Now, I do have "port forwarding" setup in the router and it is working. I can access the camera from my cell phone (across Verizon's network) and I can access it from another/a 2nd external network with no problems. I just enter my public IP address and the port number and then log in.

On the Spiceworks Server, I can access and view the camera directly by going to the camera's IP address and port...I can also log into it with no problem.

Spiceworks runs and sees the IP address and reports:
No open ports for this device were found to be responding.
This typically means that there is a firewall or permission issue preventing remote access.

Which is weird because the only firewall is the Windows Firewall. I have opened ports in the Windows Firewall. There is no other Firewall in place.

One might say that it has something to do with an Anti-Virus Security Center, but the only Anti-Virus program on this machine is the:
Microsoft Security Essentials

And like I said, I can access and view the camera, on the Spiceworks Server directly, by going to the camera's IP address and port.

I am not sure what else to try. Could someone please tell me how Spiceworks scans devices and logs in using predefined credentials when there is a "port number" involved?

Thank you

Bobby


Viewing all articles
Browse latest Browse all 184239

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>