Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Ken]

I'm having a problem with the E-Mail settings in the DNR-202L. The email settings in the cameras work fine so I've used them as examples and set up the DNR-202L the same way. No joy. When clicking on the Test button it (finally) times out and comes back with a "Test Error" response. I've used different combinations and both port 25 (default) and port 465 (port 465 is used in the cameras quite successfully.

Anyone had similar issues and fixed it?

Any help would be appreciated.

Added info: The cameras have the SSL-TLS box checked in the email account setup. The cameras fail their email test if this box is not checked. The SSL-TLS option is not available in the DNR-202L. Only the StartTLS option (or none) is there. Don't know if this makes a difference. I did try checking the StartTLS option but, again, no success.

(I tried to post some screen shots but don't see how to attach them. Also, I've sent a message to D-Link support but no response as yet.)

Thx,
Ken

[Ken]

Hellloooo! Anyone there? At least an acknowledgement from support??

[FurryNutz]

Link>Welcome!

• Link>What Firmware version is currently loaded? Found on the DNSs web page under status.
• What region are you located?

What Mfr and model is the main host router?
Is the DNS getting a Dynamic IP address from the main host router? I recommend using a Static IP address ON the DNS set to 192.168.#.2 or .20.

Is uPnP or uPnP Port Fowarding enabled on the DNR if it has this feature?

[Ken]

Thanks for the reply FurryNutz. I really appreciate your help.

Here's the answers to your questions:
•   DNR (NVR) Firmware: 2.00.11 (Agent version: 2.1.18-b44)
•   Router: Netgear R6250 with dual band wi-fi using the 2.4ghz band
•   Location: Seattle, WA
•   IP Addressing: Running DHCP on all attached devices (my addresses are in the private 10.x.x.x range) as are all the other gear.
•   Port forwarding option: No port forwarding option found in the DNR. In the router then, yes, forwarding is selected.

I hope these answers cover the info you need. If not, then let me know and I'll get whatever other info you need.

When setting up the DNR I didn't see any options that needed setting in the router for passing email from the DNR to Outlook in the PC.

Thx,
Ken

[FurryNutz]

Not sure if this will be helpful or not:
http://forums.dlink.com/index.php?topic=58848.0

I've asked some other users to review this and see if they can help you.

Is this a google email account or something else?

[robert-e]

I come here in response to an email.  I have not used any other camera other than the dcs932l, nor have I used the email notification.  What I can suggest for you to check:

-on your router, look under networking.  Take note of the addressing range that your routers uses to supply dhcp addresses to devices connected to it.  For ex. it might be something like:  starting address = 192.168.0.100, with a range of about 50 or perhaps 100, making the ending address of 192.168.0.150 or perhaps 192.168.0.200.  Now log onto your camera, and under networking, assign a static IP address to your camera OUTSIDE of the addressing that your router assigns (above).  For ex. you might choose 192.168.0.50 or perhaps 192.168.0.225.  Note that 192.168.0.255 is the maximum value allowed.  What ever it the address you choose, that is the address that you must use in your router if you wish to use port forwarding (from the router to the camera).  Not saying that you want to do this; probably not, but just saying.  Remember to SAVE the settings before you log out.

As for the TLS problem...I do believe that dlink and others had some security issues in the last year, and perhaps that might have ramifications for you.  It was the main reason for a software upgrade last year.  You might look into that.  I imagine FurryNutz might offer you some enlightenment there.

Best regards,
Bob

[Ken]

First off, to FurryNutz:

Eureka! The only change I made is to use port 587 which was indicated in the post stream of the link you sent. Voila! everything works! Motion detection, loss of signal, etc. Since I have email set up in both the cameras and the DNR I get email from both. The DNR also recorded the events so I could go back and see what the motion was. However, when the DNR sent an email with the attachment it only showed a single frame of what the cameras view is not what caused the motion detection. I'll be shutting off email from the camera and only use the DNR. Another nice thing to have would be better management of the recording device so I could manage disk space better. Anyway, I'm a happy camper at this point. BTW, I'm using comcasts email.

Now to Robert-e: 

Thanks for your input Bob! Setting up static IP addressing for the camera network is a great idea. I thought I could just use DHCP as everything else but potential connectivity issues come up whenever a camera/recorder device reboots. I may lose one or more device so I'll be statically addressing each camera and the DNR outside the DHCP range (which only allows 14 DHCP devices).

Thanks again Bob,

Ken

[FurryNutz]

Glad you got it working. Enjoy. 

[Ken]

Thanks for your help FurryNutz. Have a great weekend.

Ken

[FurryNutz]

Ditto. 

[Ken]

Bob,

Again, thanks for your help in solving my DNR email problem. I went to set up static addresses outside the DHCP range but, since I can't set up multiple IP addressing network, I would have to use the same IP address mask of the DHCP range. This would have caused some grief I think. The DHCP range is only 13 addresses (it's a security thing). But, the router has the option of setting up reserved addresses so I reserved the addresses of the "camera network" devices.

So far everything seems to be working. The DCS932L does drop out on occasion as does the DCS930L. It may be a wireless bandwidth size/camera location/radio interference issue but I'll work with that later.

Thanks again,
Ken

[Kakashi::.]

Bob,
..... The DHCP range is only 13 addresses (it's a security thing). But, the router has the option of setting up reserved addresses so I reserved the addresses of the "camera network" devices.
.....

Thanks again,
Ken

Hi Ken,

We are glad that everything worked out for your setup. If you could answer just a few more question regarding your setup:

1. make and model of the router you are using?

2. Is this equipment you received configured from your Internet Service Provider (ISP)?

3. Does this router double as a modem also?

Thanks!

[Ken]

Hi Kakashi,

The router I have is a Netgear, model R6250. It's a 802.11ac Dual Band Gigabit Ethernet router. I purchased it to setup my "internal network" for gig and to use the dual band Wi-Fi for separate functions. The modem is, as well, one I purchased to replace the unit provided by the cable providers. The modem is an Arris  Touchstone TM722G DOCSIS 3.0 Telephony unit.  (I save five bucks a month as well.) I configured all my network devices including the private IP addressing scheme.

The router and modem are separate units as I don't want all "my apples in one basket" as they say. If the modem goes out the home network still works for internal use (like the Wi-Fi camera network). If the router goes out then I pull out the old backup as a temporary unit.

One other reason they're separate, the modem and router, is that I would like to get rid of cable. So when I change ISPs I won't have to reconfigure the internal network beyond the modem. The Arris modem should comply with other ISPs as well, hopefully. There doesn't seem to be an elegant way to "get rid of" cable yet so I'll just have to wait for a while.

Hope this answers your questions. Let me know.

Ken

[Kakashi::.]

Hi Kakashi,

The router I have is a Netgear, model R6250. It's a 802.11ac Dual Band Gigabit Ethernet router. I purchased it to setup my "internal network" for gig and to use the dual band Wi-Fi for separate functions.... 

Hope this answers your questions. Let me know.

Ken

Hi Ken,

Thanks for the information... my curiosity was due to your statement in one of the prior post with regards to your DHCP scope "(which only allows 14 DHCP devices)". I was not sure if you had some sort of business account with your ISP that only allowed to use 14 nodes behind your router. We've seen some deployments like this where the customer is only allow 5 or 10 addresses behind the ISP provided router (with one big difference, all Public IPs), but I see that you are just using that as a security measure.

Good day! 

[Ken]

Kakashi,

I set the address mask to only allow for the 14 addresses to be available rather than the full 255.

Ken