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

[Massimiliano Hofer <max@xxxxxxxxxx>]

Alle 2:21 PM, domenica 7 dicembre 2003, Jordi Sanfeliu ha scritto:

> 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.

I had the same problem: samba not working, other IP services working and wrong 
IP on the tun device (I wasn't bridging).
In my case an "ipconfig" revealed a second (and wrong) IP associated to the 
tun device (it doesn't show immediately, it appears magically after a few 
seconds).
I think that normal connections (telnet, POP3, etc.) use the "nearest" IP (the 
primary one for the first device where the connection will be routed), while 
SMB somhow chooses differently and uses the spurious one.

I resolved the problema adding "ip-win32 manual" to the configuration and 
manually configuring the IP, but I think it's a bug of the Win32 
implementation.

Another problem I had is that the "route" option always fails if applied 
without a dalay (interface not ready) and that the interface never comes 
alive if I don't send packets to it (even if I use the "ping" option).

My temporary solution was to add "delay-route 1" and an up script that pings 
the peer.

-- 
Saluti,
   Massimiliano Hofer
        Nucleus

Attachment: pgpKBKajrc0zk.pgp
Description: signature