An Alternative to Sololink

[carlbeck]

tpearson:

    YOU STATE:{On Router. Check that you have setup Port Forwarding to 1024.}

    On my Router WRT54GS, Under the Administartion tab, I see "Remote Router Access -- Management Port: (I typed 1024) 

    YOU STATE {and have the correct IP address specified i.e. 192.168.x where x is that assigned by your router to the camera.}

   Where do I find this???????

    When I use my Browser and type in: http://cbcam.dyndns.org:1024 --- I get a popup for an ID and password BUT the only ID and Password is the one for my Router and I sure don't want that!

[Quickly]

Thanks again T.

I've emailed DynDNS.

Still attached via ehternet at the mo. Don't want to start messing about with wifi until I can get the basics sorted...
Q

Message Edited by Quickly on 06-02-200711:36 AM

[tpearson]

Carl ... let's take your points in turn ...

 On my Router WRT54GS, Under the Administartion tab, I see "Remote Router Access -- Management Port: (I typed 1024)     I don't have this router myself but this sounds like the wrong screen to type 1024 in. On my Netgear router there is a command which shows devices connected to the router so look on your router for something similar. Your camera should appear in the list of devices with the IP address the router has allocated it. Normally 192.168.1. x  where x is a low number 2-9.  You should allocate Port 1024 for port forward to the camera using IP found above

    YOU STATE {and have the correct IP address specified i.e. 192.168.1.x where x is that assigned by your router to the camera.}

   Where do I find this???????    (see above)

    When I use my Browser and type in: http://cbcam.dyndns.org:1024 --- I get a popup for an ID and password BUT the only ID and Password is the one for my Router and I sure don't want that!  as part of the camera setup you should have set a password for the camera's own admin user if you have not done that the password default is also 'admin' but if in doubt go back and repeat the setup as per the manual

[tpearson]

Quick ... there lies your problem.  Until you disconnect your camera and have it standalone none of the instructions I've given before will work!  See my message to Carl (for info) disconnect the network cable to your camera and try again

[Quickly]

Thanks again T.
After a little fiddling I've got the wifi working. Or so I thought... The light's on but no one's home!
And now after rebooting the camera the wireless light's off.

Talk about frustrating!

Message Edited by Quickly on 06-02-200711:36 AM

[tpearson]

Q ... there is a setting for the camera to have LED light switched off once booted so maybe that is why it's not on?  Check your router to see whether camera is on the attached devices list when you have turned it on. If not then I think you need to check camera setup again and SID used etc etc.

[Quickly]

T,

It's being rather temperemental!

Seems ok at present but have to keep rebooting the camera. Unable to acces the setup page wirelessly though.

On the brightside, the tech support chaps at DYNetc are incredibly helpful and are trying their best to help me out.

Hats off considering I'm using the free service at present. May well fork out some cash for a proper service if I can get this working!

[Quickly]

I'm getting nowhere fast here and losing the will...

DynDNS are saying port 1024 is being blocked. I've opened up every option I can think of but when I use this site: http://www.canyouseeme.org./ it still times out or states it's blocked.

Also, I'm unable to access the cameras set up page wirelessly. It's set to a static address of .115 and typing that into the browser gets nowhere.

This'll be the third day I've wasted trying to resolve this!

Any ideas? Please!

Message Edited by Quickly on 06-02-200707:36 AM

[Quickly]

"Can't say I've seen this error message myself but it does imply your Dyndns username/password is not being recognised or it is trying to get through to Sololink instead."

T, this seems to be the problem. Whilst sending my details the webpage states looking up/connecting to ddns.ourlinksys.com.

I think you've discovered the problem. Now the million dollar question is how can this be resolved?

Incidentally I successfully(surprisingly) updated the cameras firmware but obviously that didn't help!

[Quickly]

Update...

Sorted now and all is good!

A great big thank you to the staff at DynDNS particularly Jason(top bloke) and John.

Also thanks to T(pearson),Phil, embguru, ajdornier, for the original info and help.

For the record, if you're having issues with port forwarding forget 1024 and use something over 8000.

If I can help I will however don't ask about wifi. That's my next challenge!
Q