Where did you come up with that 10.0.0.25 IP address?
I would have expected something in the range of 192.168.1.x for something on a local network.
Try something like: 192.168.1.118
MMMyCloud,
That is the IP address that is from my provider which is COX Cable. That is what is coming off my router settings. The 192.168.1.*** would not work for me.
OKā¦
Iām grasping at straws, but looking at the screen that sets up āStatic Network Modeā I see that āDNS Server 1ā is 10.0.0.1. That doesnāt look right to me, based on things Iāve done in the past. I would try removing that and just using the two 208.67ā¦ addresses.
The router should work out of the box with WDMC especially after you did the factory reset. Just incase, do you have internet access with the rest of your device connected to this router? Their Subnet, IP range, Gateway, DNS etc. should be the similar. I.e. check within windows ipconfig/all.
TTD:
-
Check the latest firmware:
Firmware Version V1.0.2.46_1.0.97
GUI Language Version V1.0.2.46_2.1.49.1 -
Do you have any VLAN tagging setup/enabled i.e. for set top box? Ensure you did not plugin WDMC into the port that has VLAN. If you donāt have enough ports, extend the non-VLAN ones using a switch.
-
Try these: R8000 ā Advanced ā Setup ā LAN Setup:
Address Reservation: Remove any IP Address: 192.168.1.1 IP Subnet Mask: 255.255.255.0 Use Router as DHCP Server: Checked Starting IP Address: 192.168.1.2 Ending IP Address: 192.168.1.254
Click apply and wait for the router to reinitialize. Then go back to WDMC Dashboard and set it to use DHCP. For whatever reason using DHCP fails, try Static:192.168.1.2/255.255.255.0, Gateway:192.168.1.1, DNS#1:192.168.1.1, DNS#2/3 you can set to your ISP DNS or Googleās 8.8.8.8/8.8.4.4.
You cannot force (use) a static IP address that is outside the subnet range provided by your router. For example, if your router is 10.0.0.1 then ALL of the devices in your LAN will be 10.0.0.xxx so do NOT attempt to change the MC to a 192.168.1.xxx as this will not work.
Use DHCP only. The router will assign a valid IP to your MC. If you do not have internet access for your MC then the problem lies elsewhere. Use the debug options (if this is a Windows system).
And, a 10.0.0.1 is a VALID IP for a local network. Some routers (notably Netgear) use that range automatically. The IP address 10.0.0.xxx, 172.16.0.xxx and 192.168.1.xxx are all allowed by design.
As indicated a few posts up, some providers configure their gateway/routers to use the gateway/router as the first DNS server when handing out DHCP client leases. My provider (Frontier) does this with the router/gateway they provide to their residential customers.
Edit to add: I currently have my My Cloud device configured to use the broadband provided gateway/router as the first DNS server and it works fine.
I can`t stress too much that if your not a trained network analyst then leave everything at your gateway router boot-up defaults. The only exception to this is if you find that your ISP DNS servers are slow or poorly populated then you can (if you are careful) change the default DNS server(s) in your gateway router to point to a faster one. Check out this site for an accurate analysis and guidelines to making the changes:
https://www.grc.com/dns/benchmark.htm
Paul
As suggested early in the thread, if the OP hasnāt done so already its probably advisable to read (or reread) the User Manual (http://www.downloads.netgear.com/files/GDC/R8000/R8000_UM_8Jul14.pdf) for that router and look at Chapter 5, Control Access to the Internet to ensure none of the options explained in that chapter are blocking the My Cloud from accessing the Internet.
If setting the My Cloud to DHCP doesnāt work, and the network/IP settings the My Cloud is obtaining from the router are valid/correct, that strongly suggests that there is a setting within the router that is preventing Internet access to the My Cloud.
Other troubleshooting steps, change Ethernet cables used to connect the My Cloud to the router (the My Cloud is directly connected to the router right?), connect that Ethernet cable to a different network port on the back of the router, power cycle every single device on the local network including the router and broadband modem, perform a factory reset on the router, disconnect all other network devices to the router other than the My Cloud and one computer.
Since he can SSH into the My Cloud to the point that it asks for a password. If he ca get to the internet from his PC. I believe the router and the cable and the ports being used are fine. He needs to get into the My Cloud to check the network options. Also check the resolv.conf file to see if it has the DNS ip addresses.
The question is why canāt he login?
RAC
[quote=ārac8006, post:29, topic:136716, full:trueā]
Since he can SSH into the My Cloud to the point that it asks for a password. If he ca get to the internet from his PC. I believe the router and the cable and the ports being used are fine.
ā¦[/quote]
Oh I agree those are probably fine. But at this point it couldnāt hurt to cross those items off the troubleshooting list.
There is obviously something not right either within their Netgear router or some sort of misconfiguration error within the My Cloud that is not being reflected on the Dashboard interface. The SSH access is obviously indicating something is wonky. They changed things with OS3 firmware where one is prompted to change the SSH password upon first logging into SSH. If the OPās My Cloud was used and obtained from someone else its possible that person changed the SSH password rendering the initial default password (welc0me) unusable. If that My Cloud was used its possible the previous user modified the OS with add-on modules or edited files via SSH causing the current issues.
I donāt recall seeing if the OP did a āresetā either 4 second or 40 second or even a full restore reset. The OP should at the very least do a 4 second reset to see if that clears the SSH login problem. If that doesnāt work then do a Quick Restore after backing up any data on the device to see if that clears up the SSH login problem.
To all,
As of right now, I am able to do a TimeMachine backup with both my desktop (iMac) and my laptop (MBP). I do have internet connections through all my other devices both Ethernet and through WiFi. The only thing though is that it is taking way to long to back up. I started the back up on both units early afternoon yesterday and I checked this morning and they are not even at the half way point. Does it really take that long to back up. I have both units hooked up on ethernet cables, not WiFi. My iMac has 422.04 GB of 2.35 TB left on it and my MBP has 403.89 GB of 1.11 TB left on it.
There has to be something with my settings that is still having my WDMC to still indicate that there is no internet access. It looks like I am able to transfer files to the unit but why does it still indicate that I donāt have internet access? I also tried to see if I can access it through my iPhone through their MyCloud App and I can see it. So what might be the problem?
The problem is that you need SSH. To be able to look at the WDMC parameters. Also you
probably have the file indexing programs running while you are backing up. Which cause extra overhead.
RAC
Was your iPhone connected remotely via your cellular data plan to the My Cloud? I.e. the phone was not connected to your local WiFi network.
As to your comment about slow speeds. That is dependent on many factors not the least of which is how the computer being backed up is connected to the local network. To backup a computer with a large hard drive over WiFi can actually take several days on a slow WiFi connection.
See the following link for a discussion on copying speed on the My Cloud.
Iām using the same R8000 router and the stock firmware has itās gateway set to 192.168.1.1 by default. Refer to my previous post on how to set to 192.168.1.1. Technically 10.0.0.1 should work but Iām not sure about OS3 as Iām still using 04.01.02-417. I suspect that your resolv.conf:
cat /etc/resolv.conf nameserver 192.168.1.1
is pointing to a non-existence DNS hence you canāt resolve internet hostnames but WDMC isnāt checking hostnames for the internet access status (see below why). So you need to be able to SSH into the WDMC to check further. If required, do the 40secs reset to revert the default root password as stated in the WDMC manual (this will also revert your WDMC to default state but data preserved).
JFYI, the WDMC Dashboard is checking againts Google DNS then OpenDNS TCP port 53 for internet access. If you can SSH into WDMC, you can test:
curl http://localhost/api/1.0/rest/internet_access/googledns
curl http://localhost/api/1.0/rest/internet_access/opendns
curl http://localhost/api/1.0/rest/internet_access/wd2go ā this one www.wd2go.com:80 is specified but doesnāt seems to be doing any checks even in OS3 (I got hold of the latest OS3 rootfs).
And you should see the results:
<?xml version="1.0" encoding="utf-8"?> <internet_access> <connectivity>true</connectivity> </internet_access>
You can also check if either of the DNS is blocked by your ISP, from your PC command prompt:
telnet 8.8.8.8 53
telnet 208.67.222.222 53
And you should see a blank screen. If telnet is not enabled on your PC, use putty instead, set to telnet, IP:208.67.222.222 port:53 (for 8.8.8.8:53 youāll get disconnected instantly this is normal).
I shall not get more technical, you should be able to figure out something from all the above previous users post. If youāre still lost, temporarily enable the remote management on the R8000 default port 8443 and PM me your IP/credentials (you still need to reset your root password).
Looking at your port forwarding setup, I have the following observations:
Why did you choose port 3333 for http?
What service did you specify for that port? It should be TCP/upd
Why is there only one port? It is usual to have two ports, for http and https, being 80 and 443.
Or 8080 and 8443
Take a look at the Static IP configuration of the My Cloud, please
IP address: 10.0.0.25
Subnet mask: 255.255.255.0
It has to be
subnet mask 255.0.0.0
to get this Static IP working, itās a Class A network, not a Class Cā¦
Given that the IP addresses allocated are 10.0.0.X specifying a mask of 255.255.255.0 ought to work, surely? Isnāt it just saying 'you can only change the bottom byte? Whereas a class A mask of 255.0.0.0 says āyou can use the three LSBsā?
Correct, but I can imagine that the router - or better spoeken its LAN switch - is not able to handle different subnet masks internally. I know only one router, or better one router firmware, that is able to do this but even here it happens often that problems occur. Give the correct subnet mask 255.0.0.0 a try.
Next thing: why using Static IPs on client devices which may counteract to the DHCP server settings of the router?
Is the 10.0.0.25 outside of the routerās DHCP table?
Why not using Static Lease for the DHCP IP addresses which the router has given to the client devices? Much more easy than coping with Static IP addresses on Client devicesā¦
I agree about using DHCP and an infinite timeout/static lease/always use this address. It eliminates all the mucking about with settingsā¦
The Class A subnet mask 255.255.255.0 is correct for 10.0.0.1/24. His router will support up to 254 IPs broadcast 10.0.0.255.
He has no issues with the IPs which he can still do transfers locally. But his dashboard says no internet access which also means no remote support available. Something is blocking the php socket checks from his dashboard to GoogleDNS and OpenDNS which he can only find out after restoring SSH access.
