Setting Up Ipcam Behind True Proxy

[mads]

I'm trying to setup an ipcam(foscam).

I have signed up for dyndns.org because of the dynamic ip.

I have no problem connecting to my camera on the network but as soon as i try to connect through dyndns server it won't work.

I set up port forwarding to 5656 in both the router and the ipcam, which again works flawlessly on the local network.

When I go to whatismyip.com I always get the following :

Your IP Address Is: xxx.xxx.xx.xxx (hidden for obvious reasons)

Possible Proxy Detected: HTTP/1.1 NetScaler

Can this True proxy interfere with my setup ?

[bino]

It sounds like DynDns doesn't know where to look. I'm not completely familiar with DynDns, but I've used no-ip with no problems. I had to install a "dynamic update client" provided by no-ip so that would update them regularly with my current IP address. Does DynDns have something like this / is it configured correctly ?

[thaimite]

As stated, you need to install the DynDNS client. DynDNS is almost identical to No-IP (I use both) and the client should ideally be in your router/modem.

If your camera is on a 3G or CAT CDMA network forget it. It will not work

[HardenedSoul]

This is spooky. First the same router now the Foscam. Never had a problem with the True proxy when I had ADSL.

I, too, connect to it via DynDNS but I just don't know enough to be able to advise you on setup beyond asking if you set up the software that came with the camera.

It's called IP Camera tool and you have to set it up with an ethernet cable first. Once that's sorted and you can connect wirelessly, it's just a matter of making sure all the fields are correctly completed in the administrator section of the GUI, ports are forwarded in your router or, if you prefer, that UPnP is ticked and away you go.

[Sayonarax]

Setup your dyndns settings in your router. I assume this is the step you've missed since you didn't say you had done it.

Check youtube for "setup ip camera thru dyndns"

[h90]

Make one test: Try to connect with your dyndns.org address from somewhere far away...

(Maybe over 3G??).

We fought 5 hours to get ours to run and no way.......Than that specialist got the idea, instead of trying to connect from his house via teamviewer, he let a friend from far away try it and it worked.

After many phone calls he found out that either on the phone lines or within true there are subnets, from inside that subnet it doesn't work. From outside that subnet we could connect.

Strange and no one really understood it but that is the case here.