|
|
I think the dance is something like that: (or why i'm not a broadcast-slave partner, or even: the half of the hosts available in Network Neighborhood are just your imagination and try to use a share and you'll see what i'm talking about). Suppose you have 2 WINS servers: one in each subnet. Both are connected with their duplicating partners facilities (all Win2kServer version around here are pt_BR locale, so, translate it, please). SAMBA has a lot of ressources to get connected to it's subnet and to other WINS servers: remote announce, domain master, name resolv order, and many more. The "wins server" parameter is first used instead of broadcast - you can check yourserlf disconnecting for few moments the wins server and trying to use some "new" share. Broadcast also plays it's role: this is why we can use a share without a wins server in a given subnet. So, suppose you want to print a doc in Brazil from England trough OpenVPN: Your client connects to the WINS server in the subnet you are (usually). The wins server in the same subnet range of your host has his "copy" of lmhosts, with some entries given by the remote wins server, and the share map is done. Printing to \\veryremotehost\veryremoteprinter1 is possible, and a cross-subnet browsing stuff finally works! This is just a simplistic remote-browse-sync explanation: don't get it too seriously. I'm sure you'll have much more fun at http://us1.samba.org/samba/docs/ HTH, RSalles John Locke disse: > > > On Wed, 2004-03-03 at 10:41, vklengh wrote: >> Why a WINS server if I can allow broadcasts even with routing? >> Don't the netbios clients ask for servers with service broadcasts? >> WINS would be only needed if you deny broadcasts to the specific subnet, >> isn't so? > > Well, I'm not sure how you would allow broadcasts with routing. > Broadcasts are (usually) limited to the subnet. A WINS server is the > common way to get Windows networking to work across subnets. (And if you > have a Linux computer with Samba available, it's really easy...) > > If you set up a bridged configuration, then broadcasts work fine--your > remote computer essentially is bridged to be in the same subnet as your > other computers. > > If somebody can explain how to route broadcasts, that sounds > interesting, but I'm not sure it's the best way to solve the problem... > > Cheers, > -- > John Locke > Open Source solutions for small business problems > http://freelock.com > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Openvpn-users mailing list > Openvpn-users@xxxxxxxxxxxxxxxxxxxxx > https://lists.sourceforge.net/lists/listinfo/openvpn-users > -- "A well-written program is its own heaven; a poorly-written program is its own hell." TAO of Programming - Book 4 ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |