you need to set a custom port forward
say port 8080 on the brightbox to port 80 of the IP cam.
so you would browse to http://mydyndnswhatsit:8080
I've bought an IP camera so I can watch eggs I am incubating hatch whilst I am at work next week.
I'm struggling to access the camera from the internet. I have set one of these up before at a business and it worked beautifully. This one is being a little more awkward.
Camera: Tenvis JPT3815W
Connection: Ethernet - EE Brightbox - BT Fibre Modem - Internet
So I've set up port forwarding, DMZ and I even signed up to DynDNS, everything on the camera is saying good to go "Status DDNS Update Successful;" UPnP Enable
Status Windows Find Successful ; Port Map Successful
but when I go to my public IP I get my EE Brightbox login.
Am I doing something horribly wrong? Could the BT modem be blocking ports?
Got a few days to sort it out (about 5 or 6 until hatch day!)
Any help much appreciated!!
help.ee.co.uk/system/selfservice.controller?CONFIGURATION=1016&PARTITIO N_ID=1&secureFlag=false&TIMEZONE_OFFSET=&CMD=VIEW_ ARTICLE&USERTYPE=1&ARTICLE_ID=540688
In the last picture.
lanip address = camera
lan port = 80
public port = 8080
I doubt EE would be blocking,
what are the gateway and netmask for the camera?
Camera is on port 80.
Brightbox has port forwarding for camera ip LAN 80, Public 8080
If I browse to [external ip]:80 - I get the router
If I browse to [external ip]:8080 - I get Oops! Google Chrome could not connect to [external ip]:8080
Gateway is the router IP - 192.168.1.1, mask is 24 bit - 255.255.255.0 DNS is router IP - 192.168.1.1
ps/ got the camera IP in the DMZ on the router.... this won't be affecting anything will it?
how are you testing from external , from a real external device or from the LAN?
I would move the camera to the standard lan if there is one and not the DMZ for testing.
I'm just trying it from my laptop which is on the WLAN. Camera is plugged in to LAN. I'll take it out of DMZ now and test the external ip/port on my phone...
wowza! Maybe it was going to the router because I was connected to the LAN. It worked fine on the phone!
Many thanks your way :-)
NAT is very often broken if you try to access it from the lan side rather than truly on the WAN.
There are currently 1 users browsing this thread. (0 members and 1 guests)