Comments
-
This worked! More or less, anyway - the Internet access works, it used to have http://192.168.1.113:5000/MyWeb/video/ also available with my external IP in place of the internal one there for friends to access, which now says "The requested URL /MyWeb/video/ was not found on this server" (a change from either time out or…
-
Noooooo, after our Internet went down for a day, it has somehow reverted to its previous state, and no amount of turning SSH on and off or such is making any difference this time. I presume no-one has any ideas? The route command looks exactly the same as in the above.
-
Sorry yes, I meant SSH. Not an IPv6 address, no: a, er, port number, if I have it right? As in it used to be http://192.168.1.100/ or http://nas326/ locally and it instead changed to http://192.168.1.100:392/ or http//nas326:392 after turning SSH on. Or perhaps after running one of the above commands? I'm not sure what's…
-
Waittttt, turning on the SSL changed the NAS address to have a :392 at the end, and somehow this has made it work? I'm not sure what the status was when I ran the first route above - I should've checked, but it's been consistent every time I've looked - but it's now accessing the Internet seemingly fine
-
Thank you! Here's the full result - the first lot is before applying, the second is after (and I checked it pinged externally before and after running the second lot). It seems to create a default line above the "Gateway: *" line with a gateway of 192.168.1.1, which is my router's address, during that 30 seconds.
-
Thank you, but forgive me - I'm not a network admin but just a home user, and I'm looking at the Web GUI, and can't see any terminal where I'd enter the above. Unless you mean in command prompt, which allows a route command but not cat or ifconfig?
-
I'm resurrecting this because my NAS326 is doing the exact same thing. Reapply DNS settings: get Internet access for maybe 30 seconds, during which time it can ping external sites, find the UPnP router etc. The rest of the time: pinging the router's fine, pinging externally isn't. This may be missing an obvious piece of…