[ previous ] [ next ] [ threads ]
 From:  "Jason Brunk" <jbrunk at wthosting dot com>
 To:  <pacneil at linuxgeek dot net>, <m0n0wall at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall] ipsec tunnel network neighborhood
 Date:  Thu, 28 Apr 2005 20:45:29 -0400
Even with a wins server?   I thought having the wins server overrides the
need of having a master browser?  Most of the articles I have found said
this to be the case.  I know back in win98 we used to point to a public wins
server online and my buddies and I would share files that way, just doesn't
seem to be the case now a day.


-----Original Message-----
From: Neil Schneider [mailto:pacneil at linuxgeek dot net] 
Sent: Thursday, April 28, 2005 2:19 PM
To: m0n0wall at lists dot m0n0 dot ch
Subject: Re: [m0n0wall] ipsec tunnel network neighborhood

Jason Brunk said:
> I am working to get mono wall setup for a client of mine and his
> branch
> office.  So far the tunnel is working great, I have a wins server
> running on
> one side and every machine on both networks is registering with it.
> Name
> resolution works and everything pings fine.  But network neighborhood
> browsing only shows machines on that side of the network.  Anyone know
> why
> the workstations wouldn't be showing the rest of the machines
> registered in
> wins?

Windows won't do cross-subnet browsing without a master browser on the
subnet that knows about all the hosts on the other side. This probably
should be in the FAQs if it isn't already. Network neighborhood uses
broadcast packets and broadcast packets don't cross network

Neil Schneider                              pacneil_at_linuxgeek_dot_net
Key fingerprint = 67F0 E493 FCC0 0A8C 769B  8209 32D7 1DB1 8460 C47D
Sometimes I wonder whether the world is being run by smart people who
are putting us on, or by imbeciles who really mean it - Mark Twain

To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch