|
|
Thank you for your response. It was also my understanding that I would be able to have a shared workgroup among the different end points of the VPN connection. Where my confusion lies is that for whatever reason I am unable to register the machine with the WINS server. When I connect to the Samba server and mount a shared resource I appear in the smbstatus output as connected with my proper IP address, 192.168.1.111, the samba server is 192.168.0.197. Also, I can access all resources of the LAN at the other end of the VPN and perform tasks such as adding printers, etc ... . However, when I look at the logs on the Samba server machine I see that a connection from 10.3.0.2, the IP address of the VPN endpoint on the win2000 client, is being denied, and also a connection from 0.0.0.0 is being denied as well. As an attempt I allowed the connection from 10.3.0.2 as an allowed host in my smb.conf and the error message was no longer there, but after that my connection to the samba server was being logged as coming from 10.3.0.2 instead of my actual IP of 192.168.1.111. The change in the smb.conf had no other effect and shortly thereafter I removed the 10.3.0.2 from hosts allow Also, I have another VPN setup, although this one runs between two Linux gateways, and the windows machines in the remote location can register themselves with the same Samba/WINS server (192.168.0.197), although I cannot see them in the network neighbourhood either and weird things occur on the WinXP machines, but that is another problem. I am just unsure where to begin looking to see what may or may not be blocking my 192.168.1.111 machine from registering with the WINS server. Thank you for any further insight Michael Kelly >>> Jaye Mathisen <mrcpu@xxxxxxxxxxxxxxx> 05/08/2004 6:26:27 pm >>> 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 ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |