|
|
This is not entirely accurate. IF everything was bridged, you wouldn't necessarily even need a WINS server. WINS is useful for centralizing the collection of name/IP mappings for workgroups and domains across different subnets, as well as a single. It serves additional info, such as PDC location and such when using older NT networks, and finding the PDC and such. It's not needed anywhere near as much in a win2k network, especially if you use AD. There is no reason to have to bridge these networks, proper setup of a WINS server should take care of it. Via Samba or a windows server. On Thu, Aug 05, 2004 at 09:11:00PM -0400, Doug Lytle wrote: > Michael, > > The purpose of a WINS is to be able to resolve host names to IP > addresses, nothing else. It won't help you show up in the Network > Neighborhood. The only way you'll be able to do this is by bridging the > networks. > > Doug > > Michael Kelly wrote: > > > > >I have read through tons of e-mails from this list and tried many fixes > >to solve this. From what I have read having a shared workgroup between > >the office and remote locations is very possible by the use of a WINS > >server. > > > > > > > > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by OSTG. Have you noticed the changes on > Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, > one more big change to announce. We are now OSTG- Open Source Technology > Group. Come see the changes on the new OSTG site. www.ostg.com > _______________________________________________ > Openvpn-users mailing list > Openvpn-users@xxxxxxxxxxxxxxxxxxxxx > https://lists.sourceforge.net/lists/listinfo/openvpn-users > > > !DSPAM:4112dc5e779831464613122! > ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |