Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
IP Cam: Inaccessible Over WAN?
44 views
Skip to first unread message
(PeteCresswell)
Jun 19, 2012, 9:06:46 PM6/19/12
to
I moved a server that's managing two IP cams from a DSL-connected
site to a Comcast Cable-connected location.
The cam that is at that location, however cannot be connected to
over the WAN. Local addr works fine. But the likes of
http://Whatever.DynDNS.Org:1234 does not.
I'm pretty sure I have port forwarding set up correctly - mainly
because:
- Port forwarding is working for the server PC at that location
- There are so few things to specify (local IP addr, port range,
protocol type) that I don't think even I could have fouled
it up.
Only thing I can think of is that the server PC and the IP cam
might be different types of devices from the cable modem's
perspective.
The modem is definitely seeing the IP Cam bc it appears on it's
"Connected Devices" list with he expected local IP addr.
To that end, I tried turning the cable modem's firewall totally
off, but no joy.
I can't find anything about a make/model in the modem's web pages
except for:
eMTA & DOC SIS Software Version = 7.4.63a
Could there be some other setting in the modem/router that would
prevent port forwarding to the IP cam but not to the server PC?
--
Pete Cresswell
site to a Comcast Cable-connected location.
The cam that is at that location, however cannot be connected to
over the WAN. Local addr works fine. But the likes of
http://Whatever.DynDNS.Org:1234 does not.
I'm pretty sure I have port forwarding set up correctly - mainly
because:
- Port forwarding is working for the server PC at that location
- There are so few things to specify (local IP addr, port range,
protocol type) that I don't think even I could have fouled
it up.
Only thing I can think of is that the server PC and the IP cam
might be different types of devices from the cable modem's
perspective.
The modem is definitely seeing the IP Cam bc it appears on it's
"Connected Devices" list with he expected local IP addr.
To that end, I tried turning the cable modem's firewall totally
off, but no joy.
I can't find anything about a make/model in the modem's web pages
except for:
eMTA & DOC SIS Software Version = 7.4.63a
Could there be some other setting in the modem/router that would
prevent port forwarding to the IP cam but not to the server PC?
--
Pete Cresswell
Char Jackson
Jun 20, 2012, 12:31:55 AM6/20/12
to
On Tue, 19 Jun 2012 21:06:46 -0400, "(PeteCresswell)" <x...@y.Invalid>
wrote:
>I moved a server that's managing two IP cams from a DSL-connected
>site to a Comcast Cable-connected location.
>
>The cam that is at that location, however cannot be connected to
>over the WAN. Local addr works fine. But the likes of
>http://Whatever.DynDNS.Org:1234 does not.
Does it work if you use the WAN IP address rather than the DynDNS
translation? I assume your cam is on port 1234 and you're not also
using that port for anything else at the same time.
>I'm pretty sure I have port forwarding set up correctly - mainly
>because:
>
>- Port forwarding is working for the server PC at that location
>
>- There are so few things to specify (local IP addr, port range,
> protocol type) that I don't think even I could have fouled
> it up.
>
>Only thing I can think of is that the server PC and the IP cam
>might be different types of devices from the cable modem's
>perspective.
You're saying cable modem but obviously mean router, so does that mean
you're using a combo modem-router? What's its make and model? We may
want to access its manual. If it's a combo unit, do you have access to
its config section?
>The modem is definitely seeing the IP Cam bc it appears on it's
>"Connected Devices" list with he expected local IP addr.
>
>To that end, I tried turning the cable modem's firewall totally
>off, but no joy.
Cable modems don't have that kind of 'Connected Devices' list, nor do
they have a firewall. Further evidence that you might be saddled with
a dreaded combo unit. Yuck.
>I can't find anything about a make/model in the modem's web pages
>except for:
>
> eMTA & DOC SIS Software Version = 7.4.63a
>
>
>Could there be some other setting in the modem/router that would
>prevent port forwarding to the IP cam but not to the server PC?
Seems doubtful, but it's hard to say without knowing what you're
dealing with.
wrote:
>I moved a server that's managing two IP cams from a DSL-connected
>site to a Comcast Cable-connected location.
>
>The cam that is at that location, however cannot be connected to
>over the WAN. Local addr works fine. But the likes of
>http://Whatever.DynDNS.Org:1234 does not.
translation? I assume your cam is on port 1234 and you're not also
using that port for anything else at the same time.
>I'm pretty sure I have port forwarding set up correctly - mainly
>because:
>
>- Port forwarding is working for the server PC at that location
>
>- There are so few things to specify (local IP addr, port range,
> protocol type) that I don't think even I could have fouled
> it up.
>
>Only thing I can think of is that the server PC and the IP cam
>might be different types of devices from the cable modem's
>perspective.
you're using a combo modem-router? What's its make and model? We may
want to access its manual. If it's a combo unit, do you have access to
its config section?
>The modem is definitely seeing the IP Cam bc it appears on it's
>"Connected Devices" list with he expected local IP addr.
>
>To that end, I tried turning the cable modem's firewall totally
>off, but no joy.
they have a firewall. Further evidence that you might be saddled with
a dreaded combo unit. Yuck.
>I can't find anything about a make/model in the modem's web pages
>except for:
>
> eMTA & DOC SIS Software Version = 7.4.63a
>
>
>Could there be some other setting in the modem/router that would
>prevent port forwarding to the IP cam but not to the server PC?
dealing with.
(PeteCresswell)
Jun 20, 2012, 7:42:18 AM6/20/12
to
Per Char Jackson:
No, using the WAN IP on the server does not work.
--
Pete Cresswell
>Does it work if you use the WAN IP address rather than the DynDNS
>translation?
I left that part out...
>translation?
No, using the WAN IP on the server does not work.
--
Pete Cresswell
Char Jackson
Jun 20, 2012, 10:27:18 AM6/20/12
to
On Wed, 20 Jun 2012 07:42:18 -0400, "(PeteCresswell)" <x...@y.Invalid>
wrote:
Just to be clear, I meant using the router's WAN IP from a location
out on the WAN. (The server is on the LAN and won't have a WAN IP.)
wrote:
out on the WAN. (The server is on the LAN and won't have a WAN IP.)
(PeteCresswell)
Jun 21, 2012, 7:40:26 PM6/21/12
to
Per Char Jackson:
server. Does not work.
OTOH, 10.0.0.133:1234 works.
I've been out of town and offline for the past couple days.
Yes, it is a combination cable modem/router.
Will come back soon with a make/model.
--
Pete Cresswell
>>I left that part out...
>>
>>No, using the WAN IP on the server does not work.
>
>Just to be clear, I meant using the router's WAN IP from a location
>out on the WAN. (The server is on the LAN and won't have a WAN IP.)
I meant using the Whatever.DynDNS.org:1234 address from the
>>
>>No, using the WAN IP on the server does not work.
>
>Just to be clear, I meant using the router's WAN IP from a location
>out on the WAN. (The server is on the LAN and won't have a WAN IP.)
server. Does not work.
OTOH, 10.0.0.133:1234 works.
I've been out of town and offline for the past couple days.
Yes, it is a combination cable modem/router.
Will come back soon with a make/model.
--
Pete Cresswell
Char Jackson
Jun 22, 2012, 12:01:52 AM6/22/12
to
On Thu, 21 Jun 2012 19:40:26 -0400, "(PeteCresswell)" <x...@y.Invalid>
wrote:
>Per Char Jackson:
>>>I left that part out...
>>>
>>>No, using the WAN IP on the server does not work.
>>
>>Just to be clear, I meant using the router's WAN IP from a location
>>out on the WAN. (The server is on the LAN and won't have a WAN IP.)
>
>I meant using the Whatever.DynDNS.org:1234 address from the
>server. Does not work.
I'll repeat my suggestion to attempt access from a WAN location, but
using the router's WAN IP rather than the DynDNS translation in order
to rule out any issues you might be having with DynDNS.
>OTOH, 10.0.0.133:1234 works.
>
>I've been out of town and offline for the past couple days.
>
>Yes, it is a combination cable modem/router.
Sorry to hear that.
wrote:
>Per Char Jackson:
>>>I left that part out...
>>>
>>>No, using the WAN IP on the server does not work.
>>
>>Just to be clear, I meant using the router's WAN IP from a location
>>out on the WAN. (The server is on the LAN and won't have a WAN IP.)
>
>I meant using the Whatever.DynDNS.org:1234 address from the
>server. Does not work.
using the router's WAN IP rather than the DynDNS translation in order
to rule out any issues you might be having with DynDNS.
>OTOH, 10.0.0.133:1234 works.
>
>I've been out of town and offline for the past couple days.
>
>Yes, it is a combination cable modem/router.
(PeteCresswell)
Jun 22, 2012, 1:32:06 PM6/22/12
to
Per Char Jackson:
Long Answer: That was near the top of my little check list - ever
since I burned myself a few weeks ago by having a utility
resetting a DynDNS pointer that should have been left alone.
--
Pete Cresswell
>I'll repeat my suggestion to attempt access from a WAN location, but
>using the router's WAN IP rather than the DynDNS translation in order
>to rule out any issues you might be having with DynDNS.
Short Answer: Done that.
>using the router's WAN IP rather than the DynDNS translation in order
>to rule out any issues you might be having with DynDNS.
Long Answer: That was near the top of my little check list - ever
since I burned myself a few weeks ago by having a utility
resetting a DynDNS pointer that should have been left alone.
--
Pete Cresswell
Char Jackson
Jun 22, 2012, 2:15:09 PM6/22/12
to
On Fri, 22 Jun 2012 13:32:06 -0400, "(PeteCresswell)" <x...@y.Invalid>
wrote:
Ok, I'll assume it didn't work and that details are not available.
Get a bigger hammer. Upgrade to a service tier that provides an
additional public IP address, assign it to the camera, and you're
done.
Sorry, with the information I have, I don't have enough to offer a
better solution. I would definitely dump DynDNS until you get things
working, though. That much is a no-brainer.
wrote:
Get a bigger hammer. Upgrade to a service tier that provides an
additional public IP address, assign it to the camera, and you're
done.
Sorry, with the information I have, I don't have enough to offer a
better solution. I would definitely dump DynDNS until you get things
working, though. That much is a no-brainer.
(PeteCresswell)
Jun 22, 2012, 2:47:01 PM6/22/12
to
Per Char Jackson:
I'm guessing the first...
--
Pete Cresswell
>Get a bigger hammer. Upgrade to a service tier that provides an
>additional public IP address, assign it to the camera, and you're
>done.
"Service Tier" with the IP provider? Or with a DynDNS analog?
>additional public IP address, assign it to the camera, and you're
>done.
I'm guessing the first...
--
Pete Cresswell
Char Jackson
Jun 22, 2012, 3:52:57 PM6/22/12
to
On Fri, 22 Jun 2012 14:47:01 -0400, "(PeteCresswell)" <x...@y.Invalid>
wrote:
Yeah, with the ISP...if they offer such a thing as multiple IP's. I
haven't checked since cable Internet came to my area in 1997. Back
then 5 public IP's were included with every account, but that went by
the wayside long ago. Anyway, if you could stick a public IP on that
camera you could forget about port forwarding.
wrote:
haven't checked since cable Internet came to my area in 1997. Back
then 5 public IP's were included with every account, but that went by
the wayside long ago. Anyway, if you could stick a public IP on that
camera you could forget about port forwarding.
0 new messages