|
|
David Mir <mir@xxxxxxxxxxxx> said: > > In what version was this added? I tried it and even though it is listed in > the --help it says that it is not implemented yet. --ip-win32 dynamic was added in 1.6.0 (and is also the default in 1.6.0). If you try it in 1.5.0 you will get a message that it's not implemented yet. > On Wednesday 12 May 2004 02:42 pm, James Yonan wrote: > > jeremy@xxxxxxxxxxxxxxx said: > > > I was just debugging this same problem a couple of days ago. > > > You are right that the second IP address assigned to your TAP > > > adapter is a problem. I had the same issues where generally the > > > VPN tunnel worked fine, but windows shares were broken. > > > > > > My fix was to add "ip-win32 manual" to my configuration file on > > > the windows side. Then, go into the Network Properties for the > > > Tap adapter, turn off DHCP, and manually configure the IP endpoint > > > for the adapter (10.2.0.2 in your case). > > > > > > I don't think this is the best solution. Does anyone know what is? > > > The problem seems to go like this... Windows set the IP endpoint > > > correctly and then some seconds later these second IP addresses get set. > > > Mine was a default windows dhcp address of 169.x.x.x. > > > > > > Maybe the dynamic option to ip-win32 works... haven't tried it yet. > > > > Yes, "ip-win32 dynamic" is the solution to this problem of dual addresses > > being assigned to the TAP adapter. > > > > James > > -- > David Mir > Systems Administrator > Soar Technology, Inc. > 3600 Green Ct. Ste 600 > Ann Arbor, MI 48105-2588 > 734-327-8000 ext. 222 > 734-913-8537 (Fax) > www.soartech.com > mir@xxxxxxxxxxxx > Mobile Text (160 chars max): > mir_mobile@xxxxxxxxxxxx > -- |