From: Dave C. <dc...@da...> - 2008-07-03 10:19:25
|
Hi, Windows XP has a limitation on the number of computers can connect to it. To get around this I'm running a box with linux acting as a shared repository so that all the XP machines on the network can read and write small files to it (thus enabling a pretty crude communication system). This works fine. Now I've installed colinux onto one of the machines in the hope of using the colinux vm to act as the repository. I've used the same samba smb.conf as I used with the separate linux machine. The Colinux vm bridged to the host XP machine's network connection. Both the host and the bridged connection have the same static IP 192.168.10.100 The Colinux vm is on 192.168.10.200 I can ping both 192.168.10.200 and 192.168.10.100 from 192.168.10.13 And I can ping 192.168.10.13 from both of the other machines. However, accessing the Temp directory on the Colinux vm is problematic. Sometimes the permissions are not granted for the other XP machines, sometimes they are unable to access the contents of the Temp directory on the VM and sometimes they can. Sometimes the Colinux VM doesn't show up on the Network neighbourhood at all. Sometimes the machines lock up and do not respond for long periods. Initially all machines can see the Colinux vm and the Temp directory. But after a while the outside machines cannot see it and then the host XP machine cannot see the others, but can see the VM. Also, the VM and the XP host lose the ability to ping the outside machines. Anyone know what's going on here? 'dmesg' and '/var/log/messages' don't reveal much of interest. I don't think it's a samba issue as I can use the same smb.conf on the linux box and that works. I think it's an issue with the bridge. If I switch off the Colinux vm, the XP host cannot see the other network until the bridge is removed. |
From: Josep M. A. S. <ja...@pa...> - 2008-07-03 17:32:12
|
Just to be sure: When you talk about a bridge, you talk about the windows XP feature that lets you connect two network interfaces, creating a third one that then has the IP, right? (I sort of got confused by you saying "both the host and the bridge have the same IP"). Or do you mean the pcap-bridged type of connection of colinux? By the description of the windows machine losing connectivity to outside world, it indeed sounds as a problem on the bridge, or (less probable) on network card, cable, switch or otherwhise physical element. So for now, take a look at http://colinux.wikia.com/wiki/Network#TAP_with_Windows_Software_Bridge and see if that's what you have. -- _ _ /~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-\ o o | Josep Ma [JAZ] | * | ICQ UIN: 7014661 | `-´ | Messenger: ja...@ho... | \-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~/ |
From: Henry N. <hen...@ar...> - 2008-07-03 20:23:40
|
Josep Maria Antolín Segura wrote: > When you talk about a bridge, you talk about the windows XP feature that lets > you connect two network interfaces, creating a third one that then has the IP, > right? (I sort of got confused by you saying "both the host and the bridge have > the same IP"). > > Or do you mean the pcap-bridged type of connection of colinux? > > By the description of the windows machine losing connectivity to outside world, > it indeed sounds as a problem on the bridge, or (less probable) on network > card, cable, switch or otherwhise physical element. > > So for now, take a look at > http://colinux.wikia.com/wiki/Network#TAP_with_Windows_Software_Bridge > and see if that's what you have. > That sems me the XP-Bridge. Not the pcap-bridge mode. One problem, I see, you have self made: "The bridge and the host have the same IP" You need to know, that the bridge and the host have different MAC. If you shutting down the bridge, than the other PC would try to send packets to the old MAC. After a while (some minutes) the MAC cache would be cleared automaticly and the host network should work normal. You can watch the MAC-cache from XP command prompt with "arp -a" or "arp print" (I currently don't remember). To fix this you have one of thise choices: A) Configure a different IP address for the bridge (different from all others you currently have) B) Configure the TAP-Win32 as "always connected" to have all times the bridge online, also if coLinux is not running C) Run the "arp" with clear parameter after shutting down coLinux -- Henry N. |
From: Holger K. <hol...@gm...> - 2008-07-11 17:11:24
|
Dave Coventry schrieb: > > However, accessing the Temp directory on the Colinux vm is > problematic. Sometimes the permissions are not granted for the other > XP machines, sometimes they are unable to access the contents of the > Temp directory on the VM and sometimes they can. Sometimes the Colinux > VM doesn't show up on the Network neighbourhood at all. Sometimes the > machines lock up and do not respond for long periods. > > Initially all machines can see the Colinux vm and the Temp directory. > But after a while the outside machines cannot see it and then the host > XP machine cannot see the others, but can see the VM. Also, the VM and > the XP host lose the ability to ping the outside machines. > I hope you don't have samba on the linux box running when the colinux is started. Disapearing computers on the network can be address resolution conflicts. Are the netbios names set to match the ip names? Is the mac address of the colinux installation really unique on your network. Check if arp -a produces strange results if your connection fails. Similar problems can result if the master browser elections fail. Check with browstat.exe on a windows computer. |
From: Daniel L. <did...@go...> - 2008-07-11 22:14:48
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11 Jul 2008, at 18:11, Holger Krull wrote: > I hope you don't have samba on the linux box running when the > colinux is > started. why can't he run samba inside colinux? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkh3208ACgkQVR0QzBAS6zbcegCfeyCJmG+UPTJypnY0udcVv5uT H/AAniSv/obEwwBEcDjeZ4D716jaj5yY =w5Fc -----END PGP SIGNATURE----- |
From: Holger K. <hol...@gm...> - 2008-07-13 18:06:10
|
Daniel Llewellyn schrieb: > On 11 Jul 2008, at 18:11, Holger Krull wrote: >> I hope you don't have samba on the linux box running when the colinux is >> started. > > why can't he run samba inside colinux? He can run samba inside colinux, but he can't run two samba installations we the same config. |