<div>IMHO, sounds more like a network issue than a server issue. The first thing I would do is look for source of interference. Microwaves, cordless phones, neighbor's wifi, etc. Then, I'd try changing the channel on the WAP. WIthout a spectrum analyzer, it becomes a case of trial and error. <br>
<br></div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Message: 5<br>Date: Sun, 30 Aug 2009 22:00:30 -0400<br>From: William Witt <<a href="mailto:william@witt-family.net">william@witt-family.net</a>><br>
Subject: [ale] NFS over wireless<br>To: <a href="mailto:ale@ale.org">ale@ale.org</a><br>Message-ID: <<a href="mailto:4A9B2EBE.6000708@witt-family.net">4A9B2EBE.6000708@witt-family.net</a>><br>Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>The setup:<br>I have an old laptop(+ a 500GB hd) acting as an NFS file server and uPnP<br>media server for my xbox360 connected via CAT5 and running<br>ubuntu-server. I have two machines (mine and my wifes) plus the xbox<br>
connected wirelessly. My wife machine runs linuxMint and mine is<br>currently running Fedora 11.<br><br>The problem:<br>When either of us is copying large files (typically 1-2 GB movies) to<br>the file server, my wife's desktop and any nautilus windows will freeze<br>
and sometimes crash. I know it has to do with the NFS server because<br>when this happens "dmesg | tail" yeilds:<br><br>[ 2109.988015] nfs: server smeagol not responding, timed out<br>[ 2111.488016] nfs: server smeagol not responding, timed out<br>
[ 2112.988020] nfs: server smeagol not responding, timed out<br>[ 2114.488016] nfs: server smeagol not responding, timed out<br>[ 2115.988014] nfs: server smeagol not responding, timed out<br>[ 2117.488015] nfs: server smeagol not responding, timed out<br>
[ 2118.988020] nfs: server smeagol not responding, timed out<br>[ 2120.488016] nfs: server smeagol not responding, timed out<br>[ 2121.988023] nfs: server smeagol not responding, timed out<br>[ 2164.731019] nfs: server smeagol not responding, timed out<br>
<br>There is still enough available bandwidth on the wireless connection to<br>surf the web and do email. And on her machine, everything but nautilus<br>works fine as long as there are no gnome file dialogs involved. My<br>
machine doesn't even hiccup, except for taking a long time to do an ls<br>on the nfs mount point. I did see the same problem on my machine under<br>linuxMint and Ubuntu, but not under Suse or Fedora.<br><br>The Question:<br>
My wife is opposed to me doing much to her machine that will impact her<br>work flow, so putting her on Suse or Fedora is out of the question. I<br>don't own the house or I'd just run cat5 to her box. Is there a better<br>
way to tune NFS over wireless networks that will eliminate this problem<br>on ubuntu based boxen? Am I baking up the wrong tree with NFS over<br>wireless in the first place? If so, what should I be using?<br><br>On a side note, there seems to be something in our flooring that causes<br>
A LOT of loos between the second and first floor. I wonder if there is<br>some sort of anti static conductive coating on the laminate flooring<br>that the owners put down.<br><br>Will<br><br></blockquote></div>