From: Henry N. <hen...@ar...> - 2011-11-29 20:47:06
|
Hello Tobbe, please check, that the problem is or is not the renaming udev. Exist the network interface eth0 or what ever under "cat /proc/net/dev" inside the running coLinux? Have you maybe added a new network interface under windows, and coLinux use the wrong now? Check, that the name you have for "network connection name" in coLinux.conf, exist and has exactly this name in your windows network connections. eth0=ndis-bridge,"network connection name",MAC I can say, that I have also installed VirtualBox after coLinux, and I never found a problem. Henry At 28.11.2011 23:50, tobbe wrote: > Thanks for your reply Henry. > > Unfortunately changing to ndis-bridge did not work. Infact, I couldn't > tell any difference at all. > > //Tobbe > > Den, skrevHenry Nestler <hen...@ar...>: > > At 28.11.2011 11:58, Tobbe Lundberg wrote: > > > > > I just installed VirtualBox and my colinux network stopped working. > > > > > Any ideas why that happened and how to fix it? (except for > > > > > uninstalling VB) > > > > > I'm using winpcap for netoworking, and have a static ip configured. > > > > > > > > Replace the word "pcap-bridge" with "ndis-bridge" in your config. > > > > Ndis use an other mechanism. Maybe this will work better. > > > > > > > > -- > > > > Henry N. |