|
From: John F. <J.P...@as...> - 2004-08-16 10:40:44
|
I have done some more testing on my routing problem. The solution on Windows XP has been to swap from Internet Connection Sharing to using the Windows XP bridging. When that is installed and the appropriate settings made for the external network, the coLinux "computer" is seen as part of the external network. This means that the IP settings for eth0 in the colinux change to those needed for the external network. e.g. in my case where the external network is 192.168.123.x then 192.168.123.40 is a valid choice for the colinux. I had become confused as I had not realised that there are two distinct ways of organising what is referred to as "Native Bridging" on the wiki page http://www.colinux.org/wiki/index.php/coLinuxNetworking (a) Native bridging using type="bridged" in the colinux configuration. (b) Native bridging using type="tap" in the colinux configuration and then using a Windows XP bridge. When I have set up type (b) and changed the IP number, I have been able to access the colinux using both Samba and VNC from the second computer on my network, which is what I wanted to do. Thank you for providing such a useful tool. Best wishes John Fletcher ------------------------------------------------------------------- Dr John P. Fletcher Tel: (44) 121 359 3611 ext 4625 Chemical Engineering and Applied Chemistry (CEAC), School of Engineering and Applied Science (SEAS), Aston University, Fax: (44) 121 359 4094 Aston Triangle, Email: J.P...@as... BIRMINGHAM B4 7ET U.K. CEAC Web site http://www.ceac.aston.ac.uk/ |