I have a new Vivotek IP security camera installed on my network. There are several ways to access the camera's video streams including an Activex plugin for IE, Quicktime with Chrome, and rstp with VLC. I am able to connect with IE and Chrome. In trying to connect with VLC, I obtain an error message saying that:
Connection failed:
VLC could not connect to "192.168.1.105:554".
Your input can't be opened:
VLC is unable to open the MRL 'rtsp://192.168.1.105:554/live.sdp'. Check the log for details.
However, it I turn off Smart Firewall and then reissue the connection, it completes successfully, and then I can reenable the firewall and it continues to feed the video stream.
I've looked through virtually every setup item to try to find the appropriate exception to be made without success. The IP address of the camera is in the network map.
But that didn't help, even after a reboot. The camera now shows as "Full Trust" (see attachment).
What is being blocked is "creating" the connection. Once created, then the VLC stream is allowed through. To create the connection, I either have to disable Smart Firewall temporarily, or reboot and create the connection before the NIS icon shows in the System Tray.
Nikhil - Thanks. That seems to have worked, although I found the process not too intuitive and I'm not sure what I did.
What I think I did is added a Traffic Rule that I named Vivotek which allows any traffic in or out with 192.168.1.5 on any port and ALL protocols. I then moved this to the top of the Rule list.
I tried Googling this issue and really didn't come up with much that helped because apparently the hits that I received applied to previous versions of the Firewall and the specific prompts were different and leading me to a dead end. I'm using Version 21 of NIS.
With my network cameras I only need to give them full trust in the network security map.
Giving a device full trust is the same as the rule you made, allowing all communication on all ports and protocols.
It's also odd that your rule works when it is not even the correct IP address.
Your first post states:
192.168.1.105:554
That means IP address 192.168.1.105 port 554
Making a rule for a different address should not help 192.168.1.5
If those addresses are correct you may find you don't need the rule, but if it works how it is you might as well leave it.
Dave
Agreed Dave - Something's not right...
Just a thought ...
Since the OP seems uncertain of their actions in crafting the rule (that made their camera operational) it may be appropriate for them to take a screen shot of the rule definition and the current rule list and post it in a response message. This is because crafting a bad rule or crafting a good rule but positioning it wrongly in the rules hierarchy (or the combination of the two) can end up allowing some unwanted or even worse, all traffic through. In other words done improperly such incorrect actions will effectively disable the firewall.