1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Is it my NSLU2 or something else?

Discussion in 'Cisco/Linksys Network Storage Devices' started by DeeJ07, Dec 29, 2004.

  1. DeeJ07

    DeeJ07 Network Guru Member

    Okay, I'll be doubling posting this threat (sorry) because I just don't know what the problem is. Let's start from front to back to describe my network. At the helm is the WRT54G running Satori-4.0 v2.7.17sv. From there my roommate's PC breaks off and a physical link to a SMZ switch in my room. Off the switch I have a WAP54G running MustDie 2.7r1, my PC, and the NSLU2. Here's my problem. My PC is able to access the NSLU2 no problem. But, my Notebook is another story. When the notebook is running off of a cabled connection in my room there is no problem. When I run off of the WAP54G there is no problem. However, I HAD the WAP54G running as a repeater. The problem was that it seems to not have been working too well and I was just connecting to the WRT54G on the other side of the house. Anyway, with the notebook running through the WRT54G I was not able to access the NSLU2 via file sharing, only the HTTP interface. By switching the WAP54G to AP mode and connecting through that I solved the problem. What gives? I wanted to be able to have the expanded range by adding the AP as a repeater. I will have to get into my roommate's room to do some more testing. Any ideas, lemme know.

    Edit: Some research on this site offered an answer. Disabled loopback under the administration setting on the WRT54G. Any idea what that's all about?
  2. Disman_ca

    Disman_ca Super Moderator Staff Member Member

    Loopback enabled causes the network browsing to not function as documented in the "more" section of the administration page. You should be able to get things working for unc paths if you enable DNS Masq and Local DNS on the adminstration page.

    From the help page:

Share This Page