Menu
▾
▴
[coLinux-devel] Re: [coLinux-users] Unable to connect to coLinux from same box
|
From: Michael L. <mi...@s2...> - 2004-06-06 01:14:17
|
Not quite that big of a newbie. :) As I said before, no firewall is running on XP, there's a physically separate box doing all of that stuff between the net and the local network. Vince, do you perchance have a MSI motherboard? I have the same Broadcom NIC as you do. -----Original Message----- From: col...@li... [mailto:col...@li...] On Behalf Of John LeSueur Sent: June 5, 2004 9:09 PM To: Vince Hoffman Cc: Michael Laccetti; col...@li...; col...@li... Subject: Re: [coLinux-devel] Re: [coLinux-users] Unable to connect to coLinux from same box Try looking at your firewall settings, and remove any on your XP installation. John Vince Hoffman wrote: >On Sat, 5 Jun 2004, Michael Laccetti wrote: > > > >>Hey guys, I've got a really weird issue. When I have coLinux running >>on this machine (XP), I can't ping it from under XP, and I can't ping >>XP from under coLinux. If I VNC to my dedicated Linux box, or my >>Win2k3 server, I can SSH/VNC into the coLinux. From coLinux, I can >>see every other machine out there, just not the XP that it's sitting >>on. This is all sorts of frustrating. Anybody got any ideas as to >>how I can make them see each other? >> >> > >Wish I did :( >I have the dsame problem, I'm running the latest build from >sourceforge, on windows XP sp1. I've tried both the winpcap and the XP >native bridging with no luck. > >some relevent (maybe ? ) data >From daemon: > >Cooperative Linux Daemon, 0.6.1 >Compiled on Sat May 29 16:20:11 2004 > >From config file: > > <network index="0" name="Broadcom NetXtreme Gigabit Ethernet" >type="bridged"/> > >From startup: > >co_message_switch: setting callback rule for 6 >bridged-net-daemon: Checking adapter: Generic NdisWan adapter >bridged-net-daemon: Checking adapter: MS Tunnel Interface Driver >bridged-net-daemon: Checking adapter: Broadcom NetXtreme Gigabit >Ethernet Driver (Microsoft's Packet Scheduler) >bridged-net-daemon: Listening on: Broadcom NetXtreme Gigabit Ethernet >Driver (Mi crosoft's Packet Scheduler) ... >bridged-net-daemon: Listening for: (ether dst 00:43:4f:4e:45:30) or >(ether broad cast or multicast) or (ip broadcast or multicast) pipe >client 0/8: Connecting to daemon... >pipe client 0/8: Connection established >daemon: module connected: conet0 >co_message_switch: setting callback rule for 8 > >More disturbingly a tcpdump of a ping between them (colinux= 10.0.0.120 >windows= 10.0.0.10) ping gives: > >colinux root # ping 10.0.0.10 >PING 10.0.0.10 (10.0.0.10) 56(84) bytes of data. > >--- 10.0.0.10 ping statistics --- >2 packets transmitted, 0 received, 100% packet loss, time 1015ms > >while tcpdump shows: > >listening on eth0, link-type EN10MB (Ethernet), capture size 68 bytes >20:03:05.234086 IP 10.0.0.120 > 10.0.0.10: icmp 64: echo request seq 1 >20:03:05.234811 IP 10.0.0.120.1034 > unsane.co.uk.domain: >46843+[|domain] >20:03:05.236848 IP 10.0.0.10 > 10.0.0.120: icmp 64: echo reply seq 1 >20:03:05.236878 IP unsane.co.uk.domain > 10.0.0.120.1034: 46843 >NXDomain*[|doma in] >20:03:05.237063 IP 10.0.0.120.1034 > unsane.co.uk.domain: >46844+[|domain] 20:03:05.238790 IP unsane.co.uk.domain > >10.0.0.120.1034: 46844 NXDomain*[|doma in] >20:03:05.238909 IP 10.0.0.120.1034 > unsane.co.uk.domain: >46845+[|domain] >20:03:05.240744 IP unsane.co.uk.domain > 10.0.0.120.1034: >46845*[|domain] >20:03:06.249358 IP 10.0.0.120 > 10.0.0.10: icmp 64: echo request seq 2 >20:03:06.251320 IP 10.0.0.10 > 10.0.0.120: icmp 64: echo reply seq 2 >20:03:10.229086 arp who-has 10.0.0.10 tell 10.0.0.120 >20:03:10.229242 arp who-has unsane.co.uk tell 10.0.0.120 >20:03:10.231194 arp reply 10.0.0.10 is-at 00:0c:76:41:77:9f >20:03:10.231695 arp reply unsane.co.uk is-at 00:50:8b:03:6d:00 > >which if you cut out the DNS traffic, shoes ping request and replys. > >Any suggestions welcome, should i ask on the developers list ? > >Vince > > > > >>Mike >> >> >> > > >------------------------------------------------------- >This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one >installation-authoring solution that does it all. Learn more and >evaluate today! http://www.installshield.com/Dev2Dev/0504 >_______________________________________________ >coLinux-devel mailing list >coL...@li... >https://lists.sourceforge.net/lists/listinfo/colinux-devel > > ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ coLinux-devel mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-devel |