Print

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

[valandor]

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.

[FurryNutz]

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.

[valandor]

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.

[FurryNutz]

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?

[valandor]

No, I don't have any new Windows 10 installation media available. 

[FurryNutz]

Windows 10 installation can be downloaded and burned to DVD if that's an option.

Windows 10 makes it harder to deal with updates. 

[noshoken]

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...

[FurryNutz]

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.

[noshoken]

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...

[FurryNutz]

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. 

[noshoken]

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?

[FurryNutz]

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.

[noshoken]

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

[FurryNutz]

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.

[noshoken]

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...