[Bloat] Windows file sharing broken with RC6 ?

[Bloat] Windows file sharing broken with RC6 ?

[Jim Reisert AD1C]

Now that my new WND3700v2 router is in service with CeroWRT RC6
("Ocean City"), I've been unable to share directories between two
Windows 7 computers.

- I'm *not* using "HomeGroup".  All computers involved are in "Workgroup"

- From my wife's XP laptop, I can do a directory of
\\<her_win7_machine> and see the shared directory, but syncing that
directory with the laptop no longer works (i.e. My Documents)

I share two directories from one of my PCs to the other.  Both are
Windows 7 Pro 64-bit.  I am unable to see \\<computer1> from
<computer2>, and of course, can't see those directories either.

Is there something I need to enable in the CeroWRT software to support this?

Thanks - Jim

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

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

[Robert Bradley]

On Fri, 2011-11-04 at 11:53 -0600, Jim Reisert AD1C wrote:
> - From my wife's XP laptop, I can do a directory of
> \\<her_win7_machine> and see the shared directory, but syncing that
> directory with the laptop no longer works (i.e. My Documents)
> 
> I share two directories from one of my PCs to the other.  Both are
> Windows 7 Pro 64-bit.  I am unable to see \\<computer1> from
> <computer2>, and of course, can't see those directories either.
> 
> Is there something I need to enable in the CeroWRT software to support this?

I may be wrong, but this could be down to Windows Firewall and its
default settings.  These restrict file-sharing to the local subnet.
Unlike most routers, CeroWRT separates wireless and wired connections
into separate subnets to prevent broadcasts from wired systems flooding
the wireless side.  Are the two computers connected to the router in the
same way?

(For reference, the default address ranges are listed at:
http://www.bufferbloat.net/projects/cerowrt/wiki/Default_network_numbering)

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

[Jim Reisert AD1C]

On Fri, Nov 4, 2011 at 4:25 PM, Robert Bradley
<robert.bradley1@gmail.com> wrote:

> I may be wrong, but this could be down to Windows Firewall and its
> default settings.  These restrict file-sharing to the local subnet.
> Unlike most routers, CeroWRT separates wireless and wired connections
> into separate subnets to prevent broadcasts from wired systems flooding
> the wireless side.  Are the two computers connected to the router in the
> same way?

In each pair I described, one is wired and the other is wireless.
I'll have to look into this, thanks!

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

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

[David Täht]

[-- Attachment #1: Type: text/plain, Size: 1875 bytes --]



On 11/04/2011 06:53 PM, Jim Reisert AD1C wrote:
> Now that my new WND3700v2 router is in service with CeroWRT RC6
> ("Ocean City"), I've been unable to share directories between two
> Windows 7 computers.
>
> - I'm *not* using "HomeGroup".  All computers involved are in "Workgroup"
>
> - From my wife's XP laptop, I can do a directory of
> \\<her_win7_machine>  and see the shared directory, but syncing that
> directory with the laptop no longer works (i.e. My Documents)
>
> I share two directories from one of my PCs to the other.  Both are
> Windows 7 Pro 64-bit.  I am unable to see \\<computer1>  from
> <computer2>, and of course, can't see those directories either.
>
> Is there something I need to enable in the CeroWRT software to support this?

I knew this was going to be a problem with the routing split. (another 
issue will be multicast dns)

Like so many other things, I'd like to get this to zero configuration, 
while keeping wireless and wired interfaces separated...

The fix :

1) install wins support with the samba3 package (via:

   opkg update
   opkg install samba3 luci-app-samba

(or install via the web interface)

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.

however I do not know if windows 7 has 'extra' firewalling features in 
re subnets at this point. As an enterprise OS I sure would hope not and 
it's merely the missing wins announcement that is failing you.

start it via

/etc/init.d/samba3 start

Wash, rinse, repeat. When it works...

3) Enable it on boot via the web interface



> Thanks - Jim
>


-- 
Dave Täht


[-- Attachment #2: dave_taht.vcf --]
[-- Type: text/x-vcard, Size: 204 bytes --]

begin:vcard
fn;quoted-printable:Dave T=C3=A4ht
n;quoted-printable:T=C3=A4ht;Dave
email;internet:dave.taht@gmail.com
tel;home:1-239-829-5608
tel;cell:0638645374
x-mozilla-html:FALSE
version:2.1
end:vcard

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

[Jim Reisert AD1C]

> 1) install wins support with the samba3 package (via:
>
>  opkg update
>  opkg install samba3 luci-app-samba

Did this via the ssh interface, seems to have worked OK:

root@OpenWrt:~# opkg install samba3 luci-app-samba
Installing samba3 (3.0.24-7) to root...
Downloading http://huchra.bufferbloat.net/~cero1/cerowrt-wndr3700-1.0rc6/packages/samba3_3.0.24-7_ar71xx.ipk.
Installing luci-app-samba (trunk+svn-1) to root...
Downloading http://huchra.bufferbloat.net/~cero1/cerowrt-wndr3700-1.0rc6/packages/luci-app-samba_trunk+svn-1_ar71xx.ipk.
Configuring samba3.
Configuring luci-app-samba.
root@OpenWrt:~#

> 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.

I'm not sure what to do/change at this step.  What do I change in the
samba (or samba.conf) file?

root@OpenWrt:~# cat /etc/config/samba

config samba
        option 'name'                   'openwrt'
        option 'workgroup'              'openwrt'
        option 'description'    'openwrt'
        option 'homes'                  '1'

config sambashare
        option 'name'                   'tmp'
        option 'path'                   '/tmp'
        option 'read_only'              'no'
        option 'guest_ok'               'no'
        option 'create_mask'    '0700'
        option 'dir_mask'               '0700'
        #option 'users'                 'abc'

My Windows workgroup is called "workgroup"

Thanks - Jim

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

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

[Jim Reisert AD1C]

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

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

[Jim Reisert AD1C]

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



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

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

[Jim Reisert AD1C]

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

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

[Robert Bradley]

On Wed, 2011-11-30 at 00:13 -0700, Jim Reisert AD1C wrote:
> 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.
> 

I'm going to guess that for some reason, the WINS server is not being
advertised by DHCP.  It may not be ideal, but you could try maqnually
configuring the WINS server on each system, pointing it at the router.
At least the firewall issue seems to be sorted for the moment.
-- 
Robert Bradley <robert.bradley1@gmail.com>

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

[Jim Reisert AD1C]

On Wed, Nov 30, 2011 at 6:04 AM, Robert Bradley wrote:

> I'm going to guess that for some reason, the WINS server is not being
> advertised by DHCP.  It may not be ideal, but you could try manually
> configuring the WINS server on each system, pointing it at the router.
> At least the firewall issue seems to be sorted for the moment.

If I can access another computer on the wired network by name, that
means that the WINS server is working, right?  The problem is that I
can't access another computer by name (only by IP address) when it is
on a different subnet.  I've tried manually configuring the WINS
server in Windows 7 and it doesn't make a difference.

These are the contents of my /etc/config/samba file - should be same
as the default:

root@OpenWrt:~# cat /etc/config/samba
config samba
        option 'name'                   'openwrt'
        option 'workgroup'              'openwrt'
        option 'description'            'openwrt'
        option 'homes'                  '1'

config sambashare
        option 'name'                   'tmp'
        option 'path'                   '/tmp'
        option 'read_only'              'no'
        option 'guest_ok'               'no'
        option 'create_mask'            '0700'
        option 'dir_mask'               '0700'
        #option 'users'                 'abc'

- Jim

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

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

[Dave Hart]

On Wed, Nov 30, 2011 at 15:38, Jim Reisert AD1C <jjreisert@alum.mit.edu> wrote:
> If I can access another computer on the wired network by name, that
> means that the WINS server is working, right?  The problem is that I
> can't access another computer by name (only by IP address) when it is
> on a different subnet.

Not necessarily.  I don't have experience with Windows 7, but
generally MS clients have been able to resolve netbios hostnames on
the same subnet via broadcast name resolution even if the WINS server
is sick.  It's only when reaching across subnets that WINS is
essential in providing the flat namespace.

Cheers,
Dave Hart

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

[Robert Bradley]

On Wed, 2011-11-30 at 08:38 -0700, Jim Reisert AD1C wrote:
> If I can access another computer on the wired network by name, that
> means that the WINS server is working, right?  The problem is that I
> can't access another computer by name (only by IP address) when it is
> on a different subnet.

On the same subnet, you can resolve addresses through NBT broadcasting
and/or mDNS.

> I've tried manually configuring the WINS
> server in Windows 7 and it doesn't make a difference.

That's more interesting, since that ought to work!

I think you need to set /etc/config/samba to:

----
config samba
        option 'name'                   'openwrt'
        option 'workgroup'              'WORKGROUP'
        option 'description'            'openwrt'
        option 'homes'                  '1'

config sambashare
        option 'name'                   'tmp'
        option 'path'                   '/tmp'
        option 'read_only'              'no'
        option 'guest_ok'               'no'
        option 'create_mask'            '0700'
        option 'dir_mask'               '0700'
        #option 'users'                 'abc'
----

Next, modify "/etc/samba/smb.conf.template" directly and add:
	wins support = yes
to enable the WINS server, restart Samba on the router, then restart all
the computers.
-- 
Robert Bradley <robert.bradley1@gmail.com>

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

[Jim Reisert AD1C]

Thanks for the suggestions.  I'll try these (and the earlier ones)
when I get home tonight.

On Wed, Nov 30, 2011 at 9:01 AM, Robert Bradley wrote:

> I think you need to set /etc/config/samba to:
>
> ----
> config samba
>        option 'name'                   'openwrt'
>        option 'workgroup'              'WORKGROUP'
>        option 'description'            'openwrt'
>        option 'homes'                  '1'

Why would I make this change? I have already modified all the Windows
computers to be in the "OPENWRT" workgroup.  I can see making this
change if they were still (or needed to be) in the "WORKGROUP"
workgroup, which is probably what I ultimately want.

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

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

[Robert Bradley]

[-- Attachment #1: Type: text/plain, Size: 982 bytes --]

On 30 November 2011 18:37, Jim Reisert AD1C <jjreisert@alum.mit.edu> wrote:

> Thanks for the suggestions.  I'll try these (and the earlier ones)
> when I get home tonight.
>
> On Wed, Nov 30, 2011 at 9:01 AM, Robert Bradley wrote:
>
> > I think you need to set /etc/config/samba to:
> >
> > ----
> > config samba
> >        option 'name'                   'openwrt'
> >        option 'workgroup'              'WORKGROUP'
> >        option 'description'            'openwrt'
> >        option 'homes'                  '1'
>
> Why would I make this change? I have already modified all the Windows
> computers to be in the "OPENWRT" workgroup.  I can see making this
> change if they were still (or needed to be) in the "WORKGROUP"
> workgroup, which is probably what I ultimately want.
>
>
Sorry about that!  I thought the computers were still in "WORKGROUP".  With
all the computers now in the "OPENWRT" workgroup, you can ignore this.
--
Robert Bradley <robert.bradley1@gmail.com>

[-- Attachment #2: Type: text/html, Size: 1676 bytes --]

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

[David Täht]

On 11/30/2011 02:04 PM, Robert Bradley wrote:
> On Wed, 2011-11-30 at 00:13 -0700, Jim Reisert AD1C wrote:
>> 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.
>>
> 
> I'm going to guess that for some reason, the WINS server is not being
> advertised by DHCP.  It may not be ideal, but you could try maqnually
> configuring the WINS server on each system, pointing it at the router.
> At least the firewall issue seems to be sorted for the moment.

Your diagnosis might be correct.

There are not one, but two errors in the present /etc/config/dhcp file

config 'dhcp' 'sw00'
        option interface        'sw00'
        option start    2
        option limit    26
        list 'dhcp_option' '42,0.0.0.0'
        option leasetime        24h
        option domain   'home.lan'

The dhcp options for supplying WINS are not set. It's
not clear to me if you need to set all or merely some of these,
but adding to each interface configuration section:      

list 'dhcp_option' '48,0.0.0.0'

Seems like a good bet.

And MAYBE:

list 'dhcp_option' '19,1'

I simply don't know if setting these is useful too.

#dhcp-option=45,0.0.0.0     # netbios datagram distribution server
#dhcp-option=46,8           # netbios node type


For more details on how dnsmasq works, see:

http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq.conf.example


# The following DHCP options set up dnsmasq in the same way as is specified
# for the ISC dhcpcd in
# http://www.samba.org/samba/ftp/docs/textdocs/DHCP-Server-Configuration.txt
# adapted for a typical dnsmasq installation where the host running
# dnsmasq is also the host running samba.
# you may want to uncomment some or all of them if you use
# Windows clients and Samba.
#dhcp-option=19,0           # option ip-forwarding off
#dhcp-option=44,0.0.0.0     # set netbios-over-TCP/IP nameserver(s) aka WINS server(s)
#dhcp-option=45,0.0.0.0     # netbios datagram distribution server
#dhcp-option=46,8           # netbios node type


The second, is that it is not supplying a ntp server to the se00
network, this is not related to the wins problem.


-- 
Dave Täht

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

[David Täht]

On 11/30/2011 04:57 PM, David Täht wrote:
> On 11/30/2011 02:04 PM, Robert Bradley wrote:
>> On Wed, 2011-11-30 at 00:13 -0700, Jim Reisert AD1C wrote:
>>> 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.
>>>
>>
>> I'm going to guess that for some reason, the WINS server is not being
>> advertised by DHCP.  It may not be ideal, but you could try maqnually
>> configuring the WINS server on each system, pointing it at the router.
>> At least the firewall issue seems to be sorted for the moment.
> 
> Your diagnosis might be correct.
> 
> There are not one, but two errors in the present /etc/config/dhcp file
> 
> config 'dhcp' 'sw00'
>         option interface        'sw00'
>         option start    2
>         option limit    26
>         list 'dhcp_option' '42,0.0.0.0'
>         option leasetime        24h
>         option domain   'home.lan'
> 
> The dhcp options for supplying WINS are not set. It's
> not clear to me if you need to set all or merely some of these,
> but adding to each interface configuration section:      
> 
> list 'dhcp_option' '48,0.0.0.0'

agh, I just typoed that. I meant 44,0.0.0.0.


-- 
Dave Täht