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

Network visability / WRT54GL / Tomato 1.23

Discussion in 'Tomato Firmware' started by rburns, Jan 24, 2009.

  1. rburns

    rburns Addicted to LI Member

    Newb question -

    I have the WRT54GL with Tomato on a small home network. I generally use the XP x32 laptop wired to the network and can share resources (sometimes even this is screwy*). Using wireless, I can only access the web and not shared resources. What do I need to do differently? I imagine that it's a simple solution, but I don't speak networkese.

    Thanks, Ralph

    * screwy means that sometimes I can see resources and sometimes not. For example I just rebuilt the laptop and can see across the wired network to a shared drive on a XPx64 desktop under "my network places", but cannot see the desktop or attached (shared) printer (i.e. under Microsoft Windows Network).
  2. Eiríkr

    Eiríkr Addicted to LI Member

    Network browsing in CIFS (Microsoft's sharing protocol) can be flaky sometimes. I combatted some of these issues for a while to get Samba sharing up and running. It wouldn't surprise me at all if some obscure and minor difference in implementation between XPx32 and XPx64 was screwing something up.

    So a question for you -- even when you cannot browse to shared MS Windows Network resources, can you still access them directly? For a long time in Samba I had a similar situation, where I could not browse to shared resources via the Windows Network, but I could open them directly in Explorer by typing \\COMPUTERNAME\Shared Folder Name\ into the address bar.


    -- Eiríkr
  3. rburns

    rburns Addicted to LI Member

    Hello, thanks for the reply.

    To answer your question, yes. When I cannot browse to shared network resources, then I can still make direct access.

    I also found that to restore the capability to browse to shared network resources, I take the share computer off the workgroup and then add it back in again, so that is my short-term solution for the *screwy note above. But that only resolves the wired network connection.
  4. Eiríkr

    Eiríkr Addicted to LI Member

    Reading over on the Ubuntu forums, it sounds suspiciously like MS might have borked sharing settings yet again. This thread is one example.

    I'm sure there's a workaround, but it will likely involve digging around in your sharing settings. A few questions to start bug-hunting: Are all machines on your network WinXP? Are all the sharing machines members of the same workgroup? How many machines are there in that workgroup? I'm sure there are more relevant questions, but ironically I'm more familiar with Samba's config options than I am with how MS sharing itself does business.


    -- Eiríkr
  5. rburns

    rburns Addicted to LI Member


    There are two machines in this workgroup, plus one ReadyNAS and a working wifi Squeezebox Duet. They share the same workgroup. The laptop is XPx32 and the wired-only desktop is XPx64. What else would be helpful to know?
  6. mstombs

    mstombs Network Guru Member

    In Tomato may be worth checking/experiments with "Nat Loopback", there was an issue with this that the default "forwarded only" setting was designed to fix.

Share This Page