Bug 6505 - WD TV live can't connect to NFS share (other linux can)
Summary: WD TV live can't connect to NFS share (other linux can)
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-18 22:09 CEST by Tamás Hajdu
Modified: 2012-07-09 11:45 CEST (History)
0 users

See Also:
Source RPM: nfs-utils-1.2.6-4.mga3
CVE:
Status comment:


Attachments

Description Tamás Hajdu 2012-06-18 22:09:37 CEST
Description of problem:
Can not connect to nfs share with WDTV live, while on desktop with mageia 2 there are no problem (nfs-utils-1.2.5-1.mga2)

Version-Release number of selected component (if applicable):
Cauldron

How reproducible:
always

Steps to Reproduce:
1. Set up an nfs share
2. try connect to nfs share with wd tv live
3. watch timeout on wdtv
Comment 1 Manuel Hiebel 2012-06-20 15:00:09 CEST
it works with using the command line ?
Comment 2 Tamás Hajdu 2012-06-20 18:23:10 CEST
Here is situation: 

I have a laptop and a desktop (laptop is running cauldron, desktop is running mageia 2). I can mount any shares from the desktop on WDTV, but none of the shares of my laptop. My laptop is attached on wifi to the network, the desktop is on cable. 
On the other hand I can mount the shares of my laptop on my desktop and vica-versa. 
Since WDTV has no console (or I don't know how to reach it, I can't try it).
Comment 3 Manuel Hiebel 2012-06-21 19:46:01 CEST
since I don't understand what is wdtv not sure we can help you..
Comment 4 Tamás Hajdu 2012-06-22 12:48:31 CEST
WD TV is a stream/media player made by Western digital. 

If you can show me for example how to debug nfs at server side I could at least determine the source of the problem.
Comment 6 Tamás Hajdu 2012-07-09 11:45:44 CEST
I have just wanted to finally debug the problem, but it seems the bug is no more present.

Status: UNCONFIRMED => RESOLVED
Resolution: (none) => INVALID


Note You need to log in before you can comment on or make changes to this bug.