"Michael D. Schleif" wrote: > > Brock Nanson wrote: > > > > The catch to all this is browse lists. Unless you are running Samba > > boxes on *both* ends of the VPN doing browse list synchronization, you > > won't see the machines in both LAN's in Network Neighborhood.
[snip] > > But the local browse broadcasts aren't > > routable and hence, won't find their way onto the other subnet. You might do well to reread the part I left in, because he's telling you what to expect. Your broadcasts aren't routable, that's why you can't browse unless you run two wins servers and have them communicate. Or Samba. I don't know all the garbage that ms has nowadays for 2k that might crowbar in browsing. > What do you mean, ``able to cut/paste at will''? > > What about shares? If we cannot browse to the other side with explorer, > how do we map shares? Manually, by knowing the name/address and share > name? Yes, you map using the name/address and share name, even though you can't browse, assuming you're not blocking those 13x ports. That's what all those script kiddies do when they try to connect to your shares. They run the "net use" command on Windows. Try this: net /? Good Luck, Matthew _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
