Re: [Openvpn-users] Linux(server) <-> W2K(client) all working fine except Samba

[Jordi Sanfeliu <Jordi.Sanfeliu@xxxxxxxxxxxx>]

James Yonan wrote:
> Jordi,
>
> I've heard about this problem before (everything working except samba), and I
> haven't really been able to reproduce it.  For me everything works including
> samba.  If I were troubleshooting something like this I would try a few things
> in this order:
>
> (1) run tcpdump/WinDump on the tap interface and make sure that samba neighbor
> discovery broadcasts are correctly transiting the VPN.

Using tcpdump on the Linux side I see something strange. I dont know why the w2k
have the IP 169.254.74.152. Executing "route print" in the w2k as a command line
I get all the routing table that includes this strange IP.

This IP only appears when the tunnel is activated and pinged from the linux
server. It is always exactly the same.

> (2) Make sure that your samba configuration is correct.  If you are bridging
> ethernet interfaces on the linux server, then the samba config probably
> doesn't need to be modified.  However, if you are creating a new interface
> which uses a different subnet than the primary physical ethernet which samba
> is listening on, then you need to upgrade your samba config to a multi-subnet
> configuration, which requires setting up a WINS server, and setting up windows
> clients to point to this server.

I'm bridging, so from the samba point of view nothing is treated specially in
the LAN.


It seems does not is a samba problem, because if I telnet to w2k with 139 port
"telnet w2k 139" I get the same message (connection refused). So this makes me
think it may be a tap-win32 problem.

More tests. In this case, if I type "telnet localhost 139" from the w2k
command-line, I get the same "connection refused" message!!!!!!!!!.

But!, if I type "telnet 192.168.0.27 139" from the w2k command line, it works!!.

Remember that the 192.168.0.27 is the IP of it's physical ethernet adapter.


> If you figure it out, please post your solution to the list.

sure.


--
Jordi Sanfeliu
FIBRANET Network Services Provider
http://www.fibranet.com