12-08-2008 09:15 PM
I have 2x WVC54GCA
Static assigned as 192.168.0.240 and .241
Using Alternate Web Port of 6000 and 6001.
Redirecting ports 6000 and 6001 on the firewall to the correct LAN IP.
I cannot access either camera via http://184.108.40.206:6000 nor http://220.127.116.11:6001. The error message I get is:
"The error was: “unknown error” (WebKitErrorDomain:103) ".
I must be missing something in the camera config. I'm running a Cisco ASA Firewall and have many other services running on quite a few other LAN machines, so I know how to redirect ports.
My concern is that even with the Alternate Web Port config option set to 6000, I can only get to the camera via http://192.168.0.240 (*not* http://192.168.0.240:6000 )
Which tells me that even though I have the port option set, the device is still listening on port 80 (http). This should be incorrect, right?
12-09-2008 06:50 AM
Do the cams respond internally using those URL's? You also say "outside access" - those are INTERNAL IP's and will never work outside
First off, you can get to the cam using just the IP, which means port 80 is working. Try 1024 instead of 6000, can you get to the IP now on port 80 AND 1024? On the WVC54GCA, both ports are open at the same time, this is OK
If that works, then try changing the 1024 to 6000 and try again....If that works,then use the domain name or WAN IP and try remotely, using these steps you'll figure it out.
TZO also has a nice tutorial on the WVC54GCA cams and doing port forwarding, see the Support/Tutorials section under Linksys, and be sure to check out the MyHomeServer.com review on the WVC54GCA and WVC210 cams from Linksys
12-09-2008 09:31 AM
Yes, the camera's work fine via just the LAN IP address (or http://192.168.0.240 ). When I was talking about the "outside access", I was referring to being outside the location and trying to view the cams by going to http://18.104.22.168:6000 (where 22.214.171.124 is my WAN address).
I haven't tried 1024. I was not aware that 1024 was open by default. Are any other services run on 1024 by default? If not, then I can easily change the Firewall's config to redirect to that port instead of 6000.
I'll try it out today and respond back.
12-14-2008 04:02 PM
12-15-2008 10:22 PM
12-15-2008 10:40 PM
Sorry, I haven't been back to the client site to test things out again, but:
Remoting in I am still *able* to connect to http://192.168.0.240 and view the camera. And I am still *unable* to connect to http://192.168.0.240:6000 even though I have the alternate port set to 6000 in the config.
This must be the source of my problem, but the setting is there, and I'm still unable to do anything with it.
Something I'm missing?
12-16-2008 12:27 AM
Umm....I am a bit confused...you say 'remoting' in you can connect to 192.168.0.240....does that mean via a public IP and port forwarded at the Pix?
I assume you have checked the Pix logs to se if the traffic to port 600 is being allowed. If you can't connect to port 6000 from the local network, then it is probably something wrong wit the camera config....my best suggesttion would be to disable the alternate port option, save the config, then re-enable it and save again, then try to connect.
You can find out if the camera is listneing on port 6000 by telnetting to that port...it should at least connect....
12-16-2008 12:29 AM
Also, look here:
Looks like you are using Safari......have you tried a different browser?