Jump to content

Welcome to We Got Served Forums
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. If you already have an account, login here - otherwise create an account for free today!
Photo

View Existing Surveillance System?

- - - - -

  • Please log in to reply
9 replies to this topic

#1
Jpeckinp

Jpeckinp

    Member

  • Members
  • PipPip
  • 25 posts
I recently picked up a Acer h340, since I set up the homeserver.com address I haven't been able to access my Q-See surveillance system.
When I type in my dlinkddns address for my cameras it brings up my homeserver web page.

Does anybody know of a way I can still view my cameras?

My cameras and the server both have static addresses on the network. The cameras use port 80 and 9000 on my router.

Any help would be appreciated.

Jerry


Upgrade to a WGS Supporter Account to remove this ad.

#2
cainmp

cainmp

    Advanced Member

  • Members
  • PipPipPip
  • 442 posts
  • Gender:Male
  • Location:Cincinnati, OH
You will have to change the ports on either the WHS or the camera's, as both are trying to use the default port of 80. Change one of them, then access them by typing ...homeserver.com:<new port #> and you will be all set.

#3
Jpeckinp

Jpeckinp

    Member

  • Members
  • PipPip
  • 25 posts

You will have to change the ports on either the WHS or the camera's, as both are trying to use the default port of 80. Change one of them, then access them by typing ...homeserver.com:<new port #> and you will be all set.

I'll give that a try when I get home tonight.

Thanks

#4
Jpeckinp

Jpeckinp

    Member

  • Members
  • PipPip
  • 25 posts

I'll give that a try when I get home tonight.

Thanks


Something didn't work right.

Let me see if I understand. Should I change the port number on the camera system or in the router for the camera system?

I tried both and when I went to xxxxx.homeserver.com it came up with my camera but I couldn't access my server then. If I put a port # at the end of the address it wouldn't connect.

#5
cainmp

cainmp

    Advanced Member

  • Members
  • PipPipPip
  • 442 posts
  • Gender:Male
  • Location:Cincinnati, OH
hum...let my try to explain it differently....

for example, browse to my xxxxx.homeserver.com address and I get my default WHS web page, I changed the port on my uTorrent UI (similar to changing the port on the cameras) to 8080, and when I browse to xxxxx.homeserver.com:8080 I get the uTorrent page. Addtionaly I have vmware web access listening on port 8222, so i browse to that via xxxxx.homeserver.com:8222.

One thing to keep in mind, that if you camera's don't support, or your router doesn't support UPnP, then you will have to manually set up port forwarding to an internal IP address...like below:

WHS IP address = 192.168.1.10 Port = 80
Camera 1 IP address = 192.168.1.11 = 81
Cameria 2 IP address = 192.168.1.12 = 82

You need to tell your router to forward, either automatically VIA UPnP or manually to forward requests to port 80 to the internal IP address of 192.168.1.10, requests to port 81 to the internal IP address of 192.168.1.11, and requests to the port 82 to the internal IP address of 192.168.1.12.

Does that help at all?

I know it can be done, as I am currently doing it, its just a matter of getting everything configured correctly.

#6
Jpeckinp

Jpeckinp

    Member

  • Members
  • PipPip
  • 25 posts

hum...let my try to explain it differently....

for example, browse to my xxxxx.homeserver.com address and I get my default WHS web page, I changed the port on my uTorrent UI (similar to changing the port on the cameras) to 8080, and when I browse to xxxxx.homeserver.com:8080 I get the uTorrent page. Addtionaly I have vmware web access listening on port 8222, so i browse to that via xxxxx.homeserver.com:8222.

One thing to keep in mind, that if you camera's don't support, or your router doesn't support UPnP, then you will have to manually set up port forwarding to an internal IP address...like below:

WHS IP address = 192.168.1.10 Port = 80
Camera 1 IP address = 192.168.1.11 = 81
Cameria 2 IP address = 192.168.1.12 = 82

You need to tell your router to forward, either automatically VIA UPnP or manually to forward requests to port 80 to the internal IP address of 192.168.1.10, requests to port 81 to the internal IP address of 192.168.1.11, and requests to the port 82 to the internal IP address of 192.168.1.12.

Does that help at all?

I know it can be done, as I am currently doing it, its just a matter of getting everything configured correctly.


OK my router does support UPnP but I know the cameras system doesn't.

Here is my setup

192.168.xxx.45 = cameras
192.168.xxx.48 = server

So I would need to setup the router to forward the port of the cameras(82) to the ip 192.168.xxx.45
and I could leave the port (80) going to the server.

Does this look correct?

#7
cainmp

cainmp

    Advanced Member

  • Members
  • PipPipPip
  • 442 posts
  • Gender:Male
  • Location:Cincinnati, OH
Yes that's correct.

#8
Etoa

Etoa

    Advanced Member

  • Members
  • PipPipPip
  • 866 posts
  • Gender:Male
  • Location:Honolulu, Hawaii
Contributor
I have exactly the same situation. In my router I foward port 80 to the WHS IP address and forward port 83 to the Q-See system IP. The Q-See DVR (at least the model I have) allows you to change the default web port, which I have changed to port 83.

#9
Jpeckinp

Jpeckinp

    Member

  • Members
  • PipPip
  • 25 posts

I have exactly the same situation. In my router I foward port 80 to the WHS IP address and forward port 83 to the Q-See system IP. The Q-See DVR (at least the model I have) allows you to change the default web port, which I have changed to port 83.

Mine will allow that also.
I have other problems now. I was using a D-Link DWL-820 to connect the camera system to the network. It looks like it has taken a dump.
I had it wired to my laptop last night and it was dropping connection every few seconds. I changed the cable and tried my Netbook and I had the same results.

I'm going to hook my old router in as an AP this weekend and see if that fixes that problem.

#10
Jpeckinp

Jpeckinp

    Member

  • Members
  • PipPip
  • 25 posts
Well the problem is fixed. My problem wasn't the port forwarding as much as it was the fact I was using two DNS services.
I can't use homeserver.com and will have to stick with the DNS from Dlink.

Thanks for all the help.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users


Upgrade to a WGS Supporter Account to remove this ad.