Linksys Compact Wireless G Internet Video Camera can't access it over the net - need help from someone who does

I am trying to install a four camera system using a linksys compact
wireles g internet video camera connected to my Compact PC 1000, using
Windows XP, linksys wrt 54g version 5, over Wild Blue Satelitte isp.
Firmware updated May 26th.

I signed up with linksys and got the IP link that I am to use to access
the remote viewing server.

Everytime I try to access the link site provided by linksys with IE or
Netscape I receive the
message "the page cannot be found".

I have redone the install several times, called linksys tech support,
replaced the camera, and still can't get passed STEP 1.

Linksys Tech support said the camera must be defective. This was their
only solution as to why I could not see the site over the internet even
though the message I received was "page not found". This type of
message to me would indicate the link was bad, or the portal number
associated with the link, wasn't correct.

Today I installed the replacement camera. I can see the camera image
just fine locally as before, but once I try to see it over the net I
still get the message "page cannot be displayed".

I have disabled my firewall on my PC, lowered the browser settings to
zero security and accept all cookies.

I agree I must be stupid. What in the world am I doing wrong?

If there are any Saturday surfers who would like to take pitty, I would
gladly
and grately accept a walk through.

Is there anyone out there who has this net service viewing up and
working?

It can't be this difficult. Anyone with nothing else better to do
today, I would love to hear from you.

dummy newbie

For those who might be interested in doing this type of application, I
resolved the problem of not being able to remote view with these
cameras by enabling NAT.

In doing my setup procedure with the the linksys router software 54g, I
had turned off Network Address Translation. When I turned this option
on, I am up and running ok.

dufus dummy newbie!

(E-Mail Removed) wrote:
> For those who might be interested in doing this type of application, I
> resolved the problem of not being able to remote view with these
> cameras by enabling NAT.
>
> In doing my setup procedure with the the linksys router software 54g, I
> had turned off Network Address Translation. When I turned this option
> on, I am up and running ok.
>
> dufus dummy newbie!


Yes, this solved the problem on the local side of the router to remote
view from another PC, however, it did not solve accessing the camera
from outside of WildBlue Satellite Internet router, such as testing it
with my old dial-up line.

I contacted WildBlue tech support to see is they were blocking the port
Linksys had assigned to this camera to remote view. They said, no, we
do not block any ports.

I used Port Dectective to see what it found. It found the port blocked.

A fair warning to those who might want to try to use Linksys cameras
over WildBlue High-Speed Satellite Internet. It isn't going to work.

still dufus dummy newbie

(E-Mail Removed) hath wroth:

>A fair warning to those who might want to try to use Linksys cameras
>over WildBlue High-Speed Satellite Internet. It isn't going to work.

The WRT54G v5 router has been a constant "challenge" for me. What
version firmware are you using? (Don't say the latest).

What port number do you think is blocked? 1024?
| http://www.linksysdata.com/ui/WVC54G...lolinkDDNS.htm

For some odd reason, the camera uses port 1024 for both DDNS and web
service. I don't think that will work. Try picking another port
number for the camera (not for DDNS) such as 2222. See:
| http://www.linksysdata.com/ui/WVC54G...up-Options.htm

Then, turn OFF UPnP in both the router and the camera.
http://www.linksysdata.com/ui/WRT54G...0.6/Manage.htm
http://www.linksysdata.com/ui/WVC54G...up-Options.htm
Setup port forwarding for whatever port you select such as 2222 and
set it to port forward to your camera IP of 192.168.1.115.

Any reason you didn't bother supplying the Linksys model number?
I'm curious because it seems to be a constant oversight. My guess
would be WVC54GC. Is this the correct model?
| http://www.linksys.com/servlet/Satel...VisitorWrapper

The default IP is 192.168.1.115. Is this what you're using? Do NOT
use DHCP to assign the IP address of the camera as it may change and
screw up port forwarding. Use a fixed IP address.

--
Jeff Liebermann (E-Mail Removed)
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558

Jeff Liebermann wrote:
> (E-Mail Removed) hath wroth:
>
> >A fair warning to those who might want to try to use Linksys cameras
> >over WildBlue High-Speed Satellite Internet. It isn't going to work.
>
> The WRT54G v5 router has been a constant "challenge" for me. What
> version firmware are you using? (Don't say the latest).
>
> What port number do you think is blocked? 1024?
> | http://www.linksysdata.com/ui/WVC54G...lolinkDDNS.htm

1024 but also tried 2222
>
WRT54G V5 firmware 1.00.6

used 1024 but also tried 2222 same results

> For some odd reason, the camera uses port 1024 for both DDNS and web
> service. I don't think that will work. Try picking another port
> number for the camera (not for DDNS) such as 2222. See:
> | http://www.linksysdata.com/ui/WVC54G...up-Options.htm
>
> Then, turn OFF UPnP in both the router and the camera.

done

> http://www.linksysdata.com/ui/WRT54G...0.6/Manage.htm
> http://www.linksysdata.com/ui/WVC54G...up-Options.htm
> Setup port forwarding for whatever port you select such as 2222 and
> set it to port forward to your camera IP of 192.168.1.115.

yes

>
> Any reason you didn't bother supplying the Linksys model number?
> I'm curious because it seems to be a constant oversight. My guess
> would be WVC54GC. Is this the correct model?

yes

> | http://www.linksys.com/servlet/Satel...VisitorWrapper
>
> The default IP is 192.168.1.115. Is this what you're using? Do NOT
> use DHCP to assign the IP address of the camera as it may change and
> screw up port forwarding. Use a fixed IP address.

yes fixed IP 192.168.1.115 port 2222
>
> --
> Jeff Liebermann (E-Mail Removed)
> 150 Felker St #D http://www.LearnByDestroying.com
> Santa Cruz CA 95060 http://802.11junk.com
> Skype: JeffLiebermann AE6KS 831-336-2558

(E-Mail Removed) hath wroth:

>1024 but also tried 2222

There's nothing magic about 2222. I just picked it randomly. It
should work if nothing else is on 1024. I don't like using such a low
numbered port as 1024 as it's highly likely that some other incoming
network process would also use it.

I would stay with 2222 for now. Change it later after it's working.

>WRT54G V5 firmware 1.00.6

Current firmware version is 1.00.9. Upgrade:
| http://www.linksys.com/servlet/Satel...VisitorWrapper
The fix list is fairly extensive, but there's nothing mentioned about
fixing port forwarding problems. It's still worth doing the firmware
update.

>yes fixed IP 192.168.1.115 port 2222

I just tried to connect on 2222. Nothing.

It looks like you still have the DMZ turned on. Checking with
telnet.... yep. Turn the misnamed DMZ feature *OFF*.

Incidentally, the fact that I can distinguish between the results from
ports 2999 and 3000 from the internet indicates that WildBlue is NOT
blocking ports.

Hmmm... Ping returns 600-800msec latency. Not too horrible for
satellite.

Running a port scan, it shows you have ports 1025 thru 1034 open.
Nothing open on 2222. Why these particular ports are open is somewhat
mysterious. Check your port forwarding configuration. It's probably
wrong.


--
Jeff Liebermann (E-Mail Removed)
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558

Jeff Liebermann wrote:
> (E-Mail Removed) hath wroth:
>
> >1024 but also tried 2222
>
> There's nothing magic about 2222. I just picked it randomly. It
> should work if nothing else is on 1024. I don't like using such a low
> numbered port as 1024 as it's highly likely that some other incoming
> network process would also use it.
>
> I would stay with 2222 for now. Change it later after it's working.
>
> >WRT54G V5 firmware 1.00.6
>
> Current firmware version is 1.00.9. Upgrade:
> | http://www.linksys.com/servlet/Satel...VisitorWrapper
> The fix list is fairly extensive, but there's nothing mentioned about
> fixing port forwarding problems. It's still worth doing the firmware
> update.
>
> >yes fixed IP 192.168.1.115 port 2222
>
> I just tried to connect on 2222. Nothing.
>
> It looks like you still have the DMZ turned on. Checking with
> telnet.... yep. Turn the misnamed DMZ feature *OFF*.
>
> Incidentally, the fact that I can distinguish between the results from
> ports 2999 and 3000 from the internet indicates that WildBlue is NOT
> blocking ports.
>
> Hmmm... Ping returns 600-800msec latency. Not too horrible for
> satellite.
>
> Running a port scan, it shows you have ports 1025 thru 1034 open.
> Nothing open on 2222. Why these particular ports are open is somewhat
> mysterious. Check your port forwarding configuration. It's probably
> wrong.
>
>
> --
> Jeff Liebermann (E-Mail Removed)
> 150 Felker St #D http://www.LearnByDestroying.com
> Santa Cruz CA 95060 http://802.11junk.com
> Skype: JeffLiebermann AE6KS 831-336-2558


I tried a new port number 2699. I still was not able to remote view.

When viewing the router settings with a web browser locally, this is
how they are set:

Under Tab, Applications and Gaming:

Sub Tab: Port Range Forward

Port Range
Application Start End Protocol IP Address Enable

camera1 2699 2699 Both 192.168.1.115 Enabled

This is all this is listed on this tab

-----------------------------------------------------------

Under Sub Tab: Port Triggering

Nothing is listed

---------------------------------------------------------

Under Sub Tab: DMZ

Disable (checked)
DMZ Host IP Addres 192.168.1.

-------------------------------------------------------
Under Set up

Router name: WRT54G
MTU Auto
Local IP Address: 192.168.1.1
Sub Net 255.255.255.0

DHCHP Server Enabled
Starting IP Address: 192.168.1.
Maximum Number of DHCP Users: 50

Client Lease Time: minutes (0 means one day) 0
Static DNS 1: . . . 0
Static DNS 2: . . . 0
Static DNS 3: . . . 0
WINS: . . . 0
--------------------------------------------------------------
Under Sub Tab DDNS

DDNS Service: Disabled

---------------------------------------------------------------

Under Sub Tab Mac Address Cloning
Disabled
---------------------------------------------------------------
Under Sub Tab Advanced Routing
Nothing set
---------------------------------------------------------------

Under security, nothing is checked
Block Anonymous Internet Requests
Filter Multicast
Filter Internet NAT Redirection
Filter IDENT(Port 113)
---------------------------------------------------------------
Acess Restrictions
is disabled
-------------------------------------------------------------

Access Server: HTTP checked HTTPS
Wireless Access Web: Enable (checked) Disable

Remonte management disabled

----------------------------------------------------------
Status
Firmware Version: v1.00.6, Jan. 10, 2006
----------------------------------------------------------------

Just noticed on the camera status log is show it at end address 105
even though we have it set for static ip 115. the video is coming thru
to my local pc when logged into IP 115 but the log show video failed
after 30 seconds on 105.
-------------------------------------------------------------

I do not have any port scanning software other than a feebie Port
Dectective, which when I run, show all the ports you mentioned as being
closed.

What software are you using that allows you to see that they are open?
---------------------------------------------------------------

I am downloading the new firmware update after this post.

-----------------------------------------------------------------

Thanks for the help

dufus dummie

The new firmware update didn't seem to help either.

I am going to ditch the Linksys WRT54G v5 router and try Hawkins
Technologies.

dufus dummie

(E-Mail Removed) wrote:
> I am trying to install a four camera system using a linksys compact
> wireles g internet video camera connected to my Compact PC 1000, using
> Windows XP, linksys wrt 54g version 5, over Wild Blue Satelitte isp.
> Firmware updated May 26th.
>
> I signed up with linksys and got the IP link that I am to use to
> access the remote viewing server.
>
> Everytime I try to access the link site provided by linksys with IE or
> Netscape I receive the
> message "the page cannot be found".
>
> I have redone the install several times, called linksys tech support,
> replaced the camera, and still can't get passed STEP 1.
>
> Linksys Tech support said the camera must be defective. This was their
> only solution as to why I could not see the site over the internet
> even though the message I received was "page not found". This type of
> message to me would indicate the link was bad, or the portal number
> associated with the link, wasn't correct.
>
> Today I installed the replacement camera. I can see the camera image
> just fine locally as before, but once I try to see it over the net I
> still get the message "page cannot be displayed".
>
> I have disabled my firewall on my PC, lowered the browser settings to
> zero security and accept all cookies.
>
> I agree I must be stupid. What in the world am I doing wrong?
>
> If there are any Saturday surfers who would like to take pitty, I
> would gladly
> and grately accept a walk through.
>
> Is there anyone out there who has this net service viewing up and
> working?
>
> It can't be this difficult. Anyone with nothing else better to do
> today, I would love to hear from you.
>
> dummy newbie

I have the WVC54G camera and a Linksys WRT54GS and it works fine with my SBC
DSL.
The settings in my WRT54GS are:
From "Applications & Gaming" / "Port Range Forward"
I have set for "Application" name = Camera
Start 10** End 10** (** = your port number)
Protocol = TCP
IP Address 192.168.1.* (* = your number)
Check box "Enable" yes... check that box.

Remember that the camera requires an Active X control to view over the
Internet. So you must be using Internet Explorer. And if your using WinXP
you must recognize when the Active X control is trying to load to your
computer and allow it. You do this only once.

And like Jeff said you must include the port number in the URL preceded by a
colon.

(E-Mail Removed) hath wroth:

>I tried a new port number 2699. I still was not able to remote view.

Same here. Nothing visible from the internet on 2699.
It's kinda hard to test from here with a moving target port.

>Port Range
>Application Start End Protocol IP Address Enable
>camera1 2699 2699 Both 192.168.1.115 Enabled

That's correct.
I trimmed all the setting you mentioned that I think are correct.

>DHCP Server Enabled
>Starting IP Address: 192.168.1.
>Maximum Number of DHCP Users: 50

The starting address got truncated. I think it's suppose to be
192.168.1.100. If so, you have the camera in the middle of the DHCP
assigned range. This is generally not a great idea but will not cause
a problem until you have 15 clients attached. If you get it working,
reassign the IP address of the camera to something OUTSIDE the DHCP
address pool.

>Access Server: HTTP checked HTTPS
>Wireless Access Web: Enable (checked) Disable
>Remonte management disabled

Enable remote management for a while on port 8080. Be sure to assign
a proper password for the router. I don't need to get in. I just
need to see if the router is accessible from the internet to be sure
that WildBlue isn't blocking ports. HTTP checked is fine. No need
for HTTPS if I'm not going to play with the setup.

>Just noticed on the camera status log is show it at end address 105
>even though we have it set for static ip 115. the video is coming thru
>to my local pc when logged into IP 115 but the log show video failed
>after 30 seconds on 105.

Huh? Are you *SURE* the camera is at 192.168.1.115 ???
At what IP address do you access the camera on your LAN? 105 or 115?

>I do not have any port scanning software other than a feebie Port
>Dectective, which when I run, show all the ports you mentioned as being
>closed. What software are you using that allows you to see that they are open?

It won't do much good to scan your router from inside the your LAN. It
has to be done from the internet. I'm using Net Tools 4:
http://users.pandora.be/ahmadi/nettools.htm
I also use nMap:
http://en.wikipedia.org/wiki/Nmap
http://www.insecure.org/nmap/
I can put together a list of others if you want them.
http://en.wikipedia.org/wiki/Port_scanner
However, for this exercise, I suggest you use an online port scanner.
See:
http://en.wikipedia.org/wiki/Port_sc...ne_Portscanner

--
Jeff Liebermann (E-Mail Removed)
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558