Re: Routing IP cameras to internet



Thank you for your experienced advice, your points are well taken. Our
bandwidth/budget options are maxed out.

However, my boss is the type of guy that you have to show an example, so I
must press onward. I will try a Netgear forum for the firewall portion, and
report any answers here for others who may benefit from the information
later. Would you comment on the SBS NAT portion? How do I securely bridge LAN
to WAN on the SBS server?

"Joseph Vito Bacino Jr." wrote:

That will not make an Difference if you give them an external IP
Or use a VPN. (VPN might add a little overhead, but not that much)
It looks like your ISP is / will be your problem.

______________________________
Joseph Vito Bacino Jr
DV Technical Solutions Inc.
www.dvtechsolutions.com

OrthoResearch wrote:
He was not satisfied with the frame rate and image clarity using that method
during an earlier test. I think our ADSL upstream and downstream compete for
bandwidth with poor results. I thought direct routing might improve the
quality by reducing bandwidth overhead.

"Bill Sanderson" wrote:

Why not have the boss connect via VPN?

"OrthoResearch" <OrthoResearch@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:18E51D8B-C480-4F82-BC67-60C90C745E92@xxxxxxxxxxxxxxxx
Searched these forums and i haven't found this topic discussed:

SBS2003STD 2NICs with Netgear FVS318 Prosafe firewall router. Firewall
cabled to netopia 3364N in bridge mode acting as ADSL modem only. Standard
SBS service ports pass firewall packets to sbs server WAN. SBS server has
simple NAT only.

ISP AT&T provides ADSL w/ 7 Public static IPs 68.xxx.xxx.161 through .167
where .166 is considered gateway and .167 broadcast. Netgear firewall WAN
IP
set at 68.xxx.xxx.165, mask *.248, GW *.166.

4 surveillance IP cameras (each has onboard webservers) have internal
private static IP addresses assigned 192.168.xxx.121 through .124
Internal workstation IP surveillance software is pointed to internal IPs
to
gather images from cameras during security events. Works great!

Boss wants to see cameras from home during event. Trying to securely
connect
routable IP 68.xxx.xxx.161 to internal IP 192.168.xxx.121. I am unsure how
to
get hardware firewall to see packets at 68.xxx.xxx.161 to route them to
SBS
server WAN NIC. Then I am unsure how to configure NAT to hand packets to
Camera webserver at 192.168.xxx.121.

Your guidance is appreciated. Thank you.

.



Relevant Pages

  • Re: Routing IP cameras to internet
    ... I thought direct routing might improve the quality by reducing bandwidth overhead. ... SBS2003STD 2NICs with Netgear FVS318 Prosafe firewall router. ... SBS service ports pass firewall packets to sbs server WAN. ... gather images from cameras during security events. ...
    (microsoft.public.windows.server.sbs)
  • Re: Routing IP cameras to internet
    ... SBS2003STD 2NICs with Netgear FVS318 Prosafe firewall router. ... cabled to netopia 3364N in bridge mode acting as ADSL modem only. ... SBS service ports pass firewall packets to sbs server WAN. ... gather images from cameras during security events. ...
    (microsoft.public.windows.server.sbs)
  • Re: Routing IP cameras to internet
    ... SBS2003STD 2NICs with Netgear FVS318 Prosafe firewall router. ... SBS service ports pass firewall packets to sbs server WAN. ... gather images from cameras during security events. ...
    (microsoft.public.windows.server.sbs)
  • Re: Routing IP cameras to internet
    ... SBS2003STD 2NICs with Netgear FVS318 Prosafe firewall router. ... Firewall cabled to netopia 3364N in bridge mode acting as ADSL modem only. ... Standard SBS service ports pass firewall packets to sbs server WAN. ... Internal workstation IP surveillance software is pointed to internal IPs to gather images from cameras during security events. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS Unable to resolve domain but Bind can?
    ... The SBS server has a public IP and it is not behind or running any firewall. ... increases efficiency by allowing DNS to resolve larger DNS responses without ... Large DNS responses are answers that have several CNAME or MX ...
    (microsoft.public.windows.server.dns)

Loading