D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: chiefnet on January 31, 2009, 05:23:19 PM
-
Hello all. I've tried setting up my email notifications so many different ways with no luck. I've gone through others' emails for setting up, but still nothing. I have a Gmail account, but I saw conflicting emails saying it will work with 1.05, and one email saying it won't due to spam filters. Does anyone know which one is true? Do I need to update to 1.06? I'd rather stay with 1.05. I have RCN isp. I also opened up ports 465 and 587 as gmail said I should set the settings, and port 25 for isp. I've seen the following the most, and have tried this....
Login Method : Account
User Name : username@gmail.com (tried without gmail.com as well)
Password : gmail password
SMTP Server : smtp.gmail.com (tried smtp.rcn.com as well)
Sender E-mail : username@gmail.com
Receiver E-mail : username@gmail.com (I've tried username@hotmail.com as someone else mentioned trying)
-
Support for gmail was one of the bug fix in FW1.06
Thomas
-
Thanks for the clarification Thomas.
-
FYI - one mistake i did was i setup my device using a static address and i forgot to put an IP address in for DNS.
-
savva,
I have the non-static IP address for the DNS. I set up the port forwarding with the DNS IP address, is that what you mean?
-
If you use DHCP then you are fine; your router would provide the NAS unit all the addresses that are necessary. To double check go to your status page on the webpage and yours should look something similar to this:
IP Address: 192.168.x.x
Subnet Mask: 255.255.255.0
Gateway IP Address: 192.168.x.x
Mac Address: xx:xx:xx:xx:xx:xx
DNS1: 192.168.x.x
Post what your settings are aswell.
The other issue that i ran into you already address which was change the receiver's email to something other then gmail (ie: your hotmail).
When you click on test what error message do you get?
-
.
Login Method : Account
User Name : username@gmail.com (tried without gmail.com as well)
Password : gmail password
SMTP Server : smtp.gmail.com (tried smtp.rcn.com as well)
Sender E-mail : username@gmail.com
Receiver E-mail : username@gmail.com (I've tried username@hotmail.com as someone else mentioned trying)
Hi,
When I used the receiver e-mail <username@hotmail.com> to get my notifications, I was using ver 1.06 and I did not need opening any other ports. This might sound like a stupid question, but, chifnet, Do you have a hotmail account? The rest of the setup is he same as the one I used.
Good luck, just keep trying. It took me 2 hours to get my printer working with Dns-323. ???
-
If you use DHCP then you are fine; your router would provide the NAS unit all the addresses that are necessary. To double check go to your status page on the webpage and yours should look something similar to this:
IP Address: 192.168.x.x
Subnet Mask: 255.255.255.0
Gateway IP Address: 192.168.x.x
Mac Address: xx:xx:xx:xx:xx:xx
DNS1: 192.168.x.x
Post what your settings are aswell.
The other issue that i ran into you already address which was change the receiver's email to something other then gmail (ie: your hotmail).
When you click on test what error message do you get?
saava,
My settings were as you noted above, with the DNS1 being the same as the IP address, and IP address being that of the box. No luck.
My error message is just "Test Result: Failure". Same message for all different settings I've used.
-
escaramujo,
Yes, I do have a hotmail account, and used that username and account. Unfortunately, no luck. I'm not ready to upgrade to 1.06 since 1.05 is running pretty stable and I've seen so many posts of issues with 1.06, so I may wait until 1.07. Thank you.
-
Chiefnet, just to double check, your DNS should be the same as your Gateway IP Address... is that how yours is?
-
savva,
My mistake when I typed. You are correct, my Gateway IP and DNS are the same.
-
Last thing i could think of is to do ipconfig /all on your PC and see what information comes up for DNS. I just remembered that some routers provide the ISPs DNS IP address.
If that doesnt work, the only other thing i could thing of is to do a Factory Reset ???
-
I have tested with gmail and yes it's not compatible. I am with rogers.com provider and using their smpt works fine with the dlink smtp.broadband.rogers.com if your a rogers user
-
Gmail uses SSL Authentication and a different base port. It is not supported in ANY firmware before 1.06.
-
I cannot get 1.06 to talk to gmail.
The problem seems to be a DNS problem. Here is a tcpdump packet trace:
16:03:48.062665 IP 10.0.1.1.1024 > 10.0.0.1.domain: 2+ AAAA? smtp.gmail.com. (32)
16:03:48.130153 IP 10.0.0.1.domain > 10.0.1.1.1024: 2 1/1/0 CNAME[|domain]
16:03:48.130175 IP 10.0.1.1.1024 > 10.0.0.1.domain: 3+ AAAA? gmail-smtp-msa.l.google.com. (45)
16:03:48.141180 IP 10.0.0.1.domain > 10.0.1.1.1024: 2 1/1/0 CNAME[|domain]
16:03:48.141188 IP 10.0.1.1.1024 > 10.0.0.1.domain: 4+ AAAA? gmail-smtp-msa.l.google.com. (45)
16:03:48.197813 IP 10.0.0.1.domain > 10.0.1.1.1024: 3 0/1/0 (93)
16:03:48.197836 IP 10.0.1.1.1024 > 10.0.0.1.domain: 5+ AAAA? gmail-smtp-msa.l.google.com. (45)
16:03:48.206772 IP 10.0.0.1.domain > 10.0.1.1.1024: 4 0/1/0 (93)
16:03:48.208280 IP 10.0.1.1.1024 > 10.0.0.1.domain: 6+ AAAA? gmail-smtp-msa.l.google.com. (45)
16:03:48.208364 IP 10.0.0.1.domain > 10.0.1.1.1024: 3 0/1/0 (93)
16:03:48.208767 IP 10.0.1.1.1024 > 10.0.0.1.domain: 7+ AAAA? gmail-smtp-msa.l.google.com. (45)
16:03:48.220308 IP 10.0.0.1.domain > 10.0.1.1.1024: 4 0/1/0 (93)
16:03:48.220316 IP 10.0.1.1.1024 > 10.0.0.1.domain: 8+ AAAA? gmail-smtp-msa.l.google.com. (45)
16:03:48.261554 IP 10.0.0.1.domain > 10.0.1.1.1024: 5 0/1/0 (93)
16:03:48.263250 IP 10.0.1.1.1024 > 10.0.0.1.domain: 9+ A? smtp.gmail.com. (32)
16:03:48.272232 IP 10.0.0.1.domain > 10.0.1.1.1024: 6 0/1/0 (93)
16:03:48.272239 IP 10.0.1.1.1024 > 10.0.0.1.domain: 10+ A? smtp.gmail.com. (32)
16:03:48.274911 IP 10.0.0.1.domain > 10.0.1.1.1024: 5 0/1/0 (93)
16:03:48.274919 IP 10.0.1.1.1024 > 10.0.0.1.domain: 11+ A? smtp.gmail.com. (32)
16:03:48.277787 IP 10.0.0.1.domain > 10.0.1.1.1024: 7 0/1/0 (93)
16:03:48.279294 IP 10.0.1.1.1024 > 10.0.0.1.domain: 12+ A? smtp.gmail.com. (32)
16:03:48.284406 IP 10.0.0.1.domain > 10.0.1.1.1024: 6 0/1/0 (93)
16:03:48.284413 IP 10.0.1.1.1024 > 10.0.0.1.domain: 13+ A? smtp.gmail.com. (32)
16:03:48.286300 IP 10.0.0.1.domain > 10.0.1.1.1024: 8 0/1/0 (93)
16:03:48.286308 IP 10.0.1.1.1024 > 10.0.0.1.domain: 14+ A? smtp.gmail.com. (32)
16:03:48.289960 IP 10.0.0.1.domain > 10.0.1.1.1024: 7 0/1/0 (93)
16:03:48.297351 IP 10.0.0.1.domain > 10.0.1.1.1024: 8 0/1/0 (93)
16:03:48.297359 IP 10.0.1.1 > 10.0.0.1: ICMP 10.0.1.1 udp port 1024 unreachable, length 129
16:03:48.327578 IP 10.0.0.1.domain > 10.0.1.1.1024: 9 3/0/0 CNAME[|domain]
16:03:48.327586 IP 10.0.1.1 > 10.0.0.1: ICMP 10.0.1.1 udp port 1024 unreachable, length 138
16:03:48.338810 IP 10.0.0.1.domain > 10.0.1.1.1024: 10 3/0/0 CNAME[|domain]
16:03:48.338819 IP 10.0.1.1 > 10.0.0.1: ICMP 10.0.1.1 udp port 1024 unreachable, length 138
16:03:48.339697 IP 10.0.0.1.domain > 10.0.1.1.1024: 9 3/0/0 CNAME[|domain]
16:03:48.340915 IP 10.0.1.1 > 10.0.0.1: ICMP 10.0.1.1 udp port 1024 unreachable, length 138
16:03:48.342714 IP 10.0.0.1.domain > 10.0.1.1.1024: 11 3/0/0 CNAME[|domain]
16:03:48.343995 IP 10.0.1.1 > 10.0.0.1: ICMP 10.0.1.1 udp port 1024 unreachable, length 138
16:03:48.345923 IP 10.0.0.1.domain > 10.0.1.1.1024: 12 3/0/0 CNAME[|domain]
16:03:48.345930 IP 10.0.1.1 > 10.0.0.1: ICMP 10.0.1.1 udp port 1024 unreachable, length 138
16:03:48.349972 IP 10.0.0.1.domain > 10.0.1.1.1024: 10 3/0/0 CNAME[|domain]
16:03:48.349981 IP 10.0.0.1.domain > 10.0.1.1.1024: 13 3/0/0 CNAME[|domain]
16:03:48.352854 IP 10.0.0.1.domain > 10.0.1.1.1024: 14 3/0/0 CNAME[|domain]
10.0.0.1 is my router and from my PC (on the same LAN), an nslookup works fine and reports back:
Non-authoritative answer:
Name: gmail-smtp-msa.l.google.com
Address: 216.239.59.109
Aliases: smtp.gmail.com
If I put the ip address in there, it seems to get farther but it doesn't seem to do a starttls and hence fails.
So I'm perplexed, how do you make the dns-323 talk to a gmail account using version 1.06?
-
Can you do an ipconfig /all on your pc and post the results?
-
Sure, here's an ipconfig/all:
C:\Documents and Settings\Mickael>ipconfig/all
Windows IP Configuration
Host Name . . . . . . . . . . . . : GRUMBLE
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI
Gigabit Ethernet Controller
Physical Address. . . . . . . . . : 00-22-15-78-54-3B
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.0.3
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 10.0.0.1
-
Alright, can you try to see if NTP or DDNS works?
One thing you can try tho before is to use the following IPs for your DNS 208.67.222.222 and/or 208.67.220.220 on your NAS unit
-
I was using NTP already and it's updating the time on the NAS correctly. I just configured dyndns and that updated successfully as well.
I tried using an ip address of a server that does not require ssl that is running sendmail and it gets a little farther in the packet exchange but sendmail does not seem to like the 'EHLO localhost' that the NAS sends, I think sendmail wants to see something that matches the DNS. So it seems my trouble is a DNS issue.
I have solved the problem now. The problem turned out to be the DNS provided by my little adsl modem/router. I configured the router to give a real dns server instead of itself as the dns server and then the mail went through to gmail without problem from the NAS.
What was quite frustrating is that the test button doesn't show what's going on. I bet there are not many people out there who are going to know how to decode a packet trace to see the error like I'm doing.
For those interested in how I'm seeing the packet exchange, I have a PC on my network using an old style ethernet hub (not an ethernet switch), then I am using "tcpdump -X -s0 host 10.0.1.1" on unix/linux on a PC connected to that hub to watch the packets between the NAS and the outside world. Equally on windows/mac/linux one could run http://www.wireshark.org/ (http://www.wireshark.org/) instead of tcpdump.
-
Actually I spoke a little too soon. Ok, I have the NAS sending mail to gmail fine, but I have a second NAS that I need to send mail to this other address which is not gmail, it's a unix box running sendmail. The sendmail box is known to work, it gets a ton of mail. This NAS was sending mail to the sendmail box fine with 1.05 firmware, but now with 1.06, it is broken.
The sendmail box requires an authentication. It doesn't require TLS but it will use it. From the packet trace, I see the NAS connect to the sendmail server and say EHLO localhost and the NAS just drops the connetion. The NAS is set to use a login method of account and a username and password are configure.
<<< 220 example.org ESMTP server
>>> EHLO localhost
<<< 250-example.org Hello adsl-1-2-3-4.example.net [1.2.3.4], pleased to meet you
<<< 250-ENHANCEDSTATUSCODES
<<< 250-PIPELINING
<<< 250-8BITMIME
<<< 250-SIZE
<<< 250-ETRN
<<< 250-AUTH PLAIN LOGIN
<<< 250-STARTTLS
<<< 250-DELIVERBY
<<< 250 HELP
>>> (the NAS closes the connection)
Does the NAS perhaps not like the proposed AUTH methods of PLAIN and LOGIN? I notice that the gmail server doesn't emit the AUTH line at all and the NAS goes right in and starts TLS.