Port Forwarding and PPPoE

Please confirm that when you access the camera internally you go to http:/192.168.0.55:1111  If not, then what do you use?

If by static address you meant you tried to connect to 192.168.0.55:1111  that will not work remotely.  you have to connect to the ip address DHCP assigns to your WAN connection, use http://whatismyip.com or similar to find your external ip, then the ip:1111 should work remotely if your port mapping in your router forwards port 1111 to 192.168.0.55
You will need to run a dynamic dns client if you don't want to be checking periodically to see what external address dhcp has assigned to your router, which will change frequently on a pppoe connection.

I can connect to the camera appliance (192.168.0.55) internally using IE and able to view the cameras. The IP address assigned to the DSL connection is static (does not change) and routable and I can ping it from a remote computer. I have configured the Linksys router - Port Forwarding - to use port #1111 TCP/UDP and the appliance address of 192.168.0.55. When I go off site and use IE I type in the routable address assigned to the WAN interface plus the port number e.g. http://67.222.111.444:1111 but I cannot connect to the camera appliance. Thanks

Perhaps you should have just answered my question, which again, is this.  When you are at the site where the cameras are, do you, in your browser access them by:
a) http://192.168.0.55
OR
b) http://192.168.0.55:1111
This will help diagnose the issue.

At the site - http://192.168.0.55

try going into the camera configuration and set it to port 1111 instead of port 80 for its web interface.  that should make it work the way you are addressing it, but you will then have to access it with http://192.168.0.55:1111 from the internal network also.

"We have a DSL connection to a Linksys Router with PPPOe enabled. There is a static routable address assigned to this line. The WAN side of the router is set for DHCP. " 
This is a bit confusing because on the WAN side of the Linksys it shoudl be set for PPPoe OR DHCP..  PPPoE is NOT equivalent to DHCP...  
FIrst, either the DSL router/modem is providing the PPP connection or it should be "bridged"...  
- If the dsl router is providing the PPP, the attached linksys can use dhcp or (better yet) assign it a static IP.
- Alternately, if the dsl router is bridged, then the Linksys MUST be set for PPPoE and NOT DHCP mode on the WAN..
 
Ideally, I would "bridge" the dsl router and run PPPoE on the linksys AND I wold place the CCTV system in the Linksys DMZ...  The CCTV would be accessible via public (x.x.x.x) & private (192.168.x.x) IP with the need of config'g ports.    P2E

I am assuming that the port number you have open on the router is the same port that is configured on the camera. Since, you cannot access the camera remotely and working fine on the LAN it only means that the port is NOT yet properly open on the router that is why the firewall on the router is still blocking it and that is the reason why you cannot access it remotely.

API NOC is correct about port 80 being easiest so long as you don't have any other devices on your network serving web pages since port 80 is the default, that is why you don't need to specify it on the ip address.  using 1111 is more secure and allows you to set up other devices like a second camera on 1112 and follow the same format for additional devices if that is what you need.  The current problem is that your camera is serving its web page on port 80 and your router is relaying the connection on port 1111, unless your router is a high end load balancing type, it will not do port conversion, so the camera needs to be set to serve its page on the same port number you use from the outside connection, regardless of the port number you pick.

I have changed the port number in the DVR (Web Port) to 8080 and also in the port forwarding area of the router. I can now access the DVR remotely with the following IP address and port number: http://67.222.111.444:8080 Now the problem seems to be associated to the login. I type in the user name and password and get the following - "Login failed: Can't connect to EDR server, please contact..etc" I use the same credentials internally and get logged in without any problems. My OS at SOHO is a 64 bit version of Vista - could this be part of the problem?

as API NOC mentioned in post 23493741 port 8080 is the default port that the linksys router uses to configure the router from the internet.  You may want to pick another port like the 1111 you mentioned before to eliminate confusion and avoid possible conflicts with the router.  If you want to keep 8080 for the dvr, change the linksys remote access port to something else and see if that makes it work.

Generator, why don't you just follow my instructions?

I will try your solution and report back. Thanks

If the router & CCTV is working with 8080, forget about changing it port 1111 - if it ain't broke why try & fix it???  Your issue is NOT access it is LOGIN & yes, the CCTV app must be able to support a 64bits.  

Check and see if the system allows for a different login for remote (vs local) access...

I changed the DVR Web Port to 80 and changed the port forwarding to port 80 - this configuration worked. However, I had to re-start the DVR and nothing worked after that. I will be returning to the site on Monday to check if a firmware upgrade may be necessary and try these configurations again.

Gen, not a firmware issue - you were connected (23504359) and working via LAN & WAN...  Now it seems you are slowing starting to work backwards...

As I stated earlier - I recommend simplify the connection & "bridge" the dsl router and run PPPoE on the linksys.   Then, once you verifiy the PCs are online behind the Linksys, I would configure the CCTV system (in the Linksys) for DMZ...  

The security system will be accessible via public (x.x.x.x) AND private (192.168.x.x) IPs WITHOUT the need of config'g ports.  

If you need specifics on config'g bridge, PPPoE or DMZ - it is best you post the specpfic make/modem info of the equipment being used...  P2E

The port forward configuration I suggested will work, and has worked.  We'll see what happens on Monday.

API NOC - The DVR needed the firmware upgrade - all is well and working great. Thanks for your help

Thanks for everyones feed back - much appreciated.