Re: [coLinux-users] Lost TAP adapter after upgrade to Server 2008

[Henry N. <hen...@ar...>]

Driver conectivity "Always Connected", ICS, bridging and ip adresses are
not your problem here.

Ok. the TAP-Win32 driver is working, and rightly installed.
I think the network device was renamed by udev.

Please run "cat /proc/net/dev". If you see there eth1 or eth2, then read
the help in wiki to disable udev on the coLinux network adapter:
http://colinux.wikia.com/wiki/Wubi#udev:_renamed_network_interface_eth0_to_eth2

Henry



On 07.06.2011 02:23, Paul Ericson wrote:
> Here's what I did:
>
> Used only the command line tool.
> Removed the current tap driver,
> Rebooted Windows
> Ran regedit and searched for all TAP-Win32 entries and removed them all.
> Rebooted Windows again.
>
> Logged in as "Administrator" and ran the cmd.exe with "Run as ... Admin".
>
> Then installed the tap-win32 from command line with:
> tapcontrol.exe install OemWin2k.inf TAP0801co
> Received:
> "Device node created. Install is complete when drivers are updated...
> Updating drivers for TAP0801co from c:\Program
> Files\coLinux\netdriver\OemWin2k.inf.
> Drivers updated successfully."
> "Remember, that you should see a Warning about "not signed"
> driver."--Got this warning, chose to install anyway.
>
> and checked the driver with:
>
> tapcontrol.exe hwids TAP0801co
>
> Received:
> "ROOT\NET\0000
>     Name: TAP-Win32 Adapter V8 (coLinux)
>     Hardware ID's:
>         TAP0801co
> 1 matching device(s) found."
> ipconfig shows:
> Windows IP Configuration
> Ethernet adapter Local Area Connection 2:
>    Media State . . . . . . . . . . . : Media disconnected
>    Connection-specific DNS Suffix  . :
> Ethernet adapter Local Area Connection:
>    Connection-specific DNS Suffix  . :
>    Link-local IPv6 Address . . . . . : fe80::709b:bb83:30ff:759a%9
>    IPv4 Address. . . . . . . . . . . : 10.0.40.3
>    Subnet Mask . . . . . . . . . . . : 255.255.0.0
>    Default Gateway . . . . . . . . . : 10.0.0.1
> Tunnel adapter Local Area Connection*:
>    Media State . . . . . . . . . . . : Media disconnected
>    Connection-specific DNS Suffix  . :
> Tunnel adapter Local Area Connection* 9:
>    Media State . . . . . . . . . . . : Media disconnected
>    Connection-specific DNS Suffix  . :
> Tunnel adapter Local Area Connection* 11:
>    Media State . . . . . . . . . . . : Media disconnected
>    Connection-specific DNS Suffix  . :
>
> Here is what's in example.conf:
> # Slirp for internet connection (outgoing)
> # Inside running coLinux configure eth0 with this static settings:
> # ipaddress 10.0.2.15   broadcast  10.0.2.255   netmask 255.255.255.0
> # gateway   10.0.2.2    nameserver 10.0.2.3
> #eth0=slirp
> # Tuntap as private network between guest and host on second linux device
> eth0=tuntap
> # Setup for serial device
> #ttys0=COM1,"BAUD=115200 PARITY=n DATA=8 STOP=1 dtr=on rts=on"
> # Run an application on colinux start (Sample Xming, a Xserver)
> #exec0=C:\Programs\Xming\Xming.exe,":0 -clipboard -multiwindow -ac"
> These settings have worked in the past. CoLinux is limited, on
> purpose, to only being able to connect to the host running it. I don't
> need, or want, coLinux to connect past it's host.
>
> "Don't worry about connection state."--Tried starting coLinux with
> "Local Area Connection 2" as "Media disconnect". coLinux says:
> "Setting up networking....
> Configuring network interfaces...SIOCSIFADDR: No such device
> eth0: ERROR while getting interface flags: No such device
> SIOCSIFNETMASK: No such device
> eth0: ERROR while getting interface flags: No such device
> Failed to bring up eth0.
> done. "
>
> Went ahead and changed the driver config Advanced->Media Status to
> "Always Connected".
> This triggers "Identifying..." under Network Connections control
> panel. Eventually it shows my domain and a status of "Limited
> Connectivity"
>
> I assign an IP address of 192.168.0.1 and start coLinux again, but get
> the same result as above for eth0.
>
> Also tried turning on MS's Internet Connection Sharing on Local Area
> Connection 2 (as I had in the older version) and start coLinux again,
> but get the same result.
>
> Is there someplace other than example.com that coLinux is suppose to
> get net config data?
> Perhaps there is something different in Windows Server 2008 that needs
> to be configured? Bridging? (Not technically new as 2003 had it)
>
> -Paul