Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Sat, Aug 25, 2012 at 11:25 AM, Jerry Feldman <gaf at blu.org> wrote: > [long complicated description of a network problem] > > In any case I'm looking for some ideas. First of all, I'm going to give the generic response that I give whenever a networking problem occurs. Run tcpdump, ethereal, whatever, on one (or preferably both) ends of the problematic connection and see what packets are actually being sent/received. I have found that comparing what I see in a broken connection to a working connection usually makes it much easier to figure out where I got the configuration wrong. Now for a specific suggestion. I've seen low cost appliance vendors place arbitrary restrictions on their hardware in order to avoid competing with "enterprise" products. Is it possible that the ReadyNAS box has some kind of artificial restriction that it will only talk to the local subnet? Good Luck, Bill Bogstad
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |