Don't over-complicate this.
DDNS will point to your computer at home. Setup that software and get that working first, forget about the camera for the moment. Once you have that resolved, set the port on your router at home for the application and point that to your camera. From what you said above it looks like (80), so its a web app. Then from your software just point to the DyDNS domain you registered and you are done.
All...
User Profile
Collapse
-
This is the best advice, I would suggest to any client that if they don't hire me, to hire someone.
Just remember with VPN to KISS it. Like many things VPN can become encumbering and difficult to manage if you overdo it.
If you have 1 central location, unless you need a constant connection to remote locations, site-to-site VPN is probably overkill. But again that is a determination you and the specialist will need to make.Leave a comment:
-
Orange-White
Orange
Green-White
Blue
Blue-White
Green
Brown-White
Brown
Make sure you made the cable with standard order rules
If cable is good, check if switch is managed. If so, enter management and resolve. If not, remove switch and test connection. If successful, switch is bad. If not, check nic. If nic is bad, replace. If nic is good, router config is wrong or network interface...Leave a comment:
-
No worries sicarie, as promised here is what was ultimately missing and how one can do it themselves.
We must follow basic routing rules for internal networks. So if you had multiple routes and paths they must be defined, but if we are restricting traffic on any of those interfaces we must make exceptions.
This is the external config (modified for usable data)
...Code:ASA Version 8.0(2) ! hostname external
Leave a comment:
-
Rules were never a problem, I finally resolved the issue.
I was missing a static route from the DMZ to the Gateway of the "Internal" network.
I will post a final "cleaned up" config of both routers next week highlighting examples of key elements.Leave a comment:
-
There is no ICMP going to the outside world, only from the inside of the internal ASA to the DMZ behind the external ASA.
The ultimate problem is communication from the DMZ to the inside of the internal ASA.Leave a comment:
-
Mainly this
...Code:From the DMZ to the "Internal Network" (the main challenge, not working) DNS ICMP tcp/50389 upd/50636 SMTP (to the internal exchange server) From the Internal Network to the DMZ (everything currently is working, but as other changes might cause this to close I will need the following) ICMP tcp/50389 udp/50636 HTTP HTTPS SMTP (from the internal
Leave a comment:
-
Ok, so it sounds like you need 1 server to act as an ADC to tie in with your corporate site, and depending on how much bandwith is required by the ERP software + bandwidth for regular usage, I'd recommend @ 5-10MB, Fiber if you can get it. Its quite reasonable. Just start calling fiber providers and get quotes.
AS for your server, your corporate office should really be heading up this project, as if you want them to be tied together...Leave a comment:
-
Internet Options > Security Tab > Click Trusted Sites > Click the Sites button. Add them there...
And no.Leave a comment:
-
go to your security settings and add 127.0.0.1 as a trusted host. you can also add http://localhostLeave a comment:
-
ADS = 1 server, what else do you need a server for?
Are you saying you want to host your own website? if your are smart, that is a small server on the perimeter network.
So that would be 2, 1 decent, 1 small.
Bandwidth depends on availability and scalability. Do all of your users need video conferencing at the same time? If so that is much more than 5-6 users.Leave a comment:
-
-
-
Webhosting is usually done by ftp
they gave you a host name...
try ftp.hostname.co m but you should use an FTP clientLeave a comment:
-
2 Cisco ASA 5510's, an Exchange Edge Server, a DMZ, and a minefield.
Disclaimer
Before you ask why I don't just put everything on the 192.168.1.0/24 network, let me just say I do this on another person's will.
Info:
For purposes of this question I will refer to "Internal Network" as the 192.168.0.0/24 located on the inside interface of the internal ASA
Domain names and public Ip's changed for protection of the client.
Domain names changed to domain, public...
No activity results to display
Show More
Leave a comment: