Do the routers block any ports or netbios traffic? Did you restrict the samba ports in smb.conf - samba I think listens by default on 137, 138, 139 + 445 . 445 is for SMB-over-ip, which isn't actually used by samba 3.x/ XP machines will try to connect to 445 then redirect to 137-139 for "classic" smb-over-NBT. " Restricting the ports may cause more issues then it solves.
I can't think of anything else that would cause issues with a routed environment. On 08/30/12 11:09, real-men-dont-cl...@gmx.net wrote: > Hi, > > I already tried that, no success. > > The VPN connects two subnets via OpenVPN with dedicated routers on each side. > > > thx > > Carsten > > > > -----Original message----- > To: samba@lists.samba.org; > From: Gaiseric Vandal <gaiseric.van...@gmail.com> > Sent: Thu 30-08-2012 14:58 > Subject: Re: [Samba] join domain from different subnet (VPN) >> Did you try a packet capture on the samba server? >> >> Try adding a entry for the XP machine in the server's /etc/hosts file. >> >> I am guessing there is some sort of weird name resolution issue going on >> with the server. I don't think there is any reason the server should >> need to resolve the name of the client machine but I have had weird >> issues with VPN connections before. >> >> This is a site-to-site VPN? >> >> On 08/30/12 05:34, real-men-dont-cl...@gmx.net wrote: >>> Hello everybody, >>> >>> we have a problem joining a domain from a remote location. >>> >>> The remote location is connected via VPN. Everything is working as >>> exspected >> but joining the samba domain from the remote location does not work. >>> - Server Samba Version is 3.5.10 >>> - Windows Client is XP SP3 >>> - Joining the domain locally works without problems >>> - ping does work in both directions >>> - WINS is running on the local PDC and resolves across VPN (I tested with a >> Linux client using nbmlookup) >>> - the WINS server is configured on the client >>> - NetBIOS over TCP/IP is enabled on the client >>> - Windows on the client firewall is OFF >>> - even adding entries to the client's lmhosts file didn't solve the problem >>> >>> >>> Any suggestions? >>> >>> >>> thx >>> >>> Carsten >> >> -- >> To unsubscribe from this list go to the following URL and read the >> instructions: https://lists.samba.org/mailman/options/samba >> -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba