Microserver Dropouts

[nateboy]

Looking for some help/ideas from the brains trust;

 

I've recently rolled my own xpenology install onto an N54L, went well enough. Assigned it to a static IP rather than DHCP, and then hooked it up to a Ethernet over Powerline network at my parents place, and was it was reachable/highly contactable for both web-admin/file access across the network.

 

I've since then brought the server back to my own place, plugging it directly through ethernet into the modem/router, and now face intermittent contact issues to it. A lot of the time I will get an issue reaching either the shared folders (either from a laptop or PS3) or the web access, or if I do, the connection will inevitably drop-out.

 

The weird thing is though, accessing the Internet is still fine, i.e. at the same time as getting server can't be reached messages, I will be able to pull-up internet pages fine. So on paper, that would seem to rule out phsyical network connectivity issues between the devices, given that they all seem to still be talking to the modem/router fine, and the comm drop out specific to the server...?

[andywhit]

Which DSM version/release are you running ?

[nateboy]

4.3

[Dfds]

Since you've moved the network it was on when you set it up have you checked that the static IP isn't conflicting with any thing else on your network, also check that the IP range supplied by your router is the same as it was on your parents network i.e. 192.168.0.xx or 192.168.1.xx

[andywhit]

4.3

 

Which release of 4.3 ? I'm trying to work out if you're on a version which has the security flaw that allows hackers to turn your system into a bitcoin miner bot. If so the system might be running so hot (in CPU terms) that it's struggling to serve content to you.

 

Is the CPU level reported in DSM very low ? If so then you've not been hacked.

[nateboy]

Oh, sorry, seems to be... "4.3-3810"...? The CPU Usage seems to be pretty low (ie. less than 10%), but will continue to monitor...

[andywhit]

Oh, sorry, seems to be... "4.3-3810"...? The CPU Usage seems to be pretty low (ie. less than 10%), but will continue to monitor...

 

 

If it's the vanilla 3810 then it's vulnerable, you should look to upgrade asap.

 

viewtopic.php?f=2&t=2049

[nateboy]

Oooh, right, thanks for the tip, will do that asap and see if that resolves things (also)

[nateboy]

Hi guys, thanks heaps for all your help; after quite a bit of tinkering with the various ways to update to v4, finally managed to do so, and actually still found the drop-outs occurring (in spite of everything else on the network still being contactable, etc.); what I did then, just to see if it made any difference, was take the manual IP/DNS specs off (configured within Xpenology), turn on DHCP, and weirdly enough, everything is now working fantastically :S Thanks again though, for looking into the issue, and providing responses.

[andywhit]

Sounds like you might have had an IP clash then. If you still want a fixed IP then do it via your router and get it to allocate a fixed IP based upon the microserver's MAC address. That way the microserver is setup to use DHCP and the router will manage the IP allocation and not cause IP clashes.