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...
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany [email protected]
fax: +49-89-35655025 [email protected]
