iB::Topic::Can't ping

	Damn Small Linux :: Damn Small Linux Board The DSL Forums

» Welcome Guest
[ Log In :: Register ]

Damn Small Linux Board » Damn Small Linux » Networking » Can't ping

		Mini-ITX Boards Sale, Fanless BareBones Mini-ITX, Bootable 1G DSL USBs, 533MHz Fanless PC <-- SALE $200 each!
		Get The Official Damn Small Linux Book. DSL Market , Great VPS hosting provided by Tektonic

Pages: (2) </ [1] 2 >/

[ Track this topic :: Email this topic :: Print this topic ]

Topic: Can't ping

< Next Oldest | Next Newest >

joeinnes

Group: Members
Posts: 4
Joined: July 2006

Posted: July 06 2006,21:13

Ok, I've just installed DSL to the Hard Disk (but this is not a HD install issue), and I have a problem. I have a network set-up that basically comprises three levels.

Code Sample

[Router] - - (wireless) - - [PC2] - - (wired) - - [PC3]
|
|
[PC1]

PC1 and PC2 are Windows boxes. PC3 is the DSL box. Basically, I want to be able to use Samba to share resources between PC3 and PC2. I don't particularly care whether PC3 is connected to the internet or not.

So, I boot up PC3, and check to see if it's autoconfigured. Which it hasn't, but that's no big deal, I wasn't expecting it to anyway. So, I type in the details, and try a ping on PC2, which fails. Details are below, I can't figure out what I've done wrong. Oh, by the way, the cable between PC2 and 3 is a crossover cable.

Code Sample

Router IP: 192.168.1.1
PC1 IP: 192.168.1.100
PC2 WLAN Card IP: 192.168.1.103
PC2 Ethernet Card IP: 192.168.0.1

So I try:

Code Sample

ifconfig eth0 192.168.0.2 broadcast 192.168.0.255 netmask 255.255.255.0 up
route add default gw 192.168.0.1
ping 192.168.0.1

And the ping fails. I've tried it from PC2 to PC3 (ping 192.168.0.2), and nothing.

No firewalls are running, nothing, it's just not registering. The hardware's fine, and I can ping 192.168.0.2 from that box, and vice versa, so the cards are configured correctly... I'm at a loss...

Cheers

Joe
EDIT:
Ok, news... poking around a bit, I get this error message:

Code Sample

NETDEV WATCHDOG: eth0: transmit timed out

Whatever that means.

Google doesn't have a clue.

Thanks

Joe

jonam

Group: Members
Posts: 37
Joined: May 2006

Posted: July 07 2006,06:38

Joe,

Googling just NETDEV WATCHDOG returns quite a few posts from discussion groups. See:

http://www.cs.helsinki.fi/linux/linux-kernel/2002-03/1493.html

and

http://lists.us.dell.com/piperma....11.html

The problem appears to be related to network cards. You haven't said what hardware you are using so in lieu of that information, I would recommend you try another network card based on the information in the above posts.

Also, if you want your DSL box to access the internet, you will have to activate the IP passthrough function built into Windows. In Win98SE, it is called Internet Connection Sharing but I don't know how it was implemented in later versions.

Regards,

Jonam

joeinnes

Group: Members
Posts: 4
Joined: July 2006

Posted: July 07 2006,07:07

I'm using a Pentium III Coppermine, with 256K RAM. The network card is a cheap U.S. Robotics one, but I had it working under Gentoo. I'd love to try it with a different NIC, but I'm a student, and I can't afford one.

Both of these seem to show different NETDEV WATCHDOG errors to the one I'm getting, and so I don't think the solutions are appropriate to me.

Thanks for your help,

Joe

jonam

Group: Members
Posts: 37
Joined: May 2006

Posted: July 07 2006,13:17

I did some more searching and one solution to the problem appears to be to disable ACPI power management completely. See here:

http://lists.xensource.com/archive....14.html

DSL normally boots with the cheat code "noacpi" in the boot command line. Suggestion appears to be to add acpi=off to this command line as well.

Try this out and see how you go. I have a PIII Coppermine(desktop), 384MB, with Realtek ethernet adapter which I have loaded DSL on as a live CD and it works fine. Another option might be to try DSL 2.1b which has a newer kernel.

Regards,

Jonam

green

Group: Members
Posts: 453
Joined: Oct. 2004

Posted: July 08 2006,03:59

I would try making all the IP's on the same subnet.
You have one subnet as: 192.168.1.x and the other subnet is: 192.168.0.x
PC's like to be on the same subnet unless there is a router between them that knows how to route the tcp/ip traffic between them. There is no real network reason for them to not be on the same subnet is this situation.
Give it a shot, it's easy to do before getting too deep into something else.
So an example would be:
PC1 192.168.1.100
PC2 192.168.1.103
PC3 192.168.1.105
Make your broadcast, netmask, and default gateways the same.

Good luck.

8 replies since July 06 2006,21:13

< Next Oldest | Next Newest >

[ Track this topic :: Email this topic :: Print this topic ]

Pages: (2) </ [1] 2 >/

Damn Small Linux Board » Damn Small Linux » Networking » Can't ping