setup ip camera foscam knock off Cant get past cox they block port 80. Wits end

Question

Hello,

I can see my camera on lan, but cannot setup for wan.

I have cox cable, motorolla surfboard modem, linksys router wrt54g.

I have dyndns enabled works great at home.

I have read about 100 hours of setup and cannot do this I am familliar with just about all setting now phew.

I have assigned port forwarding for the ip camera in the router. address of the camera and changed the ports for the camera and assigned ip its 192.168.1.100:8080

I can type http://mihali.homeip.net (dyndns assignment) works locally perfect.

my ip adress is from cox 72.207.78.91 when chck it on (whats my ip)

I have tested port ip and i can get in to my router locally but not from wan. 72.207.78.91:8080 and get to my router only locally. I checked it with (can you see me) and its open.

What would you suggest.

I dont know how to get into the ip camera from wan. How can I get past cox? Totally Frustrated Mitch

Answer 1

0

HI,

I am using another free dnns provider for ip cam in China but the speed of film movement is not smooth , about 4 second for refresh watching from Hong Kong. I wonder if i pay for the service of provider like dyndns, would it enhance the speed for viewer.

thanks

Patrick

answered Aug 08 at 06:19 AM

$littlepat2165\'s gravatar image$

littlepat2165
1

Please, rather than asking your question as an "answer" to somebody else's question ask your own. If you do so I'll happily explain why it won't, and what you can do to improve it.

Aug 08 at 07:02 AM Cry Havok ♦

Answer 2

Doesn't look like Cox block port 80. When I connect to your hostname (currently resolving to 204.13.248.125) I see an Apache server:

HTTP/1.1 302 Found
Date: Fri, 09 Jul 2010 19:36:57 GMT
Server: Apache
Location: http://flora92105.homeip.net/
Content-Type: text/html; charset=iso-8859-1
Connection: close

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>302 Found</TITLE>
</HEAD><BODY>
<H1>Found</H1>
The document has moved <A HREF="http://flora92105.homeip.net/">here</A>.<P>
</BODY></HTML>

This does tell me you're already running a web server, which is issuing a redirect to flora92105.homeip.net (also 204.13.248.125). That host is also running a web server:

HTTP/1.1 302 Found
Date: Fri, 09 Jul 2010 19:38:18 GMT
Server: Apache
Location: http://192.168.1.100:8080/
Content-Type: text/html; charset=iso-8859-1
Connection: close

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>302 Found</TITLE>
</HEAD><BODY>
<H1>Found</H1>
The document has moved <A HREF="http://192.168.1.100:8080/">here</A>.<P>
</BODY></HTML>

Which will never work from outside your network since it's redirecting to a LAN IP (192.168.1.100). Instead try redirecting to the DynDNS hostname and then the LAN IP, configure Apache to respond to connections to mihali.homeip.net with a redirect to http://mihali.homeip.net:8080.

Answer 3

Be aware that comments are just that, comments. Don't use them to add to your question since we may never see them.

Ah, right. You forgot to mention that you were using WebHop. That would have been useful to know.

I'll say it again though, you cannot use a WebHop to a LAN IP address. I'd also suggest you read the documentation for WebHop since mihali.homeip.net should be a webhop to http://flora92105.homeip.net:8080/ and flora92105.homeip.net must be the host updated by your update client.

setup ip camera foscam knock off Cant get past cox they block port 80. Wits end

Dyn Community Support

Get Involved

Related Questions

Follow this question