Re: [Bloat] Windows file sharing broken with RC6 ?

[Jim Reisert AD1C <jjreisert@alum.mit.edu>]

It may not be as dire as I originally thought.

On the two wired computers running Windows 7, in Windows Explorer I
can see all the nodes on the system - themselves, OPENWRT (and its tmp
directory) and the Windows 7 computer on the wireless network.
However, I can't connect from the wired subnet to the wireless subnet
by name:

  Windows can not access \\wirelesscomputer

But Windows can get to it via its IP address:

  \\172.30.42.69

On the wireless computer, the only node I see is itself - I don't even
see OPENWRT, and certainly don't see the computers on the wired
subnet.

- Jim


On Tue, Nov 29, 2011 at 11:51 PM, Jim Reisert AD1C
<jjreisert@alum.mit.edu> wrote:

> I was close, but I then pushed my luck too far.
>
> Since the "openwrt" workgroup appeared to be working, I thought I
> would name the "openwrt" workgroup back to "workgroup" (by editing
> /etc/config/samba), to be compatible with the other computers in the
> house.  In other words, I could swap my old router back in if needed,
> and the local networking would still work (they wouldn't rely on an
> openwrt master).  That was a mistake, I now couldn't set the first
> computer to "workgroup" because it said there was another "workgroup"
> already on the network (maybe my wife's computer, which hadn't been
> re-configured for openwrt).  So I modified /etc/config/samba to use
> "openwrt" again.  I shut down all the computers in the house, as well
> as the router.  I rebooted the router and waited.  Then I rebooted my
> PC which was previously working.
>
> I can see my own node in the Windows network but I no longer see the
> "openwrt" node.  The wireless computer only sees itself, and the two
> wired computers only see each other.  They no longer see the computers
> on the other subnet (wired to wireless, and vice-versa).  I do see the
> samba processes running on the router, so I have no idea what I broke.
>
> Very frustrating!
>
> - Jim
>
> On Tue, Nov 29, 2011 at 9:35 PM, Jim Reisert AD1C
> <jjreisert@alum.mit.edu> wrote:
>> I'm so close, see below:
>>
>>
>> On Sat, Nov 5, 2011 at 2:51 AM, David Täht wrote:
>>
>>> 1) install wins support with the samba3 package (via:
>>>
>>>  opkg update
>>>  opkg install samba3 luci-app-samba
>>>
>>> (or install via the web interface)
>>
>> Done.
>>
>>> 2) configure it to be in the workgroup and announce on the subnets. It
>>> should then become the    'master' browser for that domain.
>>>
>>> While I recall this setup as straightforward (edit either /etc/config/samba
>>> and/or /etc/samba/smb.conf.template) and used it to share a flash disk
>>> across a XP/Vista network as well as printers, that was waaaay back in may.
>>
>> Done.  I left the default network name as 'openwrt'.
>>
>>> start it via
>>>
>>> /etc/init.d/samba3 start
>>
>> Done.
>>
>>> 3) Enable it on boot via the web interface
>>
>> Done.
>>
>> I put two Windows 7 computers into the OPENWRT workgroup - one on the
>> wired LAN, one on the wireless LAN.  Both have their WINS
>> configuration set to "NetBIOS over TCP/IP".  Both have been rebooted.
>>
>> On both computers, The network contains three nodes:
>>
>> - AD1C (wireless)
>> - JJR (wired)
>> - OPENWRT (router)
>>
>> I browse OPENWRT and see the tmp folder.  However, when I try to
>> browse \\JJR (from AD1C) or \\AD1C (from JJR), Windows 7 says "Windows
>> can not access \\<HOST>"
>>
>> You also suggested I try browsing by IP address:
>>
>>  \\the.ip.add.ress\sharename
>>
>> That actually WORKS!  So why does the IP address work, but the NAME
>> (ie. JJR or AD1C) does not?
>>
>>
>> Note that there is another computer on the wired network, it's still
>> int the "WORKGROUP" workgroup, and it does *not* show up as a node on
>> the network.  This is what I expected, is that what you expect?

-- 
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us