D-Link Forums
Software => D-ViewCam => Topic started by: valandor on June 29, 2016, 10:16:57 AM
-
I've encountered a very weird situation with my DViewCam on Windows 10. This has been working perfectly for about six months on this new OS and for years on Windows 7 prior to this Windows update.
Last week DViewCam stopped sending out email notifications. After investigating, it was no longer able to connect to the gmail smtp server. I tried a wide variety of things like changing to different smtp servers, to no avail. When trying to send a test email, it just immediately pops up an error box saying "Check the setting." This was on version 3.6.4 of DViewCam.
After talking to Dlink support, I upgraded to 4.0.5 of DViewCam and had the same results. Dlink support spent several hours troubleshooting on my machine and weren't able to solve the issue. The cameras themselves can send email notifications through gmail without a problem.
I can send email out on that machine just fine with other programs (like powershell directly through to gmail smtp).
I'm wondering if anybody else has encountered this and if you were able to solve it?
Note: I moved dviewcam to another non-windows 10 machine and I'm back up and running sending email notifications just fine through gmail.
-
Was there a recent Windows 10 Update by chance?
Your testing of DVC on a non Windows 10 PC that is working seems to point to something on the 10 PC that's no longer working. Something in 10 maybe blocking DVC and or network communications.
-
There were windows updates on 6/18, but the machine doesn't auto-reboot on updates. The problem started around the 25th, so those updates could be a contributing factor.
That being said, I installed DVC on a fresh Windows 10 machine and the problem is happening there as well, so there is certainly some very good circumstantial evidence pointing to recent Windows 10 updates as causing this issue.
-
Any chance you can install DVC on a Windows 10 PC that's just been installed, however has not been allowed to install any updates?
-
No, I don't have any new Windows 10 installation media available.
-
Windows 10 installation can be downloaded and burned to DVD if that's an option.
Windows 10 makes it harder to deal with updates. ::)
-
I am experiencing the same issues - DVC running for years on older OSs, and months on windows 10 and now in June it stops sending email to gmail smtp server. I have captured packets and see that the gmail server is closing the connection after the TLSv1 client hello is sent for the encryption negotiation. The reason for the close from the server is "Level: Fatal, Description: Protocol Version. Not sure if it is actually a change on the gmail side that has locked down the connection options but that wouldn't explain why it works on other versions of windows. I've tried the "allow less secure apps to access your account" option on the google side but that didn't make any difference. I was playing around with trying the unsecured gmail account which requires SMTP on port 25 but saw (wireshark) that I was never getting a response on port 25 and thought Verizon (my ISP) was blocking that but also decided to turn off windows firewall to see what that would do. I don't remember the exact order of things (turning off the firewall and trying different mail settings in DVC) but it started working. I turned the firewall back on - set DVC back to using authentication, SSL, port 465 and it worked for about 3-4 days but then stopped again and I haven't been able to get it to work since. Can't believe it's only us two running into this problem...
-
What version of DVC are you using in windows 10.
This user seemed to notice that there was a possible windows update that may have caused problems.
-
Sorry - should have put that in my post - 4.0.4. Also running all cameras on a private network with DVC having access to the internet through another NIC. Not sure if that would play into things...
-
Might try to narrows things down to using one NIC and see if problem still happens. I don't know if that will make any difference. Seems this maybe a email issue possibly or with gmail or something with Windows 10. :-\
-
I ran a couple tests - downloaded a disc images for windows 10 install and spun it up in a VM in virtualbox. No updates - just once up and running I installed DVC 4.0.4 and it failed to send email to gmail. I then deleted that VM and installed a Win 7 pro in it's place and immediately installed DVC 4.0.4 and it also failed in the same manner which implies to me that the more secure google email settings are not compatible with DVC. So now my question is - is anyone running DVC with gmail smtp servers and if so what are the settings required? My ISP blocks SMTP to port 25 (there is a google email service that allows no authentication etc.) so I can't use that.
valandor - are you still working with an older version of windows with gmail?
-
I have asked D-Link to review this. Will be checking on this there.
Any chance you can get a wireshark capture of this? Something we can send to D-Link.
-
Don't know how to add an attachment - maybe not enabled but wireshark lets you export captures as text. The things to look at are frame 4 is the Client Hello (full decode goes through all supported encryption options from the connection attempt of DVC to the server), frame 5 is the ACK from the server and immediately frame 6 is the gmail server sending a TLS fatal message that the protocol isn't acceptable. The rest is just the closing of the TCP connection. This is with the authentication (which never gets that far), SSL checked and going to port 465 for the gmail connection. These settings used to work but gmail locked down some things recently excluding more "insecure" protocols. Trying other options (different ports, no selection of SSL etc.) results in different errors but are more of the type that a protocol is expected but not being used. This is the most meaningful capture where the protocols are correct, gmail just isn't going to accept any of the offered security options. I'd be glad to send the pcap file if you can tell me how.
No. Time Source Destination Protocol Length Info
1 0.000000 10.0.0.3 gmail-smtp-msa.l.google.com TCP 66 60459 → 465 [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=256 SACK_PERM=1
Frame 1: 66 bytes on wire (528 bits), 66 bytes captured (528 bits) on interface 0
Ethernet II, Src: AsustekC_09:98:e3 (00:24:8c:09:98:e3), Dst: Netgear_b6:f7:2e (50:6a:03:b6:f7:2e)
Internet Protocol Version 4, Src: 10.0.0.3 (10.0.0.3), Dst: gmail-smtp-msa.l.google.com (74.125.21.108)
Transmission Control Protocol, Src Port: 60459 (60459), Dst Port: 465 (465), Seq: 0, Len: 0
Source Port: 60459
Destination Port: 465
[Stream index: 0]
[TCP Segment Len: 0]
Sequence number: 0 (relative sequence number)
Acknowledgment number: 0
Header Length: 32 bytes
Flags: 0x002 (SYN)
Window size value: 8192
[Calculated window size: 8192]
Checksum: 0x6a12 [validation disabled]
Urgent pointer: 0
Options: (12 bytes), Maximum segment size, No-Operation (NOP), Window scale, No-Operation (NOP), No-Operation (NOP), SACK permitted
No. Time Source Destination Protocol Length Info
2 0.021330 gmail-smtp-msa.l.google.com 10.0.0.3 TCP 66 465 → 60459 [SYN, ACK] Seq=0 Ack=1 Win=43152 Len=0 MSS=1392 SACK_PERM=1 WS=128
Frame 2: 66 bytes on wire (528 bits), 66 bytes captured (528 bits) on interface 0
Ethernet II, Src: Netgear_b6:f7:2e (50:6a:03:b6:f7:2e), Dst: AsustekC_09:98:e3 (00:24:8c:09:98:e3)
Internet Protocol Version 4, Src: gmail-smtp-msa.l.google.com (74.125.21.108), Dst: 10.0.0.3 (10.0.0.3)
Transmission Control Protocol, Src Port: 465 (465), Dst Port: 60459 (60459), Seq: 0, Ack: 1, Len: 0
Source Port: 465
Destination Port: 60459
[Stream index: 0]
[TCP Segment Len: 0]
Sequence number: 0 (relative sequence number)
Acknowledgment number: 1 (relative ack number)
Header Length: 32 bytes
Flags: 0x012 (SYN, ACK)
Window size value: 43152
[Calculated window size: 43152]
Checksum: 0x19e4 [validation disabled]
Urgent pointer: 0
Options: (12 bytes), Maximum segment size, No-Operation (NOP), No-Operation (NOP), SACK permitted, No-Operation (NOP), Window scale
[SEQ/ACK analysis]
No. Time Source Destination Protocol Length Info
3 0.021410 10.0.0.3 gmail-smtp-msa.l.google.com TCP 54 60459 → 465 [ACK] Seq=1 Ack=1 Win=66816 Len=0
Frame 3: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0
Ethernet II, Src: AsustekC_09:98:e3 (00:24:8c:09:98:e3), Dst: Netgear_b6:f7:2e (50:6a:03:b6:f7:2e)
Internet Protocol Version 4, Src: 10.0.0.3 (10.0.0.3), Dst: gmail-smtp-msa.l.google.com (74.125.21.108)
Transmission Control Protocol, Src Port: 60459 (60459), Dst Port: 465 (465), Seq: 1, Ack: 1, Len: 0
Source Port: 60459
Destination Port: 465
[Stream index: 0]
[TCP Segment Len: 0]
Sequence number: 1 (relative sequence number)
Acknowledgment number: 1 (relative ack number)
Header Length: 20 bytes
Flags: 0x010 (ACK)
Window size value: 261
[Calculated window size: 66816]
[Window size scaling factor: 256]
Checksum: 0x6a06 [validation disabled]
Urgent pointer: 0
[SEQ/ACK analysis]
No. Time Source Destination Protocol Length Info
4 0.021456 10.0.0.3 gmail-smtp-msa.l.google.com TLSv1 194 Client Hello
Frame 4: 194 bytes on wire (1552 bits), 194 bytes captured (1552 bits) on interface 0
Ethernet II, Src: AsustekC_09:98:e3 (00:24:8c:09:98:e3), Dst: Netgear_b6:f7:2e (50:6a:03:b6:f7:2e)
Internet Protocol Version 4, Src: 10.0.0.3 (10.0.0.3), Dst: gmail-smtp-msa.l.google.com (74.125.21.108)
Transmission Control Protocol, Src Port: 60459 (60459), Dst Port: 465 (465), Seq: 1, Ack: 1, Len: 140
Source Port: 60459
Destination Port: 465
[Stream index: 0]
[TCP Segment Len: 140]
Sequence number: 1 (relative sequence number)
[Next sequence number: 141 (relative sequence number)]
Acknowledgment number: 1 (relative ack number)
Header Length: 20 bytes
Flags: 0x018 (PSH, ACK)
Window size value: 261
[Calculated window size: 66816]
[Window size scaling factor: 256]
Checksum: 0x6a92 [validation disabled]
Urgent pointer: 0
[SEQ/ACK analysis]
Secure Sockets Layer
TLSv1 Record Layer: Handshake Protocol: Client Hello
Content Type: Handshake (22)
Version: SSL 3.0 (0x0300)
Length: 135
Handshake Protocol: Client Hello
No. Time Source Destination Protocol Length Info
5 0.041829 gmail-smtp-msa.l.google.com 10.0.0.3 TCP 60 465 → 60459 [ACK] Seq=1 Ack=141 Win=44288 Len=0
Frame 5: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface 0
Ethernet II, Src: Netgear_b6:f7:2e (50:6a:03:b6:f7:2e), Dst: AsustekC_09:98:e3 (00:24:8c:09:98:e3)
Internet Protocol Version 4, Src: gmail-smtp-msa.l.google.com (74.125.21.108), Dst: 10.0.0.3 (10.0.0.3)
Transmission Control Protocol, Src Port: 465 (465), Dst Port: 60459 (60459), Seq: 1, Ack: 141, Len: 0
Source Port: 465
Destination Port: 60459
[Stream index: 0]
[TCP Segment Len: 0]
Sequence number: 1 (relative sequence number)
Acknowledgment number: 141 (relative ack number)
Header Length: 20 bytes
Flags: 0x010 (ACK)
Window size value: 346
[Calculated window size: 44288]
[Window size scaling factor: 128]
Checksum: 0x011d [validation disabled]
Urgent pointer: 0
[SEQ/ACK analysis]
No. Time Source Destination Protocol Length Info
6 0.041832 gmail-smtp-msa.l.google.com 10.0.0.3 TLSv1 61 Alert (Level: Fatal, Description: Protocol Version)
Frame 6: 61 bytes on wire (488 bits), 61 bytes captured (488 bits) on interface 0
Ethernet II, Src: Netgear_b6:f7:2e (50:6a:03:b6:f7:2e), Dst: AsustekC_09:98:e3 (00:24:8c:09:98:e3)
Internet Protocol Version 4, Src: gmail-smtp-msa.l.google.com (74.125.21.108), Dst: 10.0.0.3 (10.0.0.3)
Transmission Control Protocol, Src Port: 465 (465), Dst Port: 60459 (60459), Seq: 1, Ack: 141, Len: 7
Source Port: 465
Destination Port: 60459
[Stream index: 0]
[TCP Segment Len: 7]
Sequence number: 1 (relative sequence number)
[Next sequence number: 8 (relative sequence number)]
Acknowledgment number: 141 (relative ack number)
Header Length: 20 bytes
Flags: 0x018 (PSH, ACK)
Window size value: 346
[Calculated window size: 44288]
[Window size scaling factor: 128]
Checksum: 0xa308 [validation disabled]
Urgent pointer: 0
[SEQ/ACK analysis]
Secure Sockets Layer
TLSv1 Record Layer: Alert (Level: Fatal, Description: Protocol Version)
Content Type: Alert (21)
Version: TLS 1.0 (0x0301)
Length: 2
Alert Message
Level: Fatal (2)
Description: Protocol Version (70)
No. Time Source Destination Protocol Length Info
7 0.041832 gmail-smtp-msa.l.google.com 10.0.0.3 TCP 60 465 → 60459 [FIN, ACK] Seq=8 Ack=141 Win=44288 Len=0
Frame 7: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface 0
Ethernet II, Src: Netgear_b6:f7:2e (50:6a:03:b6:f7:2e), Dst: AsustekC_09:98:e3 (00:24:8c:09:98:e3)
Internet Protocol Version 4, Src: gmail-smtp-msa.l.google.com (74.125.21.108), Dst: 10.0.0.3 (10.0.0.3)
Transmission Control Protocol, Src Port: 465 (465), Dst Port: 60459 (60459), Seq: 8, Ack: 141, Len: 0
Source Port: 465
Destination Port: 60459
[Stream index: 0]
[TCP Segment Len: 0]
Sequence number: 8 (relative sequence number)
Acknowledgment number: 141 (relative ack number)
Header Length: 20 bytes
Flags: 0x011 (FIN, ACK)
Window size value: 346
[Calculated window size: 44288]
[Window size scaling factor: 128]
Checksum: 0x0115 [validation disabled]
Urgent pointer: 0
No. Time Source Destination Protocol Length Info
8 0.041981 10.0.0.3 gmail-smtp-msa.l.google.com TCP 54 60459 → 465 [ACK] Seq=141 Ack=9 Win=66560 Len=0
Frame 8: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0
Ethernet II, Src: AsustekC_09:98:e3 (00:24:8c:09:98:e3), Dst: Netgear_b6:f7:2e (50:6a:03:b6:f7:2e)
Internet Protocol Version 4, Src: 10.0.0.3 (10.0.0.3), Dst: gmail-smtp-msa.l.google.com (74.125.21.108)
Transmission Control Protocol, Src Port: 60459 (60459), Dst Port: 465 (465), Seq: 141, Ack: 9, Len: 0
Source Port: 60459
Destination Port: 465
[Stream index: 0]
[TCP Segment Len: 0]
Sequence number: 141 (relative sequence number)
Acknowledgment number: 9 (relative ack number)
Header Length: 20 bytes
Flags: 0x010 (ACK)
Window size value: 260
[Calculated window size: 66560]
[Window size scaling factor: 256]
Checksum: 0x6a06 [validation disabled]
Urgent pointer: 0
[SEQ/ACK analysis]
No. Time Source Destination Protocol Length Info
9 0.042033 10.0.0.3 gmail-smtp-msa.l.google.com TLSv1 61 Alert (Level: Fatal, Description: Handshake Failure)
Frame 9: 61 bytes on wire (488 bits), 61 bytes captured (488 bits) on interface 0
Ethernet II, Src: AsustekC_09:98:e3 (00:24:8c:09:98:e3), Dst: Netgear_b6:f7:2e (50:6a:03:b6:f7:2e)
Internet Protocol Version 4, Src: 10.0.0.3 (10.0.0.3), Dst: gmail-smtp-msa.l.google.com (74.125.21.108)
Transmission Control Protocol, Src Port: 60459 (60459), Dst Port: 465 (465), Seq: 141, Ack: 9, Len: 7
Source Port: 60459
Destination Port: 465
[Stream index: 0]
[TCP Segment Len: 7]
Sequence number: 141 (relative sequence number)
[Next sequence number: 148 (relative sequence number)]
Acknowledgment number: 9 (relative ack number)
Header Length: 20 bytes
Flags: 0x018 (PSH, ACK)
Window size value: 260
[Calculated window size: 66560]
[Window size scaling factor: 256]
Checksum: 0x6a0d [validation disabled]
Urgent pointer: 0
[SEQ/ACK analysis]
Secure Sockets Layer
TLSv1 Record Layer: Alert (Level: Fatal, Description: Handshake Failure)
Content Type: Alert (21)
Version: TLS 1.0 (0x0301)
Length: 2
Alert Message
Level: Fatal (2)
Description: Handshake Failure (40)
No. Time Source Destination Protocol Length Info
10 0.042158 10.0.0.3 gmail-smtp-msa.l.google.com TCP 54 60459 → 465 [RST, ACK] Seq=148 Ack=9 Win=0 Len=0
Frame 10: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface 0
Ethernet II, Src: AsustekC_09:98:e3 (00:24:8c:09:98:e3), Dst: Netgear_b6:f7:2e (50:6a:03:b6:f7:2e)
Internet Protocol Version 4, Src: 10.0.0.3 (10.0.0.3), Dst: gmail-smtp-msa.l.google.com (74.125.21.108)
Transmission Control Protocol, Src Port: 60459 (60459), Dst Port: 465 (465), Seq: 148, Ack: 9, Len: 0
Source Port: 60459
Destination Port: 465
[Stream index: 0]
[TCP Segment Len: 0]
Sequence number: 148 (relative sequence number)
Acknowledgment number: 9 (relative ack number)
Header Length: 20 bytes
Flags: 0x014 (RST, ACK)
Window size value: 0
[Calculated window size: 0]
[Window size scaling factor: 256]
Checksum: 0x6a06 [validation disabled]
Urgent pointer: 0
-
Thank you for taking the time to collect this information. Ya, if you can get me the pcap file, I'll forward it on to D-Link and hope they can figure out whats going on.
Thank you.
-
Tried a couple of things - Ubuntu linux VM and played with a SMTP relay - could send email to gmail through that but haven't researched a way to send from D-viewcam yet. I did download the trial version of Sighthound Video and it sent emails to gmail fine - I have 5 cameras so after the trial runs out I'll be deinstalling it. It didn't work with my older 2100+ or 3420 cameras (or at least I couldn't figure out the correct video URLs to configure Sighthound correctly) but back to this thread - it seems that it is definitely D-viewcam that is doing something wrong since other applications can get to gmail find through their more secure settings, in Sighthound these settings worked:
smtp.gmail.com, username/password, port:587, use TLS...
-
Thank you for this information. I'll pass this along to D-Link for review. ;)
-
Anymore progress on this ?
I have just realized I am not able to receive E-mail notifications for Motion Detection . I was able to do this at one point , but not now . I am using Windows 10 with Gmail 2 step authentication , I have generated a new password for the Gmail 2 step authentication , but still no luck . Any ideas ? I am using the DCS-930LB camera , Firmware Version 2.13.15 , D-Viewcam version 4.0.5
-
I am having the same issue. After 6 months exactly that same week in June, my dviewcam stopped emailing. The cameras can still be set up to email, but I don't like it that way. Dviewcam is way better with less false positives/negatives, and doesn't send as many blank pictures--and the images seem to be better quality or something.. Please fix with a new update we can download. I have tried 10 different smtp server settings that I know work and nothing seems to work. I even reloaded win 10 and tried it before any updates, still we have the same problem. Maybe windows 7 will work for me...I will try with my work computer this evening. could it be a non windows update or something in win10? It doesn't work on my win 7 computer at work, but the ports or something may be blocked.
Thanks!
-
What version of DVC are you using?
If it had been working then stopped, possible something with your ISP mail service maybe blocking. If nothing changed on your home side network configuration at all, leads me to think something with the ISP mail service maybe at play here...Or if Windows 10 did any updates, you might check the update history around that time frame...
Can you test with a Windows 7 PC at home?
-
I will test with my win 7 laptop tonight. I don't think it's ISP settings since none of my different email SMTP settings work. Gmail, Yahoo, ATT, work email or Hotmail -- Nothing works. I have tried DCV versions 3.60, 3.64, 4.04 and 4.05. I was working on 3.60 in June. If I was blacklisted could the SMTP test still work or would it fail? I can look into being blacklisted too.
-
The SMTP test would fail I presume if your being block or some kind of mis-configuration.
Let us know how Windows 7 does...
-
Win 7 test email failed. I also tried changing things in my router around to see if that would be a problem. I see it updated the firmware but that was way back in March. Maybe I could roll that back to an earlier version...but Ive had it and will call AT&T (my ISP) tomorrow. I can call Linksys too to see if there may be something in there to block it. I have a Linksys EA6350 and it worked fine for 6 months. So it's either my ISP, or my router.
-
Let us know how it goes...
-
I bypassed my wireless router altogether and still had the same issue. My DSL modem is connected directly to my laptop. So Linksys and/or my wireless router are not causing the problem. it's either AT&T or something with the dviewcam software. do you all have a test program or app for smtp servers (with fields for port, ssl, authentication username and password and servername) that works? I downloaded 3 on the web and none of them work. One called SMTP test just says "disconnect" and "timeout" and gives me no info. Maybe it's an AT&T question. I am going to call them shortly. Thanks for the help. If you have any more suggestions that I can try..let me know.
-
I don't have any other suggestions. Seems like if you removed the external router and directly connected to the ISP service and it's still happening, possible ISP issue. Let us know if you find out anything from them...
-
Just remembered something you could try in collecting data for ISP to review if needed, try loading wireshark on a PC and while directly connected to the ISP modem, capture while your testing...
-
Thanks. Am doing this now. Will update you later.
-
;)
-
I have been having the same problem with DVC not sending emails. It worked fine for several months and then some time around late May or June it stopped sending motion detection emails. I'm running on an old Vista computer so its not just a Win 10 issue. I have checked my Win firewall and my Norton firewall and all looks ok. Was running an older version of DVC but now have Ver:4.0.5. I have since replaced my router so that takes that out of the equation. I am able to get emails directly from the cameras using gmail and yahoo SMTP servers so its not security issue on their end. So that tells me that it has to be something with my Vista computer or the DVC program. After reading this thread I'm leaning towards the DVC program. We have had some break ins in our area lately so I would love to get this back running. Like I said I'm currently getting my motion detection emails directly from the cameras but it is a bit cumbersome. Can't set them up the way I can on DVC. Any help would be great.
-
Link>Welcome! (http://forums.dlink.com/index.php?topic=48135.0)
- What region are you located?
Internet Service Provider and Modem Configurations
- What ISP Service do you have? Cable or DSL?
- What ISP Modem Mfr. and model # do you have?
What email service provider do you use?
What Mfr and Model router did you have before replacing and what is the Mfr and Model now?
-
I live in South Georgia. I have Dish Network DishNet satellite internet. I had Windstream DSL before Dishnet but the DVC stopped working before I changed internet providers. I did have an OLD Linksys N router. No idea what model it was. Now running a Netgear N750 router. I use gmail and yahoo email and have tried using both for the DVC email push. I have tried both on my cameras (DCS-932) and both work. Just not on the DVC program.
-
Ok, I'll forward this onto D-Link for review. Please be patient.
-
Well I called att 3 times with questions finally. They said it must be a dviewcam issue since the cameras are sending the pictures right and I can login correctly thru my email with outlook. I have DSL thru att. I have a netgear adsl2+ modem model 890-755025-15 dsl modem. I have looked and changed some things that I can change around in the modem and still have the same issue. I did get the Wireshark captures as well...they are pretty much the same as on one of the previous posts.
-
I am from Midwest GA with ATT DSL by the way...maybe it's a regional issue?
-
I've passed this on to D-Link for review. I presume it make take some time for them to look at the information and do some testing and fixing on this. I hope that the next release of DVC will have this fix.
-
Some users may want to review this and see if this help with DVC and Windows 10:
http://forums.dlink.com/index.php?topic=66142.0 (http://forums.dlink.com/index.php?topic=66142.0)
-
Well I was about to give up on dviewcam emailing pictures but it finally started working with my att email yesterday. I'm using the last previous version of dviewcam and it just started working. Must have been some att routers that were changed. I haven't tried it in 3 months but now it's all working smoothly!
-
What model ATT modem/routers had you been using and have currently?