Pages: [1]   Go Down
Print
Author Topic: Mede8er only accessible via NAS once and a while  (Read 978 times)
flouzje
Newbie

Offline Offline

Posts: 22


« on: August 15, 2010, 01:47:22 pm »

Hi,

My mede8er is connected to my network at home (a switch)
Sometimes it works, sometimes it doesn't. ("mede8er is not accessible")
Today it was working ok, and suddenly out the blue I lost the connection, while the mede8er wasn't turned off.
Anybody experienced the same problems ?
I have installed the latest firmware version.

Thanks
Logged
pc 37
Newbie

Offline Offline

Posts: 1


« Reply #1 on: August 16, 2010, 05:32:21 pm »

i have the same problem, please help

pc 37
Logged
tachita
Guest
Newbie

Offline Offline

Posts: 0



« Reply #2 on: August 16, 2010, 11:07:37 pm »

For now the most simple way is to toggle NAS from on to off and back to on
Logged
flouzje
Newbie

Offline Offline

Posts: 22


« Reply #3 on: August 17, 2010, 08:35:52 am »

Will this be taken care of with the next firmware release ?
This is very annoying, and apparently lots of people are having this problem.
Logged
tachita
Guest
Newbie

Offline Offline

Posts: 0



« Reply #4 on: August 17, 2010, 11:01:33 am »

Will this be taken care of with the next firmware release ?
This is very annoying, and apparently lots of people are having this problem.

I hope so...
Logged
jer1956
Global Moder8or
Hero Member
*****
Offline Offline

Posts: 9 142


« Reply #5 on: August 17, 2010, 11:42:47 am »

You say your using  a switch. Is this on all the time, or powered up and down with other equipment? Most users may well bw using a full blown firewall/router which may make the difference. These mediaplyer chips seem very particluer and operate best in a typical home configuration. Use a PC monitor, or a lan switch etc, and things stop working as they should.
Logged
Domino1999
B8a Tester
Senior Member
***
Offline Offline

Posts: 420


« Reply #6 on: August 17, 2010, 01:52:05 pm »

I really hope they fix this in the next FW. I've read and participated in many of the other threads where this issue has been discussed, so tried all suggestions etc., but I still have this issue and just toggle NAS off/on to sort it out when the problem happens.

I still haven't been able to nail the exact circumstances under which the Mede8er becomes inaccessible over the network, although it does seem to be after a period of time, rather than to do with anything I'm actually doing. Maybe it's a period of inactivity of the Mede8er, where it's switched on but not doing anything, or maybe it's MS Windows that's the culprit...who knows!
Logged

Mede8er model: MED500X
Board: 1073DD
Bootloader: 0000.0202.1026
Firmware: V4.04 INC_HD Audio
Internal HDD: WD20EADS 3.5" Caviar Green 2TB SATAII 32MB
External USB HDD: Seagate FreeAgent 1TB
Network: Home Plugs (NETGEAR Powerline AV Adapter with Ethernet Switch XAVB1004 bridge)
Router: BT HomeHub V2
Display: Panasonic TX-L37G15B
Audio connection: HDMI to TV
Audio output devic
tachita
Guest
Newbie

Offline Offline

Posts: 0



« Reply #7 on: August 17, 2010, 02:13:19 pm »

I really hope they fix this in the next FW. I've read and participated in many of the other threads where this issue has been discussed, so tried all suggestions etc., but I still have this issue and just toggle NAS off/on to sort it out when the problem happens.

I still haven't been able to nail the exact circumstances under which the Mede8er becomes inaccessible over the network, although it does seem to be after a period of time, rather than to do with anything I'm actually doing. Maybe it's a period of inactivity of the Mede8er, where it's switched on but not doing anything, or maybe it's MS Windows that's the culprit...who knows!

most of time is the target machine fault, in our case M8R NAS, but this is happen when the sender machine lost his connection for a while and try to reconnect..... it is a sort of chain : computer + M8R server faults.
to keep connection alive, i think , you could keep open a ping response from M8R ip (ping mede8er ip -t).
i dont know if will work for you , cause dont know the particular problem of your system and most of time it is very hard to identifiy them.   i was not forgot about M8R server fault , he is the big problem here : he cant be wake up after connection lost. so, a ping should keep alive 

 Huh Huh
Logged
mark.m.moran
Newbie

Offline Offline

Posts: 23


« Reply #8 on: August 18, 2010, 11:45:10 pm »

Hi all,
Does anyone have issues with a connected USB HDD and it suddenly not working like the NAS? When I copy a file from the network (my laptop) say to an attached HDD and after this you try to browse\access the file on the HDD it can't read anything from the drive?? Its like the drive has gone to sleep? I have a 1TB WD Elements and it does this. Does this drive have a sleep mode??

You have to power off and back on the Mede8er and as soon as you do I can hear the HDD coming back to life???

Cheers,
M
Logged
chicken-
Newbie

Offline Offline

Posts: 4


« Reply #9 on: August 21, 2010, 06:34:17 pm »

I own 2 mede8ers, one of which never had a problem showing up on the network.  The other I've always had to toggle nas mode for it to show up.  After upgrading to the latest firmware 2 weeks ago, I've only gotten it to show up on the network ONCE.  They have yet to address this in any of the firmware updates in the 8 months I've had this product and I'm quite disappointed.

The funny thing is that since the newest firmware I've been able to access other workgroup computers from the mede8er which never worked before, but still can't do anything other than FTP files from PC to mede8er.
« Last Edit: August 21, 2010, 06:49:41 pm by chicken- » Logged
mover
B8a Tester
Active Member
***
Offline Offline

Posts: 78



« Reply #10 on: August 22, 2010, 03:47:24 pm »

Even if the Med8er doesn't show up when browsing your network, you should still be able to access it by typing its host name (\\mede8er) or IP address (\\a.b.c.d).
Logged
riccardoz
Newbie

Offline Offline

Posts: 36


« Reply #11 on: August 22, 2010, 03:56:22 pm »


try "\\1.2.3.4\hdd1"  and set static IPs, it worked out the issue for me.
Logged
tachita
Guest
Newbie

Offline Offline

Posts: 0



« Reply #12 on: August 22, 2010, 05:46:57 pm »

try "\\1.2.3.4\hdd1"  and set static IPs, it worked out the issue for me.



 Huh Huh Huh Huh

can you explain more?
Logged
Pages: [1]   Go Up
Print
Jump to: