NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Error when trying to "Send Message" to Alert Contact "Unable to send a test message"
After some time it displays a message box with "Unable to send a test message".
I've restarted the nas.
I've tried a Microsoft email address instead of a gmail address.
Emails have been sending...
itnorm wrote:
I putty'ed into the NAS in my office and got this:
https://i.gyazo.com/740b3821ad29c9b99502f1eb12bb3ff9.png
I see that ping succeeded to google, but ifconfig shows 16 errors for Rx with both ethernet links.
What bonding mode are you using for the two NICS?
Are you using static IP addresses? If so, did you remember to set up the DNS server?
On the errors, perhaps check back later and see if the counts increase.
BTW, if your local network doesn't use IPv6, I recommend disabling the protocol on the NAS.
The ethernet ports are not bonded.
Rx errors are at 19 right now.
IPs are not static and have not changed.
IPv6 has been disabled.
You might want to run the test as shown here -> https://community.netgear.com/t5/New-ReadyNAS-Users-General/RN104-OS695-unable-to-send-alert-messages/m-p/1750936/highlight/true#M36648
itnorm wrote:
The ethernet ports are not bonded.
.
That could be part of the problem. I suggest disconnecting the second ethernet port for now.
Generally speaking, you shouldn't use both ports unless you are bonding them.
itnorm wrote:Rx errors are at 19 right now.
It's odd that they both are in lock step. Is the NAS connected to a switch or is it directly connected to your router?
Well, I went to try the email test thru ssh as you suggested and now I can't access the NAS thru putty. Tried different users and different ip address (eth0 and eth1) and a different computer. All return a message that says "Remote device unexpectedly closed network connection" after I enter the password. Also, noticed that it seems to taking alot longer than other days, it takes several minutes after I enter root for the password to appear and then several minutes for the message to appear.
Then I disconnected one of the ethernet cables.
Putty connected at its faster and usual speed.
And the email test mesage was sent and received.
Thanks.
I have a side question related to this area.
Can I do a local connection thru ssh and a remote connection thru rsyncoverssh and use different ports?
I'd like the rsync to still use port 22, but the local ssh to use another port. Is there info on how to do this if possible?
itnorm wrote:Well, I went to try the email test thru ssh as you suggested and now I can't access the NAS thru putty. Tried different users and different ip address (eth0 and eth1) and a different computer. All return a message that says "Remote device unexpectedly closed network connection" after I enter the password. Also, noticed that it seems to taking alot longer than other days, it takes several minutes after I enter root for the password to appear and then several minutes for the message to appear.
Then I disconnected one of the ethernet cables.
Putty connected at its faster and usual speed.
And the email test mesage was sent and received.
This would confirm the suspicion an unluckly (default) Kernel/IP stack config - where the return traffic is not forced to incoming interface, the default does allow using any interface connecting to the same interface, what good firewall software does simply refuse.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
