You don't need a WINS server (Samba or NT/2K) on both ends, just at one end. If you can set up your DHCP server (assuming you're using one) to give out the WINS address, all the better, because then all the machines will eventually get the correct config without touching any of them. You can use Samba as a WINS server or just as a WINS client (as all your other clients should be configured).
This is the classic problem of locating AND browsing across TCP/IP segments that don't forward the NetBIOS broadcasts (as most don't). WINS helps with the locating of resources as well as keeping up with the browse lists. Avoid lmhosts files, if possible, as they're like hosts files... just as DNS is a much better solution for locating hosts because it's less configuration mess, WINS is a much better solution for locating NetBIOS resources. If you have any questions, I'll be happy to help if I can. By the way, there are many good tools (browstat, browmon, etc.) in the NT resource kit for monitoring browsing, but you probably don't need them. -Blanton > > > 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. I also > > > found that having one of the Samba boxes do WINS serving > > helped... I > > > never needed the lmhosts or hosts files on the > > workstations. However, > > > if you don't have Samba, you can map resources by IP > > without issue. I _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
