CCTV Network Program

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a CCTV PC and program running on my network, which obviously as been
designated an IP address. Now this CCTV program is web enabled, meaning that
if I type in the IP address of the CCTV Program in the URL bar it will show
me the program and all the cameras etc, basically like typing a network
printer IP address in the URL, which gives you the configuration pages.

This only works internally. I want to get this working on the outside of my
network for example getting it working at home for disaster recovery
purposes.

So far I have opened the port which is 443, or so I was told, but when I go
home it doesn’t work. Is there something else I need to do? Does anyone know
how to do this that could help me out?
 
There is so much more to this that I don't even know where to begin.

How is opening an SSL port going to matter? What do you mean when you say
you "opened the port" since that doesn't even begin to describe all that
must done?
 
yeah sorry i got the port number mixed up, basically i have opened port 80,
8016, 8017 on my router which is used for web guard (8016, 8017). So in
theory i should be able to go home, type in the static ip address of the CCTV
PC in my URL and i should be able to see the program. But it does not
reslove, which i knew anyway, but it is what the manfacturer told me to do,
which i thought doesnt even make any sense because how does my home PC know
that the static IP address belongs to my works domain.

The PC that has the software installed is a client PC running Win XP with a
static IP address. Is there anyway of doing what i have said. I got it
working internally just not externally.
 
chrisjowett said:
yeah sorry i got the port number mixed up, basically i have opened port 80,
8016, 8017 on my router which is used for web guard (8016, 8017).
Click to expand...

Same question. What do you mean by "opeing a port"? Allowing traffic to
pass on a particular port number does not tell traffic where to go or what
to do with itself.
theory i should be able to go home,
Click to expand...

No it won't. Not even in theory.
type in the static ip address of the CCTV PC in my URL and i should be able
Click to expand...
to see the > program.

What static IP#? Static IP# attached to what?
which i thought doesnt even make any sense because how does my home PC know
that the static IP address belongs to my works domain.
Click to expand...

Domains don't have anythng to do with it since you were using an IP# and not
a Domain Name.
The PC that has the software installed is a client PC running Win XP with a
static IP address. Is there anyway of doing what i have said. I got it
working internally just not externally.
Click to expand...

What static IP#? Static only means that it is not dymanically
assigned,...it has nothing to do with whether is it a publicly registered
valid Internet address or if it is an RFC Specified Private address from one
of the RFC Private Address Ranges. You cannot directly access RFC Private
Addresses from the Internet. They have to be Static NAT'ed (aka Reverse
NAT).
 
ok seen as you are just picking out bits of what i am saying wrong/or you
dont understand,
which isnt really helpful what so ever and its getting me know where
Because it doesnt tell me what i am doing wrong at all...

i will tell you what i have so far. I got a PC with the CCTV program
installed and on the NIC of that machine
is a static IP address. Now on my internal network on a different Cleint PC
i can type the Static IP address
of the CCTV PC in the URL bar and i can see the program, basically see all
the cameras around my building.
I want to be albe to see this outside my network so when i go home i can
check it. HOW
 
chrisjowett said:
ok seen as you are just picking out bits of what i am saying wrong/or you
dont understand,
Click to expand...

It is that I don't understand.
There are too many possible meanings to the words you use and if I guess at
what I think you mean we will be here forever. People often get ticked off
when I (or others) try to pry information from them,...but it has to be
done.
i will tell you what i have so far. I got a PC with the CCTV program
installed and on the NIC of that machine
is a static IP address. Now on my internal network on a different Cleint PC
i can type the Static IP address
of the CCTV PC in the URL bar and i can see the program, basically see all
the cameras around my building.
I want to be albe to see this outside my network so when i go home i can
check it. HOW
Click to expand...

Again, "static IP address" doesn't mean anything. I need to know if the
Device you are connecting to is behind a NAT Firewall or a Proxy Server and
is using a RFC Private Address. If it is, than you have to perform a Static
NAT in the case of a NAT Firewall ,...or perform "Server Publishing" in the
case of a Proxy (MS ISA, or MS Proxy for example). When you connect to it
from home you have to contact the NAT Firewall or the Proxy *as if* it was
the device you were wanting,...the Static NAT (or Server Publishing) does
the rest of the work. If you think about this you will see the the terms
"opening a port" and "static address" don't mean anything.
 
The device i am trying to connect to is behind a NAT firewall i am not sure
about the RFC Private Address, not come across that before, do you mean the
IP of the NAT Firewall (sorry but i havent done this before so excuse my
ignorance)

Ok so the device is behind a NAT firewall how do i perform a static NAT?

thanks again
 
chrisjowett said:
The device i am trying to connect to is behind a NAT firewall i am not sure
about the RFC Private Address, not come across that before, do you mean the
IP of the NAT Firewall (sorry but i havent done this before so excuse my
ignorance)
Click to expand...

These are the RFC Private Ranges. They are not compatible with the Internet
and can never be accessed from the Internet:

Class "A" 10.0.0.0 -- 10.255.255.255
Class "B" 172.16.0.0 -- 172.31.255.255
Class "C" 192.168.0.0 -- 192.168.255.255

These are reserved ranges that can never be used for anything anywhere:
127.0.0.0 -- 127.255.255 Reserved for LocalHost
224.0.0.0 -- 224.255.255.255 Reverved as Multi-Cast addresses
There are others but I can't think of them right now.
Ok so the device is behind a NAT firewall how do i perform a static NAT?
Click to expand...

It depends on the Device you use, they are all different. you have to
consult the documentation,...but here is the general idea.

You set the device so that whenever it receives traffic destined to its
external IP# on the port# that the CCTV runs on, the traffic is passed back
to the internal machine's IP# that runs the CCTV on the same port#. The
correct terms for this are Static NAT or Reverse NAT,....however some
documentation with SOHO equipment *incorrectly* referes to it as Port
Forwarding, or IP Forwarding.


As an FYI.......
Tecnically Port Forwarding is Port Address Translation (PAT) which is not
what you are doing.
Tecnically IP Forwarding is just normal every-day Layer3 Routing. This is
seen in Unix/Linux and way back in the old NT4 systems where you turned on
"routing" by enabling IP Forwarding, which also is not what you are doing.

But the SOHO Market has already butchered the dictionary by now and there
probably isn't much chance of fixing it.
 
Back
Top