Tom's Hardware > Forum > Linux/Free BSD > Linux/Free BSD General Discussion > Caldera OpenLinux 2.4 Network problems

Caldera OpenLinux 2.4 Network problems

Forum Linux/Free BSD : Linux/Free BSD General Discussion - Caldera OpenLinux 2.4 Network problems

Tom's Hardware: Over 1.4 million members in 6 different countries available to answer all your high-tech questions. Sign up now! Its free!
Word :    Username :           
 

I decided to get all my spare bits together and make another comp.

I got a mobo with the i430VX chipset running a Cyrix166mx CPU.

I installed Windows98se (mainly to use the dos part with some dos TCP/IP tools).
The network card works and finds and connects to my other comps.

The card is a "32-BIT IO MODE PCI ETHERNET ADAPTER" based on the Realtek RTL8029 chip.

I installed Caldera OpenLinux eDesktop 2.4. It didn't complain when installing (not about the nic anyway.)

I can't ping any other computer on my net. It pings localhost (127.0.01). It can't ping its own hostname or IP (192.168.0.3), it says network unreachable. And obviously cannot pull an IP from my Win2k DHCP comp or even when I boot the DHCP comp in Redhat, again serving DHCP.

When I run COAS, I can see eth0 and all the ip and stuff bound to it, but still nothing seems to work. cant figure out what is wrong.

Any help would be apreciated.

Thanx.



<font color=red><i>Poor is the pupil, who does not surpass his mentor</i> - Leonardo daVinci</font color=red>

Sponsored Links
Register or log in to remove.

two words: default route.

but first, hold up a moment, you said when you run COAS, you see eth0 and all the ip and stuff... however you also said youcannot pull an IP from Win2K DHCP?

Probably need to go back to basics for a moment...

Start with `ifconfig -a`. that'll tell you what's up as far as IP addresses for the card. If that's no good, then try to bring it up manually with `ifup eth0`.

Assuming DHCP and DHCPC is working, it should then pull an IP accross the net. If it does, everything's probably been set up. run `ifconfig -a` again to check.

Got IP but no network? `route` will show the current routing table. If there's just one entry like 127.0.0 * 255.0.0.0 then you need to add a route to 'outside your computer', something like `route add -host 192.168.0.1 netmask 255.255.255.0 dev eth 0` and `route add default gw 192.168.0.1`.

It might be something completely different of course, like the PCI card isn't being set properly. Let me know where it's at with the networking, and then I'll have a think about other possibilities.

Reply to Anonymous

Actually, if I set the ip manually it seems to work, I can ping my other comps and vice versa. (don't know why that wasn't happening before.)

The problem comes when I try to get DHCP to work. My other win98/WinNT box manages to pull an IP from the Win2k box. The Caldera box, when booted into Win98 also manages to get an IP and successfully get onto the network. They seem to work even if the Win2k box is booted into Redhat. Its just this caldera linux that fails to get in IP.

If I try setting eth0 to DHCP and running 'ifup eth0', it doesn't get a response from DHCP server. Before I thought it might be an IRQ problem, but since it works with a static IP, I haven't got a clue to what is wrong...

<font color=red><i>Poor is the pupil, who does not surpass his mentor</i> - Leonardo daVinci</font color=red>

Reply to HolyGrenade
Tom's Hardware > Forum > Linux/Free BSD > Linux/Free BSD General Discussion > Caldera OpenLinux 2.4 Network problems
Go to:

There are 1223 identified and unidentified users. To see the list of identified users, Click here.

Please mind

You are about to answer a thread that has been inactive for more than 6 months.
If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.

Add a reply Cancel
Sponsored links
  • Ask the community now
  • Publish
Ad
They won a badge
Join us in greeting them