Problem setting up a Wireless IP Camera - remote access

howardb

Expert Member
Joined
Sep 12, 2003
Messages
3,647
Just need a bit of advice here - I may have overlooked something with the setup.

I have a 4-port D-Link ADSL modem with built-in wireless, and have a wireless/wired IP camera that I want to use over wireless (monitoring the back of the house from work via internet). I've setup everything according to the camera software and managed to get the wireless connection working on the LAN side from my local PC (I have MAC filtering for the camera/modem authentication, and have disabled the WEP/WAP security for now). I can access the camera interface via this PC and can control the tilt/pan/zoom on the LAN, from any PC that's wired to the network.

I have a dynamic IP ADSL account, so I've also set up a DynDNS account and forwarded the port I'll be using on the modem, as well as set the camera to the same port number with the DynDNS details entered into the camera. I've allocated a static IP to the camera, and disabled the DHCP IP settings on the modem (I use static IP's on all my wired PC's to the modem.

The problem I have is not being able to access the camera controls via internet from a remote location - I just get a timeout or page cannot be displayed. According to the camera manual, I should get the camera control page in a web window, where I can log on and control the camera. I've rechecked all the port numbers, forwarding, IP, etc. but cannot get a remote connection.
I've tried accessing remotely via the DynDNS host name I set up (e.g. hxxp://test.dyndns.org:85) and directly via the external IP (e.g. 123.123.123.123:85) - am I missing something?

E.g. of IP and ports used:
ADSL Modem IP: 192.168.1.1 (also the gateway)
4 wired PC's with IP range 192.168.1.2 to 192.168.1.5
Allocated IP 192.168.1.6 to the camera on forwarded port 85 (also setup on camera as per manual)
MAC address for camera entered on the modem
Setup DynDNS details on both the modem and the camera - checked and working via the Dyn Updater

Any ideas?
 

davemc

Executive Member
Joined
Apr 8, 2009
Messages
6,518
Well, when you're controlling the camera, there is some software running.

That software is the key to accessing the camera, as it provides the means to communicate with the camera, so you need to know how it works.
No, you don't typically need to install a web server as well, whatever software is already running should to the trick, but you need to know what it is.

Try this: In front of your PC, with the software all working and running, open up a command prompt and type in the command:
netstat -a -b
This will list all the network-based software running on your computer and the port numbers that they're listening on. Look for something that's related to your ip camera, and note the port number.

You then have to forward your router through to that port, AND, you must make a hole in your windows/whatever firewall to allow traffic through to and from that port.

EDIT: You said win7 ... I don't even know how to do the netstat command in Win 7 ... google is yer friend I suppose.
 

zamicro

Expert Member
Joined
Oct 22, 2007
Messages
3,823
Well, when you're controlling the camera, there is some software running.

That software is the key to accessing the camera, as it provides the means to communicate with the camera, so you need to know how it works.
No, you don't typically need to install a web server as well, whatever software is already running should to the trick, but you need to know what it is.

Try this: In front of your PC, with the software all working and running, open up a command prompt and type in the command:
netstat -a -b
This will list all the network-based software running on your computer and the port numbers that they're listening on. Look for something that's related to your ip camera, and note the port number.

You then have to forward your router through to that port, AND, you must make a hole in your windows/whatever firewall to allow traffic through to and from that port.

EDIT: You said win7 ... I don't even know how to do the netstat command in Win 7 ... google is yer friend I suppose.

I think in his case the camera will have its own operating system. (Mine does)

What I can suggest is to first try and access it from another ADSL line. It might be that your office firewall is blocking the traffic to the camera. I also found that I had to enable DHCP on the camera, but then to set the router to reserve the IP for the camera, thereby making it almost static.
 

Kroks

Well-Known Member
Joined
May 27, 2009
Messages
158
You stated that you had MAC address filtering on. Try and disable it. That might be causing the problem.... Start with a simple configuration, then add features once it is working.
 

xplicet

Well-Known Member
Joined
Oct 17, 2005
Messages
221
when you access the cam on you LAN do you you type in the port number as well to get access (i.e 192.168.1.16:85) or is 85 a secondy port that you have set up for external access?

Are you sure the cam has your gateway details in under static ip. The gateway being 192.168.1.1

Have you made sure your dyndns account is synced correctly and updated with current ip?

Can you access your router by typing your dyndns address with out port number? Should default to port 80 which should be the router.
 

Jola

Honorary Master
Joined
Sep 22, 2005
Messages
20,124
I have exactly the same issues as the OP, also couldn't get it to work with remote access (local is fine).

However, my router setup is a bit more complicated, I have two chained Netgear routers - I guess that I could simplify that !

I have three IP cameras.

So will also try some of these suggestions and contribute to this thread.
 

howardb

Expert Member
Joined
Sep 12, 2003
Messages
3,647
Thanks chaps - will try these and see if they help. Will let you know. :)
 

howardb

Expert Member
Joined
Sep 12, 2003
Messages
3,647
Resolved!

I tried all the above suggestions and basically started from scratch. It turned out to be the firewall blocking the port I selected - there was an update on Monday to the firewall software (Comodo) and it didn't import all my previous settings and setup, so the default setting was blocking all the ports - once opened and re-setup my trusted networks, I was able to access remotely via the web without issues.

Many thanks for all your help everyone.
 

The_Unbeliever

Honorary Master
Joined
Apr 19, 2005
Messages
103,196
Resolved!

I tried all the above suggestions and basically started from scratch. It turned out to be the firewall blocking the port I selected - there was an update on Monday to the firewall software (Comodo) and it didn't import all my previous settings and setup, so the default setting was blocking all the ports - once opened and re-setup my trusted networks, I was able to access remotely via the web without issues.

Many thanks for all your help everyone.

The most obvious... :D

Good to hear you've got it working :D
 
Top