openvpn and samba, can't browse shares

[tingon]

Hi all i'm new here, i hope someone can help me..

i've openvpn installed and working on ipcop (zerina module)
i can connect to vpn, ping all ip of the lan i've a samba server ip 192.168.0.170 (ubuntu 9.04)
i can ftp to it, but i can't access at the shares from winxp, but i can reach the shares correctly from my MacOsx

tnx in advance

[Douglas]

Hi all i'm new here, i hope someone can help me..

i've openvpn installed and working on ipcop (zerina module)
i can connect to vpn, ping all ip of the lan i've a samba server ip 192.168.0.170 (ubuntu 9.04)
i can ftp to it, but i can't access at the shares from winxp, but i can reach the shares correctly from my MacOsx

tnx in advance

That sounds more like a Windows problem then a OpenVPN problem, but I'll let the experts here get back to you on it.

[tingon]

i make more tests and i find that

with IP "\\192.168.0.170\shared_folder" works correctly
but don't work with \\domain_name\shared_folder

at least is enough for my needs....

so i think is something on samba configuration

thanks

[ecrist]

You will want to explore setting up a WINS server. Samba has the ability to do this, properly configured.

[george]

We have multiple samba, and windows shares in our environment, and the only issues we've came across since deploying OpenVPN have to do with either the UNC path used to access the share, or the client computer's ability to route to the share.

The UNC issue is fixed by using the FQDN of the server in the UNC path, ie. \\server.domainname.com\sharename when accessing shares from client computers, the client routing problem was fixed by pushing routes for our other subnets to clients that require access to shares on other subnets, (the issue was originally caused by sloppy research).

Hope this sheds some light.