NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Got a brand new ReadyNAS 104 and it crashes when trying to setup Dropbox
I got my ReadyNAS 104 a week or so ago, and slapped 4 1TB Seagate drives in it, updated firmware to the newest release 6.4.2 and setup an iSCSI target. It's been working great and not had any issues...
Received your logs. Thanks.
Looks like you are missing a DNS server or a gateway possibly. Lots of services like msmtp (e-mail alerts), Cloud services, are producting errors mentioning unable to connect to internet services. You have many e-mails queued up to send, but this seems intermittent (worked on Mar 2nd, didn't work Mar 3rd).
Dropbox is erroring out: error in dropbox/request_token api. http-status=500, means Internal Server error.
Can you double check DNS servers are valid and also that your default gateway is on your routable network?
Received your logs. Thanks.
Looks like you are missing a DNS server or a gateway possibly. Lots of services like msmtp (e-mail alerts), Cloud services, are producting errors mentioning unable to connect to internet services. You have many e-mails queued up to send, but this seems intermittent (worked on Mar 2nd, didn't work Mar 3rd).
Dropbox is erroring out: error in dropbox/request_token api. http-status=500, means Internal Server error.
Can you double check DNS servers are valid and also that your default gateway is on your routable network?
You are right, that was the problem, nice! One of my NICs didn't have a DNS server setup so I disabled that NIC and now when I click ON the Activate button lights up and I was able to finish the setup and it's now working.
The reason I didn't have the second NIC setup correctly was because I use one NIC with a real IP address on my normal network, so it has a DNS and gateway and is seen on my network. The other NIC is plugged directly into one of 4 NICs on my server which has a VMware virtual switch and NIC tied to it. I did this to keep iSCSI traffic on my regular network without have to create a separate VLAN and the VM host can see the iSCSI target that way while the ReadyNAS is seen (as SMB) on my regular network through the other NIC. It actually works great except for this... I guess the ReadyNAS tried to send outside traffic out the NIC that doesn't really go anywhere.
I noticed that I setup eth0 with the "fake" network and eth1 with the real network. I'm guessing that it tries eth0 first when trying to reach the Internet so I'm going to swap the settings of eth0 and eth1 so that eth0 has the IP on my regular network with Internet access and see if that works with both NICs enabled.
ReadyNAS won't care what network adapter you use as long as it is configured correctly. Even if eth0 is your 'fake' iSCSI network, your eth1, with a proper DNS and gateway, should be the default route for all traffic. Do not set a gateway on your eth0 and your eth1 should have a gateway. If you see your eth1 gateway in eth0, don't panic. That's normal.
Before I got your response I had already swapped the settings for the adapters and plugged them both back in. I was able to switch Dropbox on and off and it still works. This problem with routing traffic before also explains why when I clicked on Firmware Update it would just spin and not do anything else. Now it tells me there's no new update available so it's actually reaching out and checking.
This time I didn't setup a router or DNS server for the iSCSI network, since it wouldn't need either anyway, and although I already moved it to eth1, it's working now so it must've been because I didn't enter a router or DNS server this time so it's not even attempting to send traffic out that interface. I'm also glad I didn't have to put the iSCSI traffic on my regular network because of this.
Thanks for the help, I didn't stop and consider it being a network problem and didn't look at the detailed logs so I was assuming it was something crashing on the OS.
JeremyL wrote:
Thanks for the help, I didn't stop and consider it being a network problem and didn't look at the detailed logs so I was assuming it was something crashing on the OS.
You did have a crash that you should not have been experiencing because of a bad network config. I PM'd you seperately about this to collect data.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
