Gert Doering wrote:
Hi,
On Wed, Jun 23, 2010 at 09:10:10AM +0200, Jan Just Keijser wrote:
assigns a 169.254 address. If this works for you as well then maybe the
tap-win32 developers can dive deeper into this and find out why windows
treats the 'always connected' adapter differently from an 'application
controlled' adapter .
I'd assume that windows services are not "bound" to "dynamic" interfaces...
They're not , as far as I know.
However,
- the SMBoverIP service binds to 0.0.0.0:445 yet it refuses access from
IPs other than the 'always connected' ones
- as Henno found out, disabling and then enabling the "windows file
sharing" protocol on the TAP-win32 adapter after the connection has been
established fixes the problem ; I don't know if it is possible to do
this using some 'netsh' magic, however
- the same thing works on windows 2000, no modifications
- on windows XP and higher it *does* work for PPTP/L2TP+IPsec VPNs
JJK
