Moved to www.NetworkCameraCritic.com

One of the biggest benefits of having IP cameras is being able to access them from the internet. Many of us have smartphones, iPads or netbooks that we take with us and it would be great to check in on the place, a pet or the elderly while at work, in a coffee shop or while traveling. Some cameras have 2 way audio, so you can even talk to the person or pet.

The problem many of us have is how do we do it. We all know that if we go to a certain IP address on our home browser, we can configure and view the camera, but how do we do the very same thing when we are not home.


There’s several steps into making this work, so it’s best to start at the camera. By default, most IP cameras are assigned a temporary IP address by your router. This is composed of 4 numbers from zero to 255 that are separated by periods that is how you find your camera. Then you use a program the vendor provided on a CD that finds the IP address assigned to the camera. You click on that and it brings up the in-camera software that lets you view and configure the camera. The problem with this is that it’s likely that this address will change next time turn off and then back on the router or camera. The first step is to set a fixed address on the camera so that it doesn’t change and you can always find it.

To do this, you will have to go into the configuration screen for your camera and set the option to have a fixed IP address and not use DHCP. Many times, unchecking DHCP will present you with the necessary fields for an IP address, subnet mask, gateway and DNS. This may be overwhelming. The easiest place to get this information is to go on a PC that is on the network and open a DOS window (on Windows, press the START button and then type “command” or on a Mac, run Terminal). In the DOS window, enter the command “ipconfig”, on a MAC enter the command “ifconfig”. You will see the IPv4 address, the subnet mask and the default gateway. Use this subnet mask (typically and default gateway (the IP address of the router). For an IP address, use the first 3 sets of numbers and chose a higher number up to 253 for the last, for example, if it’s, you can use an IP address like Just make sure that you do not use the same number twice, it must be unique and not interfere with the lower number that are used by DHCP, so I would recommend you start at least at an IP address of your PC plus 25. For DNS, put either the gateway address or as a last resort.

It will also give you the option of a port number. A port number is what is used to allow a single IP address to have multiple devices. The default is typically 80, but if you want to have more than one camera, you need to use a different number. To avoid port conflicts, it’s better to use a number higher than 8000 but less than 60000. For example, if you have 3 cameras, you can use 10001, 10002 and 10003. From that point on, since port 80 is the default, you must specify the port number after the IP address separated by a colon when accessing the camera, for example if you used 10002, you will use to view the camera from your browser at home.

Foscam IPAxis TCP


Once you have a fixed IP address, the next step is to update your routers firewall with this information. The job of the router is to use a single connection to the internet and allow you to use it with multiple devices like cameras and computers. By default, the router has what is called a firewall and it’s job is to block anyone trying to get into your network including you. You have to define which devices can been accessed from the internet. You do this by going into the firewall configuration screen (sometimes called a Port Forward screen or Application & Gaming) and tell it which IP addresses can be accessed and what port number they are using. Some are as simple as putting in address and port 10002 (start and end are typically the same). Some have separate screens where you define a service. A service is a port number assigned to a name, like Camera2 and port 10002, then in the other screen, you select Camera 2 and specify the IP address, If it asks for protocol, it’s TCP, but if you leave it at the default of Both it doesn’t matter.

Below are sample screens from common routers. While I can’t possibly show you every router, you’ll find that once you find the port forward or firewall screen, the process is simple.



When you are home, you access the camera using what is called the LAN address. This can only either start with 192.168 or 10…, so you know you are using an internal address if it starts with this. To access the cameras remotely, you need it’s WAN address. This is the address that the router uses to connect to your cable or DSL service provider. Any router will have the ability to display this, but it’s much easier to go any PC on your home network and go to http://www.whatsmyip.org. This will display your IP in large numbers on the top of the page. You should now test this, enter the IP and port and see if you can access the camera (ie. Some routers block the ability to loop back to your own network so it’s possible that this won’t work from home, so try it from a neighbor or friends network and see if you can connect. If it works you can use this to access your camera from anywhere in the world with one caveat, it may only last a few hours or at best a few days, so onto to the last step in the process.


Service providers have many, many customers and it would be very expensive to give each and every one of us a fixed IP address as you did with your camera in step 1. So they use DHCP and assign you temporary IP address and that can change. Some providers set this at once a day, some at once a week, it varies, but you can’t rely on this address to be fixed for very long.

To get around this, there’s a service called Dynamic DNS or DDNS. The way it works is a DDNS company assign you a host name, like myhome.dyndns.com and then your router or camera has the ability to keep this up to date every time your service provider changes the WAN IP address. There are some large DDSN services that are free and I would recommend DynDNS (http://www.dyndns.com). You create an account, pick a domain name from what is free (you can have your own domain name, but not for free), then pick a hostname which is the part of the name you can choose as long as someone else is not using it. Use only one hostname per location, so one for your entire home and maybe one for your vacation home or business.

The best place to maintain this is on your router. Check to see if it supports DDNS and most do. You’ll have to specify the name you chose, your username and password and the DDNS provider you picked. If your router does not support this, many cameras do. ONLY DO THIS ON ONE DEVICE ON YOUR NETWORK.

Once this is set up, you can use this name and port address to visit each camera at home. For example, http://myhomecams.dyndns.net:10001 for one camera and http://myhomecams.dyndns.net:10002 for the other.

If configuring the router is too confusing or not possible, there’s software to do this for you, but at a cost. The most popular is http://www.PortForward.com. This will only take care of Step2, you will still need to do the other steps and the software still requires the information noted above, so I don’t think it’s a good investment. You can always contact the support group for the router vendor to get help. Don’t contact me as I probably do not have the same router as you and won’t be of much help.



  1. 1 Big D
    September 24, 2010 at 6:09 am

    Congrats. Although I had to learn the hard way piecing everything together on my own (ugh), I believe this is one of the best all inclusive postings of information online regarding this topic. I’m sure it will benefit those starting out or simply those stuck in limbo.

    Excellent job.

  2. 2 JDW
    September 29, 2010 at 6:40 pm

    Thanks for taking the time to put this information up. I’ll be using it soon. Much appreciated.

  3. 3 miker
    September 30, 2010 at 8:01 pm

    Wonderful stuff, I just wish I’d found something like this before I setup my system. It’s been running for over a month without a hitch . . . that is until I had a power outage and had to redo all the addresses ’cause I didn’t use the fixed IP trick you listed above. Plus I had them all setup with DDNS active, not sure what that’s been doing to DynDNS’s system (oops). In closing, this is excellent advice and I’m sure others will benefit from it. Keep up the good work.

  4. 4 Roy Brown
    November 7, 2010 at 11:56 pm

    I am still having problems with my Foscam IP cameras. I have 4 set up at a campground which is closed for the winter. I can get into 2 of them by contacting them one at a time. I would like them to all come up on the screen so I can switch between them. I have used IP adresses such as ,116,116,118 and use port 90,160,130,and 1490 the router is set up with these settings. It is a Linksys router are these port numbers ok or should I use different ones?
    The router is Mod.WRT54G the cameras are Mod.IPCAM01

    Hope someone can help

  5. 6 miker
    November 9, 2010 at 3:53 pm

    I’m running a Foscam, 2 Cisco’s and a Linksys, and the software that comes with each of them won’t recognize the other brands. I found a commercial package with a 60 day trial (that sets up with 21 days left?) which works really well called Webcam7 @ http://www.webcamxp.com/download.aspx. They allow free personal use with only 1 cam, or the trial version with all 4 active.

    The truly best thing was a free app for my Droid called IP Cam Lite (http://www.androlib.com/android.application.com-rcreations-webcamviewerpaid-jjpm.aspx). This lets me view all 4 at once on the cell phone. It even uses “widgets” that are self updating, so every time I turn the phone on I get a still shot of each cam taken within the last few minutes. The paid version lets you use more than 4 cams and removes the annoying ads.

    I hope this helps.

    • November 9, 2010 at 6:03 pm

      The webcamXP products looks good, at least from what I saw on their website. For about half the price, I’ve been using BlueIris software. I’m able to juggle 6 cams, 4 of them megapixel with the software on an Atom processor based PC and it works really well.

      Thanks for the tip on the android software, will give that a try.

    • 8 johnd
      November 26, 2010 at 1:03 pm

      Thanks Miker – the IP Cam Lite is really slick and fast. Need to upgrade to enable audio though, and not sure it will support two-way if I do that. But nice.
      The PC WebCamXP was less successful for me. Could not access/drive the Foscam with it and will seek another. The Foscam IE (ActiveX) view is pretty flaky it seems – often not connecting smoothly or at all. I need to experiment a bit more.

  6. 9 Tom
    November 23, 2010 at 6:23 am

    Cannot get past steps 3 & 4 with ACTi TCM-1231 camera

    xxxx.dyndns.org:7388 (assigned port) returns No such URL error when I try to access it.

    Blue Iris will not work either – no documentation for setting it up with my camera.

    • 10 miker
      November 23, 2010 at 6:45 am

      You said steps 3 “AND” 4, Did it work using your actual external IP address (68.111.xxx.xx:7388)?
      That should tell you if the problem is with the DynDNS part of it . . .
      But try Blue Iris tech support, I’ve switched from the webcam7 stuff now and love the Blue Iris features.
      Good Luck,

  7. November 24, 2010 at 4:37 am

    I had friend connect directly to IP address:port and he can see the log in prompt and log in but once the data starts the connection fails.

    Also, only can connect via IP address not with dyndns although all the steps in dyndns to test connection pass.

    So technically it is step 4 above that I cannot accomplish.

    Send me a direct email n4nw at n4nw dot org and I will give you user name and p/w and you can see if you can access it.

  8. 12 johnd
    November 25, 2010 at 6:18 pm

    Thanks for this. I got the Foscam FI8818W to use as a monitor for my elderly Dad, and working through the Chinglish documentation was only partially successful, despite me understanding quite a bit about IP ! I had’t set up Port Forwarding very often before and never used DDNS.

    The Firewall on the BT Home Hub is pretty rubbish it seems to me – no easy way to set up access through there, but the DDNS setup at Dyndns.com was pretty smooth and then I set the Webcam to connect there and bingo – it worked (had to port forward the webcam on the home hub too)

    So thanks for the technote – very useful.


  9. 13 Lázaro Maia
    January 16, 2011 at 7:44 pm

    Ola estou com um problema já a camera esta instalada e funcionando dentro da rede, e eu configurei o roteador para liberar a porta 80 mais quando vou ver em um site a porta ainda ta fechada, já criei um login no dyndns. Detalhe meu roteador é um AP Router WR 254 que esta funcinando como gateway, minha camera é uma foscam.
    Pergunta 1: Posso realizar todas as configurações de qualquer computador da rede?
    Pergunta 2: Eu tenho que ter um servidor de video na rede e se tiver todas as configurações tem que ser feito apartir dele?

    Qualquer coisa me add olibetanio@hotmail.com

  10. January 22, 2011 at 9:19 pm

    I gues the Apexis is the same? work with Foscam Software?

  11. January 30, 2011 at 5:00 am

    Thanks for this – a great guide. I hope you don’t mind that I am linking to it on my website http://www.mangocam.com. We are selling Foscam cameras in Australia and our customers will definitely appreciate it. Good work.

  12. 18 Bernie
    February 14, 2011 at 10:22 pm

    Can you take this one step farther for me? My camera is connected to a (D-Link DIR-655) router in a detached garage. That router is wired to a bridge (EnGenius EOC-2610). The bridge connects wireless to a (Linksys WRT54GL) router in the house which connects to a cable modem.

    • February 15, 2011 at 5:41 am

      The bridge should have no firewall on, it takes no IP address, it just connects the router to the cable modem. So it’s all up to the cable modem handle the port forwarding.

      • 20 Bernie
        February 15, 2011 at 1:33 pm

        I assume I need to do step 2 on both routers but Lynksys uses 192.168.1.xxx and D-Link uses 192.168.0.xxx. My bridge has as the IP address.

  13. February 19, 2011 at 5:53 pm

    The problem is you have both setup as routers, that’s not good, it works, but can be problematic. You should turn off DHCP on the bridge and allow the main router to be the authoritive DHCP so all devices get the same subnet, for example, they should all see 192.168.0.xxx, no device should be assigned 192.168.1.xxx. Not all routers let you do this, that’s why I run DD-WRT (free) instead of the original firmware when I can.

  14. February 25, 2011 at 6:21 pm

    I thought I had this working, but I cannot access remotely. I can access my local network, I set up the camera with
    I have ATT, a ActionTec modem, Linksys router, iMac, and Foscam F18911W. The router says it is connected to the free dyndns url. If I use the URL I got from dyndns, with the port (10001 for the camera), no access.
    On the router, I have DDNS enabled, it says it is connected. In gaming and applications, both single port forwarding and port range triggering enabled with port 10001. It has as the internet IP address.
    My dyndns account has the IP address as, but says my current address if 70.231.231.xxx?

    • February 25, 2011 at 7:25 pm

      Dyndns has to have your wan address, meaning the 70.231…. You can go to a site like whatsmyip.org and it will tell you your wan IP address that dyndns should have. So when you run the nslookup command on your pc (ie. nslookup myhome.dyndns.com), it should show the same address as what you got from the whatsmyip.org website.

  15. February 25, 2011 at 8:38 pm

    Thanks for the reply. I changed dyndns wan address.
    myhome.dyndns.org:10001 cannot access camera, but myhome.dyndns.org accesses my modem? Maybe the modem is not allowing the access? Its firewall is disabled.

    • February 25, 2011 at 8:55 pm

      You mean you can access the webpage for your router from the internet and not your camera. This would mean that port forwarding of port 80 is working fine for your router. Should work fine for your camera. When all else fails, you can designate your camera internal IP to be the DMZ in your router, that means that all external port requests go to the camera, this way you can make sure it’s not a specific port forward issue and you can change around your port numbers to see if your ISP is blocking, but I doubt it, I use AT&T and never had any issues with port forward except when they gave me what was supposed to be a DSL modem, but turned out to be a single port router instead. This meant I had two routers plug into each other, so I had to turn off the router feature of the DSL modem to make my home WiFi router the authoritive router, otherwise it causes big time mayhem with port forwarding.

      • February 25, 2011 at 11:01 pm

        Again, Thank You for your help and the above turorial.
        I got it figured out. I email Actiontec, the modem maker. They emailed back, quickly, that the modem is also a router. So, like you, I made it a dumb modem, and set up the router to handle the ISP connection, which I found out how to do on the Linksys website. My wife is now able to watch her dog outside.

      • 27 claudio
        February 13, 2013 at 2:08 am

        I have the same problem as Dan, but his comments on the solution is not detailed enough. Could you please tell me exactly what to do with the modem Dlink 500B and Linksys WRT54GRT router? Best regards!

  16. 28 Jayton
    May 13, 2011 at 8:14 am

    Thank you for this post. It would help our company a lot since we are on the process of installing ip cameras. This will be a big help. Thank a lot…

  17. 29 Chris L.
    May 20, 2011 at 1:06 pm

    Thank you so much for this blog. I finally got my Foscams set up on the web, thanks to you. It was embarassing that I couldn’t seem to get them going, but your simple explanations of what was going on made it for me. Please keep reviewing and giving up tips. And if you have any other sites you like, let us know.

  18. 30 brandon
    July 19, 2011 at 3:17 pm

    Thanks. I have a quick question. If I used whatsmyip.org, it gave me 72.x.x.x.x.x.x.x., but if I looked up in router setting, it have different numbers 172.xx.xx.xx. I still can’t access remotely after setting up step 3 and step 4 using the latter IP address.


  19. 32 Diver
    August 25, 2011 at 7:57 pm

    Thanks for this nicely written tut.

    Anyway, I still am looking for a free webcam app that I can run on Win7.

    However, my wish setup is: Foscam works in ‘detect movement mode’ and then sends the stream or pictures on my HDD that sits in the USB port of my router.

    So, I do not have to watch my cam all the time but can more ergonomically connect to my HDD on my router (also via DDNS since it is installed as a FTP drive so to speak) and see whether there are new files (that are pictures or film streams of course).


    21.8.11 stream01
    28.8.11 stream02

    You got the rest….

    Is that possible?

    thank you
    keep watching, ehm rocking

    • August 26, 2011 at 4:58 am

      For Windows, the only free software I know of is Milestone XProtect Go. It has limitations on the number of cameras and the amount of days it will save, but it’s a good way to start, has support for a lot of different cameras. If you wanted to pay a little, BlueIris Software is a good complete solution with remote access, recording, notification and is $29 for 1 camera or $50 for an unlimited amount of cameras.

      There are cameras that can write directly to a NAS disk or to SD cards on the cameras themselves, Foscam is not one of them. Some cameras let you send video as FTP, but I don’t believe Foscam is one of those, I believe it only sends pictures. For example, Axis sends pictures via FTP, not video, ACTi send video via FTP.

  20. 34 Isabelle
    September 5, 2011 at 1:34 pm

    Hello All,

    I really need some help from you.

    I’ve my foscam IP CAM, configuration seems to be alright and running well. I can access from LAN: or from WAN: http://isabelletoong.dyndns.org:81 .. Internet Explorer working fine for this. Now my problem is, I can’t find any IPHONE APPS to run this IP CAM .. I’ve been search through all possible apps put in the ip address or even tried host address with the correct port … username and password .. but still unable to open from IPHONE 4 .. 😦

    just curous, if i can access from external with http://isabelletoong.dyndns.org:81 … but why can’t access from iphone apps ?!?! 😦

    possible for you to recommend me any iphone apps can work well for this IP CAMERA ?


  21. 37 howie
    September 9, 2011 at 11:18 pm

    Wish i found your blog earlier 😦 . I can access my 2 Foscams at home either with their ip address or dyndns.org. but cannot connect them ouside of the house ie. using internet connection at Public library. On the device status of the cameras, the DDNS status shows: “Errors in Network Communication”. I made a mistake by updating the DDNS in both the cameras and the router.
    Your help is appreciated

  22. September 15, 2011 at 10:26 am

    Great article! I’d like to link to it if possible? We sell a lot of iOS Baby Monitor Apps that deal with network cameras. Configuring the port forwarding always trips people up. So a well written guide like this would be a really useful link from our FAQ.

  23. 40 thaimai
    October 10, 2011 at 3:08 am

    I just bought an IP cam (Astak CM-Mole) from Costco and feel paranoid about having to go through a third party video server (Yoics.com) to have remote access to the camera. I have heard of port routing and have done some research. It appears I can follow this process to do without Yoics.com.

    Do you know of any potential problem with using this camera bypassing Yoics?

    Great article and great discussion thread.

    Thanks very much.


    • October 10, 2011 at 4:25 pm

      Several of these types of cameras like Mole and Dropcam have come out to provide more of a plug and play feel than a traditional security camera, but I share your trepidation about putting surveillence video on the cloud. If you know what you are doing setting up port forwarding on your router, then by all means, access the camera directly. Also, you can have it record to a PC using software like BlueIris that supports that camera.

      • 42 thaimai
        October 12, 2011 at 1:37 am

        Thanks for the suggestion. I will try to set up the router and access my cam directly. That bring up the need to decide whether I should go for a fixed address (from my ISP) or should I opt for some url name (from DynDNS or DNS2go), or … In you experience, which option do you think is more secure and private ethan the other.

        Thanks very much for your time and advice.


      • October 12, 2011 at 1:51 am

        There’s not any difference in security using a fixed IP or DDNS so I would save the money and use DDNS.

  24. 44 Caroline
    October 12, 2011 at 6:51 am

    Today’s got to be my luckiest day! Had been sleeping very little in past 1 week fiddling with the set up of 3 EASYN Ipcams and trying to view them remotely. The chinglish miniature manual skipped so many steps that I had to google around to find an understandable procedure to hook these things up. I chanced upon your blog and made 1 change on the cam app setting on my ipad. JUST ! step and voila! I see all my cams on my ipad!!! All 3 cams should have the SAME hostname but 3 different port nos! I had 3 different hostnames (given and printed by the cam supplier on each of the cam boxes) and 3 different ports set up. Thank God for you! Thanks very much. I can sleep well tonite.


  25. 45 sHaDoW
    October 31, 2011 at 11:45 am

    Given the privacy and security implications if someone managed to gain access, in my opinion exposing an IP cam to the outside world thru port forwarding is far too risky. There’s a number of ways to exploit such a system. First, there exitsts a possiblity that the web server on the camera has a vulnrability. I’d be especially suspect of the less expensive camera manufactures, due to the lack of extensive product testing performed. If I remember correctly, 4wire had a bug in its routers that allowed someone to change settings without ever logging in.

    Assuming that the webserver itself has no exploitable bugs, the next thing to consider is whether you’re using http or https when accessing the camera in a web browser. If you use the former, realize that your password to login along with everything else is very likely being sent in the clear, across the internet! I’ve seen some cameras that can use “digest” authentication. This is nothing more then using a hashed version of your password rather than the actual password. More times than not, the insecure, MD5 hash is used. I’ve got two Vivotek’s at home and it was necessary to turn on the https setting in the web gui. Despite having the option to, I was not able to get it to work with certificates I generated myself. Instead I reluctantly let it generate them itself. Of course, even with https turned on, there’s no way verify the camera’s authenticity (assuming you didn’t purchase or use your own certification authority to generate the RSA cert). Hence, a man-in-the-middle type attack is real possiblity. That said, using encryption is certainly better than not using it.

    So what’s the alternative? I personally perfer using VPN due to the transparency it offers. The second way is using SSH tunnelling. SSH requires you to specify each and every host/port you’d like to access. It only works with TCP (and if i remember correctly, UDP) protocols. There is dynamic forwarding using a socks proxy; however, my unrooted Android phone doesn’t allow this to be used, and good luck getting a non-proxy-aware windows app to work. Setting up SSH on a router is very simple, assuming you have the option. If not, I’d look into dd-wrt or one of the other alternate firmwares available. Setup for VPN access, at least in DD-WRT, has been problematic to say the least. Since I’m typically using my smartphone to check up on things and only have a single port to access per camera, SSH was the way to go in this case. Regardless of which method is used, two things are gained. First, you’ll only have a single port exposed on the internet…always a good thing. Second, traffic between your SSH/VPN client and server can be automatically encrypted. This is great for cases when you use want to have to use a non-secure protocol like http or rtsp.

    I realize that this may be a bit deep for some. The easiest step one can take it avoid using http when accessing one’s camera, instead use https (don’t forget to update the port forwards).

    • November 2, 2011 at 8:17 pm

      Clearly there a chance that someone can do a brute force attack to get into your camera. Funny that cheap and expensive is not a determining factor in a cameras security. AVTech provides the use of a Captcha that prevents brute force password crackers from getting in. I would imagine that any methodology, even ssh or tunneling is still vulnerable to a brute force password attack. Sure, the encryption makes it hard to intercept the data as it moves from your network to your remote PC, but the reality is, the hackers don’t want to intercept the communications, they want to get into your camera and encryption doesn’t really help much there. Also, some cameras like from Axis do provide encryption of the web interfacing using HTTPS. But it does nothing for a password attack.

  26. 47 pattpete
    December 23, 2011 at 8:51 pm

    Thanks for the great write-up !

    Just to add –

    1. The router must best set up in the PPOE mode behind the modem set to bridge mode
    for the embedded DDNS client function router to function properly .

    2. A router flashed with DD-WRT firmware offers many DDNS service provider choices (some of them free).

    • December 23, 2011 at 9:01 pm

      PPOE applies only to service providers that make you log in, for example DSL. Most cable companies and U-Verse from AT&T are provisioned by mac address which is it’s own internal set of numbers that uniquely identifies the device, so there’s no need to log in, no PPOE. It’s a little tougher to impossible to put them in any bridge mode, so you are forced into either a modem only and then have your own WiFi router or get an all-in-one modem/router that’s compatible with your provider. I recently switched from the fastest DSL to U-Verse, uses the same phone line but it’s many times faster.

      • 49 pattpete
        December 23, 2011 at 10:38 pm

        Thanks for the explanation . My post above ( December 23, 2011 at 8:51 pm) was based on my experience with a my DSL service (separate modem and router)

  27. 50 bob
    December 31, 2011 at 6:16 pm

    Follow the direction and it work first tine out, i tried usibg the manual that came with and a cesco network tried and could not get working before i received these ssimple instions.

  28. 51 Iann
    January 27, 2012 at 4:17 pm


    i just bought an easyN F serries ip cam which is working fine on the local network and also i can access the cam from the web but i do not have a static IP address from my internet provider and as you may know if my connection goes down and back on again i get a new IP address.

    The camera’s box comes with a sticker on the side with the inner access info, the remote access info which is like oppp.ipcam.hk and the ddns password which is six numbers.Using the Search IP Camera software that come with camera i get a DDNS Status Errors in Network Communication and i can not connect to the camera over the web.Anybody had any success so far?Are those links on the cam’s box (user.ipcam.hk) dead or you need to activate them ?

    Thank you


    • January 28, 2012 at 5:33 pm

      Use a regular DDNS Service such as DynDNS.org or myq-see.com to make the connection work. The DDNS-Services offered by OEM Cam Sellers are unreliable, possibly insecure and some not even in service

      Register your name like:


      Don’t forget to MAP the Cam IP-Number to a specific Port in your ADSL-Router in order to be called correctly.

      Map the IP-Number to (or possibly to as http-service, trough PORT # 88

      DISABLE ‘DHCP’ in the ADSL-Router

      Set the Camera IP-Number fixed to: (or possibly to

      You would then, by example, adress your Cam like this:

      or just: yourname.myq-see.com:88

      or just yourname.dyndns.org:88

      Good luck!

  29. 53 Dustin
    January 28, 2012 at 12:14 am

    I am confused by step three. I got everything else set up and then I went to get my IP address at the recommended website. What am I supposed to do with this IP vs. the one I set up starting with 192?

    • January 29, 2012 at 8:38 pm

      That is your WAN address, the IP address you can access the camera from outside your network, say your in Kathmandu having a Momo dupling at an internet cafe, want to check on the house, you would use this IP address, assuming you setup the camera and router correctly.

  30. January 28, 2012 at 5:20 pm

    If you look for a FREE software capable to be used with different “series” Ip-Cams, please visit the page linked below, I have modified several versions of the popular “IP Camera Super-Client” to enable it to work with multiply chinese OEM Camera Versions of this nice piece of Software.

    Here are the links to the different ‘enhanced’ versions of the IP Camera Super-Client. It’s possible that one program does not work entirely with your Cam’s, the other one may will, so, you better download all four progs.





    No installation is required, just unzip and copy them to a directory and create a Desktop-link to the “SuperIPCam.exe” file. If you start the (each of) software for the first time, if will ask you to allow an ‘active-X’ routine to be installed, so please allow this process, it’s of no danger. Also, you can install several versions of the program, they do not influence each other.

    Modify the last line (L.52) of the “Option.ini” file from “1=C:\2\IpCamData\” to your choosen Datafolder(Name).


    The DevFind.exe, enclosed in some Zip’s, will not find all different “series” IP-Cams in your Network, so, it’s possibly of no real use. I left it in the Software because it belongs there. Also, Progs like ‘Backup.exe’, ‘Watchdog.exe’ & ‘ZPlayer.exe’ e.t.c., are untested at all.

    To uninstall, just delete the Program-Folder and use a reliable registry cleaner program to get the rest out of your PC Registry.

    I have invested a lot of time to make my ‘IP Camera Super-Client’ Software capable to work with multiple “series” of IP-Cameras, having, at times, about 20 different OEM Versions installed on my PC. Since I like the Program so much,I am glad if my Information helps others also.

    If you already use an existing IP Camera Super-Client, you may just replace the existing ‘DevType.dat’ File with one of the ‘DevType.dat’ files enclosed in one of the downloaded Versions. Then start your Client and look how it works.

    The “oemopt.dat” file is another gizmo, containing some information on OEM Suppliers, wich may even prevent the software to accept connection from Competitor-Brands, those using the same “series” spec’s. (b.Ex. EasyN/Vstarcam), a rather bad sample of doing honest Business. At least, from the standpoint of y Buyer and unser. Experienced users may compare the different versions and play around, just remember to make a copy of the original first…

    Good Luck and best regards from Switzerland.


    Note: Unregistered ‘IP Camera Super-Client’ Versions usually function for ONE hour before beeing required to be restarted again in order to work.

  31. 56 Jeff
    February 9, 2012 at 9:49 am

    Hi and help!

    I have spent the last couple of days trying to get my Axis 207w to work and although I have made some progress; I have sticking points:

    I have set a static IP address for the camera
    My pc gets its address from DHCP and my ip camera is connected to the pc
    My router is and both pc and router have a class c subnet address
    I can connect to the axis via my pc and open up the home page using the static address and the port 9080 so basically which works fine.

    Issue 1
    I am unable to see the camera over the WAN even though I have setup port forwarding and saved it. I have checked my firewall and allowed for the Axis camera with its ip address to access in and out of my home network. I have asked a member of my family to try and access from his router and he gets a timed out message.
    Issue 2

    When I disconnect the axis to work wireless I cannot see it despite setting the SSID in my Axis setup and disabling the N facility on the router (only using B/G) The router is a BT Home Hub 3. I cannot even ping the axis camera from my pc without using a cat 5 cable.

    I would really appreciate your thoughts on this as Axis support have been unsupportive to date.

  32. 57 Henri
    February 12, 2012 at 7:42 pm


    I bought 3 IP cams (LoneStar) and I have been trying to set them up for the last 2 days without any luck. I am very bad with computer so I am truly hoping someone can help me.

    – I have set-up the same static IP address for the 3 cameras (192.xxx.x.xxx) => wasn’t clear if each Cam should have their own IP address (ie: 192.xxx.x.xxx / 192.xxx.x.xxy / 921.xxx.x.xxz)? And I have one Port for each camera (aaaaa / aaaab / aaaac) => I believe this is correct
    – I have updated my router firewall (it is an SMC) and I believe I did it properly

    => I can now view my cameras but only if they are plugged to my modem/router. I am not able to view them wireless even though I am at home, using my PC connected to my modem/router.

    I would really appreciate if someone could help me view my cameras without having to plug the cable.

    Thank you for your help.

    • February 13, 2012 at 4:17 pm

      Each camera has to have a unique address on your subnet, for example and The port numbers should also be different so you can access then via your single external WAN address (not 192.168….).

  33. 60 jeff
    February 13, 2012 at 8:39 pm

    agree with Henri and also if you can view via your cable (cat 5) but cannot via wireless; it could be one of the following:
    have you identified the SSID of your wireless network and used your wireless router password
    some IP cameras do not work with the Wireless N Protocol – mine does not so by changing from N to G wireless protocol I was able to use my camera wireless.

  34. 61 Mark
    February 17, 2012 at 2:02 am

    Spent hours getting two Cameras on my home network. I’m not that Network savvy.

    Now I am trying to set up to access externally from my home. Read over many postings here and on other sites.

    I think I am getting closer. Thought I would ask for help. Any suggestions or direction would be appreciated.

    Currently can see both cams on my home network. I identified the IP Addresses from the Internet Cam Admin Tool from Zonet. I can view both cams on the IPCam Zonet Software also buy bringing up each IP Address in IE.

    Just trying to get one cam accessible from outside my home first.

    Looking at Zonet info on the web I see:

    Video Port: Default value is 4321. AV Control Port is used to transmit or receive the AV streaming in the network.

    Web Port: Default value is 80. Since the web server may use port 80, you can use a different port for ZVC7611/ZVC7611W.

    Service Provider = Verizon DSL

    Router: D-Link WBR-2310.
    Under Advanced Port Forwarding

    Name = HTTP
    IP Address = Entered IP Address of Cam1
    Port = 80
    Traffic = TCP

    Name = Video
    IP Address = Entered IP Address of Cam1
    Port = 4321
    Traffic = UDP

    Went to canyouseeme.org to check the ports:

    Success: I can see your service on My IP .. on port (80) Your ISP is not blocking port 80

    Error: I could not see your service on My IP .. on port (4321) Reason: Connection timed out

    As suggested went to No-IP.org and signed up and created host
    Signed up and have it on my PC. Not sure now what to set up on it ???

    • February 17, 2012 at 3:41 am

      The video port is not really something you connect to in that way. You go to port 80, the HTTP port and connect with your browser. Then either an ActiveX or Java program uses the video port, in your case 4321, to transmit the video stream. In your router, you have to open up both ports to the same address, if you only open port 80, you’ll be able to log into your camera but you won’t see video. If you spent hours, welcome to the club. I’ve done this for many years, but when handed a new router, I can spend hours trying to make it work too.

  35. 63 Mark
    February 17, 2012 at 6:32 am

    Thank you with your help and more time I was able to get both cams to work.

    To test it I was able to access cams using a notebook with aircard.

    http://mycamexample.zapto.org:80 This worked Cam1
    http://mycamexample.zapto.org:81 This worked Cam2

    http://mycamexample.zapto.org:4321 This did not work using Video Port

    Thought I would share the settings on D-Link router:

    Name = HTTP
    IP Address = Entered IP Address of Cam1
    Port = 80
    Traffic = TCP

    Name = Video
    IP Address = Entered IP Address of Cam1
    Port = 4321
    Traffic = TCP
    Now for the second cam I just changed the Port to 81

    Went to http://mycamexample.zapto.org:81 This worked


    Name = HTTP
    IP Address = Entered IP Address of Cam2
    Port = 81
    Traffic = TCP

    Name = Video
    IP Address = Entered IP Address of Cam2
    Port = 4321
    Traffic = TCP

    Is there a clean way to view both cams on one window without loading any SW or anything every time I am traveling using someone elses PC. Suggestions?

  36. February 17, 2012 at 11:27 am

    Click to access D00000215_90.pdf

    it seems that the Camera Server is not built to handle multiple camera view, exept by using Client software, at least, there is no such information available. I would contact Zonet and ask them if a firmware upgrade is availeble to do this.

  37. 65 Olof
    February 25, 2012 at 4:36 pm

    Just a quick note that http://www.dyndns.com have ended their free service. See for example;

    Maybe a good idea to update your otherwise excellent post?

  38. 68 Linda
    March 9, 2012 at 4:44 am

    Thanks for this information, it is very helpful. I set up 2 wireless IP Foscam Cameras a couple of months ago. I have ADSL Broadband and use a Netgear DGN2200 Modem/Router. My ISP IP address is dynamic, so I got a dynamic DNS host through dyndns (which by the way lets you sign up for a free 30 day trial, and if you cancel the trial within 14 days they let you keep 1 hostname for free). I’ve done port forwarding, which in my router is in the firewall. I have camera hosting through Mangocam (who also sell the cameras), and both Mangocam and the Foscam camera configuration allows you to set up to 9 cameras and view them together. I have two issues that I’m hoping someone can help me with, because I’ve also wasted many weekends and had many late nights trying to sort it out. I am able to view my cameras remotely through the camera hosting site (from anywhere), and through their IP address and hostname and port number on my home computer, but I’m not able to access the camera configuration remotely using their IP address & port number or hostname and port number on my work computer (maybe that’s a port issue with my work computer) or I’ve done something wrong? But my bigger dilemma is that my wireless internet connection to the cameras keeps dropping out every 10 minutes, which effects the recording because it stops and starts constantly. I’ve tried everything I’ve read and been told to do to fix this problem, and thought perhaps my crackly line might be the issue, but Telstra recently fixed my line and it’s no longer crackly, and the connection is still dropping out up to every 10 minutes. I’ve pinged the camera IP addresses in my router and that’s all good in most cases. I just read before that you should only set up the DDNS in one device on your network, & I’ve set it up in my router, and in both camera configurations, so I’ll now take that info out of both camera configurations and see if that makes a difference? I’ve also tried other channels in my router, which haven’t made a difference to the dropouts. I did only set up one port for each camera in my firewall, which are HTTP Port 80 for one and HTTPS Port 443 for the other. Wasn’t sure which port to do for the 2nd camera because I only had a choice of 1 HTTP (TCP Port 80) and a HTTPS (TCP Port 443), there were no other HTTP Ports, only a list of other types, and it doesn’t give me the option to add another port e.g. 81 that I could see? I just read that I need to set up 2 ports for each camera IP address in my Firewall/Port Forwarding, so I will also try that. I will see which one in my router is for audio/video, but will make sure it’s TCP – hopefully that will stop the dropouts – unless anyone has any other suggestions?

    • March 9, 2012 at 6:13 am

      These cameras have weak radios so I try to keep mine 1-2′ away from my router. I used to have one about 20′ away and it would drop. What happens it will connect with a weak signal but walking in front of the signal, turning on a microwave or any minor thing will cause the signal to drop. I fixed my problem by paying an electrician to hard wire every single camera in my house then switching to PoE cameras and getting rid of the power adapters on WiFi cameras which looks bad. At our weekend home, we have wireless Axis cams, M10 series and they have much stronger radios, works longer distances, no problems with WiFi at all.

      As for DDNS, you should only set it up for the router to update. Having each camera update it won’t hurt, but it’s overkill. Changing channels only helps if you have close neighbors that use the same channel. Some ISP’s block certain ports, it’s best to use high numbers like 8000 maybe for the first, 8001 for the second. Many routers let you specify the port numbers directly, some make you add a service or application, which is port number with a name, for example, you may create a service or app called mycam1 at 8000 and mycam2 at 8001 and instead of selecting HTTP you select mycam1.

      • 70 Linda
        March 9, 2012 at 6:55 am

        Thank you so much, that makes sense to me, I didn’t realise they had weak radios. My cameras are about 5 & 10 metres away from my router. I will have another look at my router to see if I can set my own port numbers in there to 8000 & 8001 & take DDNS info out of the camera configuration of both cameras.

  39. 71 Joe
    May 2, 2012 at 11:19 pm

    I am stuck ppl maybe something simple but i am stuck.
    1) i have airsight camera, i am okay will all but i have choice of dnydns..and some other.. i have account with myq-see
    2) same with router it doesn’t have myq-see option pick under DDNS tab
    someone please help

    • May 3, 2012 at 6:25 am

      It’s best to use a dyndns provider that works with your router. If not, myq-see probably has a program that runs in the background on your PC to do this, but you have to leave your PC on all all the time. If you have tech skills, consider installing DD-WRT or Tomato to replace your router’s firmware as it will likely have more choices.

      • 73 joe
        May 10, 2012 at 5:13 pm

        So just to be clear, it doesn’t matter if my airsight cam has many choices ddns, since it is conected to my router?
        so by updating my router and have choice of other than dnsdny i should be good to go?
        thanks for your reply before…

  40. 74 DH
    May 5, 2012 at 1:40 pm

    I have three Foscams and can see all on my internal network but when I went to set up the port forwarding Fairpoint has blocked all but one of the ports. This seems to mean that I can only access one cam via the net and have set one up successfully using DYNDNS. I’ve read through the posts above but all seem to be able to assign multiple ports for port forwarding. Sorry I don’t have the brand or model of the DSL modem Fairpoint is using, The modem does have built in wireless. Any help would be welcome.

    • May 5, 2012 at 4:41 pm

      Try using high numbers, maybe even 5 digits, like 10000, 11111, 222222. ISP’s tend to not block higher number ports.

      • 76 Linda
        May 7, 2012 at 2:43 am

        Check with your internet provider what ports they block. Westnet blocks port 8080 range and other internet providers block other port ranges. Have you done port fowarding for all of your camera IP addresses or address range? You need to use TCP/UDP ports. It would also pay to add the cameras ports to your Windows Firewall exceptions list if you haven’t already. You might have to add 2 for each camera to your Exceptions List e.g. Camera 1 TCP Port No.# & Camera 1 UDP Port No. #, Camera 2 TCP Port No # & Camera 2 UDP Port No #, Camera 3 TCP Port No # & Camera 3 UDP Port No. #. If you are using a Dynamic DNS Host for these, you should only add the Dynamic DNS Host address to your modem/router, don’t add it to your camera confirguration as well or this will cause an issue.

  41. May 11, 2012 at 1:16 am

    I found two more versions of the IP Camera Super-Client and I ‘enhanced’ them to be adapted to most of the popular ‘Camera – series’ ersions..

    This is the standard version:

    This is for the all new ‘PNP’ Installations:


    I have not found anything related to ‘registering’ the Client Software, so, hopefully, the Clients will not shut down after 1 hours like the older versions.

    Good Luck


  42. 78 Hans
    July 21, 2012 at 11:52 am


    I do hope your blog is still active.
    My problem with an IP camera (a chinese Wifi Oem ID002a bought in Australia) is really basic : it’s apparently not recognized by my router (Orange Lifebox, I’m living in France) when inter-connected by Ethernet cable. So I can’t get the camera’s IP address,with the software provided (IPcamtool.exe) or another one (ipscan.exe, security monitor pro 4.4) nor proceed to any changes of the camera’s setup (such as fixing an IP-address).
    I’m obviously not a wizzard (it’s my first reply to a blog…), but truly feel like a fool.
    Can you help ??
    Thanks so much

    • July 21, 2012 at 10:42 pm

      Camera finding tools rarely work for me, don’t know why, but what I do is this. First look at the back of the camera for what is called the MAC address. It’s a series of letters and numbers. Now log into your router and look at all devices it found on your network and many routers will show you a list by MAC address, then you will know what the IP address is that your router assigned to the camera. If not, you can try all the ones on the list from your browser until you get a hit and since it’s new to the network, it tends to be the highest number.

      • 80 Hans
        July 22, 2012 at 12:48 pm

        Thanks for your reply – my router does indicate MAC addresses of several unconnected “new hosts”, but, unlike with connected items (such as my laptop and a TV decoder) no IP address.
        Can I just make one up myself for these “new hosts”, corresponding to the routers address, such as 192,168.1x ?
        Or how else to proceed ?
        Other question : does the DynDNS service need to be activated (I noticed it was not), and/or should I install a static IP address, if ever I do get a working IP address ?
        Thanks again for your help !

      • July 22, 2012 at 3:50 pm

        If they are “unconnected” then you won’t get a MAC address or IP address. I set all my devices on fixed IP addresses so I know what’s what. You don’t do it from the router, you do it from the device. In Windows 7, to setup a static IP, you have to go into control panel, network and sharing, change adapter settings, double click on the connected adapter, click properties button, select Internet Protocol Version 4 and click Properties, click the radio button that says Use the following IP address and enter one in, the subnet mask (usually and thr default gateway (your router’s address).

        Make the IP address have the same first three octects, so if it’s currently, use the 192.168.1 always and then make the last number something larger, maybe start at 100 so it doesn’t interfere with the DHCP assignments.

        You can use the router as the DNS server, most work that way now, but to be safe, you can use Google DNS (not to be confused with DDNS which is totally different), and

        None of this has anything to do with DDNS. That’s once you have have setup your static IP on the camera and you set port forwarding for that in your router and have tested accessing your camera from outside home network and are ready to assign it a DDNS name.

      • 82 Hans
        July 23, 2012 at 8:50 am

        Thanks for the suggestion, and sorry to bother you further, but my basic problem remains : the IP camera is not detected.
        Going into the Windows control panel networks/change adapter settings (Win 7, slightly different from what you describe), there are only 2 connections detected, both to my laptop (one LAN, one Wifi).
        On the other hand, when checking the router via internet, aside from these 2 connections and one to the TV decoder (all with MAC and IP address), there are two more items apparently detected, both with MAC, but no IP-address : one “equipment 1” (my telephone ?), the other “new host 1”, with the highest MAC address (starting with 26), thus potentially indicating a recent installation trial (IP camera) to which, however, on the router, no IP address can be added.
        So – this looks pretty desperate, and I start to wonder whether the IP camera bought (chinese) is a fake despite its 100$ price tag (fake IP camera’s are sold). The camera itself does blink in the back (green still, yellow blinking), with red lights on in front after an hour or so (infrared ?) which go off after some time…
        Thanks for further thoughts !

  43. July 22, 2012 at 12:25 am

    IP-Cameras are usually configured with a standard IP Address.
    This can be either 192.168.0.x or then 192.168.1.x

    If your local network is set under by Example 192.168.0.x , but the IP-Camra is set under 192.168.1.x, then, no tool is able to recognize the camera. Vice Versa, it’s the same problem.

    I would succest that you check your router IP. If it is:
    change to 192.168.1.x
    or vice versa

    If you so solve your problem, reconfigure the IP-Camera to mathc your network IP Range, reconfigure the router also to the standard setting and start again…

    Good Luck


    • 84 Hans
      July 22, 2012 at 12:52 pm

      Hi Ernie – Thanks for your suggestion. My routers IP address is indeed 192.168.1. Also it does indicate MAC addresses of several unconnected “new hosts”, but, unlike with connected items (such as my laptop and a TV decoder) no IP address for these.
      Can I just make one up myself for these “new hosts”, corresponding to the routers address, such as 192,168.1x ?
      Or how else to proceed ?
      Other question : does the DynDNS service need to be activated (I noticed it was not), and/or should I install a static IP address, if ever I do get a working IP address ?
      Thanks again for your help !

  44. July 23, 2012 at 8:50 pm

    1. Before beeing able to help, it would be important to know more details about the camera in order to recognize the brand. What I can say at the moment is:

    RESET your IP Camera, there should be a small hole sonewhere near the back connectors or then at the bottom of the cam. Puch (with care) the knob about 15 seconds.

    Set your Router to , then reboot the entire system and try all the programs you will find here:


    If no result:

    Set your Router to , then reboot the entire system and try all the programs, regardless of B, F, Q, or V-Type as declared. But try the F-Type Search programs first. If you see the Cam IP, note it down immediately. Because if you try to search a second time, you may not see any IP address anymore, for some reason, with some of the programs. To see it again, you would have to reboot the PC.

    You will receive a WARNING, if you start the progs, Please accept UNSIGNED Active-X Installation, or your Progs will not work.

    2. Do do NOT need to activate the internal configured DNS Service, because it would possibly not work anyway, in most cameras. To assure a steady connection, you would have to, either, use a static IP-Address, wich is costly, of the have a local network-PC running, using a program from myq-see.com or dyndns.org, wich connects to the DNS Server on a regular bases, so keeping the IP alive….


    • 86 Hans
      July 25, 2012 at 12:13 pm

      Hi Ernie,
      Thank you so much for your help – even if I’m still stuck.
      Regarding the camera : it seems to be a chinese no-brand (for 100$ nevertheless, bought in Australia), and all I can give you is what’s written on its bottom :

      USER:admin PASSWORD:admin

      The camera looks pretty much like they all look (e.g. MayGion) : black, with a wifi antenna, marked “IR – Night – Vision” around the central lens, and 12 tiny LED’s in a circle around it, which seem to be lit at night without a connection to my laptop established.

      The given internet address (apparently for DDNS ?) can’t be reached – a port conflict ? (81, mine seems to be 80). If so, how to resolve it ?

      I did reset the cam, as suggested (which seems to work, at least I heard a tiny noise during pushing the reset knob) and tried all your programs with the router set to, which is my normal setting : the cam or its IP-address wasn’t detected with any of the programs, not more than with the software provided with the cam.

      I didn’t change my router setting (to as suggested) fearing to lose other connections (laptop, TV).
      If it is important to try, please tell how and where to make the IP address change for the router with no risk involved..

      From the cam’s manual (a photo of a connected screen), I gather that a usable cam IP address would be (for instance I guess). Is there a way to installing such a connection (fixed ?) without having the cam’ IP address properly detected ?

      The manual indicates that there is a reverse connect option allowing to set the camera as client and the monitor software as server how to specify how to go about it.

      I truly feel old and stupid – should I give up and buy another (presumably also chinese) camera here in Europe ?

      Thanks for your time, if you have a better idea !


  45. 87 Jeff
    August 16, 2012 at 1:31 pm

    I have successfully setup the camera via cable, and also via wireless and can access via my LAN on both fronts.

    When trying to access externally via web or apps is where I am having an issue. I went and created a hostname on no-ip.com and that was fine.
    In fact when I try and access my hostname via an external web page, it takes me to the login page for my router.
    I have setup the camera with port 8090.
    When I try and access the camera on the LAN via myip:port ie, it is fine, no issues.

    But when I try and access the camera using the hostname:8090, it does not work.

    I then thought maybe my port forwarding was wrong, but I am able to access the 8090 port using the link http://www.yougetsignal.com/tools/open-ports/

    Any assistance would be much appreciated

  46. September 13, 2012 at 3:18 am

    Just to inform you all, I found new FREE versions of the IP Camera Super-Client.

    This is the ‘light’ version:

    This is the ‘classic’ version:

    This is for ‘UID’ only Installations:


    I have not found anything related to ‘registering’ the Client Software, so, I guess, you like this!.

    Good Luck


  47. 90 Kuang Hau Tan
    November 29, 2012 at 10:48 am

    Sometimes the port mapping fails. A reboot of the ipcam fixes it.but why doesit happen and how do I fix it?

  48. 91 user1
    January 14, 2013 at 2:38 pm

    great article, first time i ever able to set my cam with this help

  49. May 2, 2013 at 7:17 pm

    I have an Astak Mole Cam that, for the most part, works okay, but at certain times of the late morning and early afternoon, cannot be viewed in Internet Explorer because the video screen area is black. The only workaround I have been able to come up with is run the camera in night vision mode.
    Oddly, my WiFi connected Android phone with it’s browser can view the Mole Cam video in color, without night vision mode. Internet Explorer, exclusively, seems to be unable to view the video at certain times of day. Cannot find any info on the web as to why this is. The quality of the video signal should not be blanking the digital transmission to IE, but not to the generic browser on an Android phone. The real mystery here is why video is viewable in the daytime only in Night VIsion mode! In normal mode, there is no video until late afternoon when the angle of the sun is low. At about 3:15pm, the IE browser starts getting a frame now and then, and after half an hour, it’s up to the full frame rate that the camera is set to. The situation seems to be dependent on the angle of sunlight. Camera blanks LAN video when sun is behind camera (east), but starts to transmit images over the LAN when sun is in the west and close to setting. This is a real head scratcher!

    • May 2, 2013 at 11:39 pm

      This blog has moved to NetworkCameraCritic.com. But it sounds like a an ActiveX issue. When viewing remotely like from your phone, you are using the RTSP protocol and it may work well with that. You can try and stream the camera to a free program called VLC and see if that works but from IE, it’s using ActiveX to display and there may have been a Windows update that messed you up. Drove me crazy with Dahua cameras not working with IE 10 when that was updated recently, I get that problem fixed and then ACTi cameras didn’t work. Then Hikvisioncameras only display in “compatibility mode”, all because of ActiveX incompatibilities. Also check antivirus programs, they can block some unsigned ActiveX controls from working.

  50. 94 buythisdashcam
    June 28, 2014 at 5:32 pm


    Can you tell me what is the bets IP camera to be able to check online what happens in a small office ?

    Thank you for yoru help.

  51. July 16, 2014 at 11:49 am

    i have neo cam NIP 03 clone (i think so, mine has h.264 decoder also).

    my network is like this camera :-

    3G USB > TL MR-3020 wifi router > IP cam (wifi)

    and for PC :-

    3G USB > TL MR-3020 wifi router > PC (LAN cable)

    without 3G connection (i.e. internet) , i can access my cam on PC (i.e. on LAN)

    but when i connect USB router (TP LINK _ MR3020) to my router and
    connect router to internet , camera instantly drops connectivity with
    wifi router. so it can not be accessed via local PC or via remotely.

    don’t know the problem, but due to this problem, i can not access it remotely 😦

    i have done port forwarding Ok AFAIK (its 8888)

    • July 16, 2014 at 11:52 am

      sorry, previous was a bit confusing,
      please delete that and have this 😦

      i have neo cam NIP 03 clone (i think so, mine has h.264 decoder also).

      my network is like this camera :-

      3G USB > TL MR-3020 wifi router > IP cam (wifi)

      and for PC :-

      3G USB > TL MR-3020 wifi router > PC (LAN cable)

      without 3G connection (i.e. internet) , i can access my cam on PC (i.e. on LAN)

      but when i connect USB modem to my router (TP LINK _ MR3020) and
      connect router to internet , camera instantly drops connectivity with
      wifi router. so it can not be accessed via local PC or via remotely.

      don’t know the problem, but due to this problem, i can not access it remotely 😦

      i have done port forwarding Ok AFAIK (its 8888)

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 237 other subscribers

%d bloggers like this: