Henry,

Thanks for the tip. 

It looks like when I upgraded from Server 2K3 and 2K8 that the upgrade process just destroyed my TAP-Win32 adapter.

First I tried installing the TAP-Win32 driver manually using the device manager. This created the TAP-Win32 adapter in Windows, but said it was "disconnected" in the network control panel. I tried setting the "Media Status" to "Always Connected", which changed the status to "Limited Connectivity", but I don't think this is the same thing as "Host-only" operation.

I then tried turning on MS's Internet Connection Sharing (ICS), but it failed with no useful error message. I think the problem is that I'm not able to get the TAP-Win32 adapter into Host-only mode and Windows doesn't think the interface is properly connected to anything.

I removed that TAP-Win32 interface with the device manager.

Then I downloaded the latest stable coLinux installer and ran that, but it never asked me about networking--just told me that I need Winpcap for bridged networking--which I don't need.

I then tried turning on MS's Internet Connection Sharing (ICS), but it failed with no useful error message. I think the problem is that I'm not able to get the TAP-Win32 adapter into Host-only mode.

Any thoughts?

Thanks,

Paul

On Fri, Jun 3, 2011 at 6:53 PM, Henry Nestler <henry.ne@arcor.de> wrote:
Hello Paul,

On 04.06.2011 01:39, Paul Ericson wrote:
> Anyone seen this?
>
> What's the best solution?
>
> I figure its either a hidden adapter and could be unhidden or I've got
> to re-install the TAP adapter.
>
> This is 32-bit BTW.

Try the command line tool in directory "netdriver".

A good help will find in the Wiki:
http://colinux.wikia.com/wiki/TAP-Win32_driver

--
Henry N.