Networking problem in Linux, but no problem in Windows on same hardware

Networking problem in Linux, but no problem in Windows on same hardware

Post by Christopher Ada » Sun, 08 Apr 2001 12:55:50



To Linux Networking expects...

You may or may not be able to help me (a true Linux newbie) with this
problem....

I have a system with removable hard drives (slide out frames) for
which I have both Windows 98 and Linux configurations up and running.
However, while I can get the Windows 98 configuration to connect to
the internet (through my router), I am not able to get my Linux
configuration to connect using (what I think) are equivalent
internet/network card setup parameters.

I can (and have) set up my Windows 98 configuration two ways: First,
using DHCP to let the router assign the computer an internet address,
etc., and Secondly, har coding the internet address, DNS address, etc.
- and both configurations seem to work fine.   However, when I try to
do this in Linux, I am not even able to talk to the router's status
page (at 192.168.123.254 - a local address which my router will
respond to).  

My ethernet card is working ok in Windows 98, but it may not be
working in Linux.  

The key hardware on my system:

P-233, with 64 mb ram.
8+ gig Maxtor HD.
3Com Etherlink 3c905 (?) class ethernet card.

I have set up the system with both Caldera and SuSE distributions, but
with no avail.   What could I be doing wrong, and how can I check the
scenarios and fix them?

Thanks in advance....

Chris

 
 
 

Networking problem in Linux, but no problem in Windows on same hardware

Post by Dean Thompso » Sun, 08 Apr 2001 14:01:45


Hi Chris,

[...]

Quote:> My ethernet card is working ok in Windows 98, but it may not be
> working in Linux.

The above could be a clue.  When the system boots, do you see it identify your
network card.  It will appear in the startup screen as all the stuff scrolls
past your eyes.  You want to look out for something which says: eth0.  If it
goes too fast, then you might like to take a look in the /var/log/messages
file which contains a copy of most of the stuff that you see at bootup.

Providing that all goes well, and you can see a reference to the 3com card in
your bootup, you should check the following files (they have been configured
with a static IP address) and see whether the following has been set correctly
(and restart the networking or computer and see if it works):

/etc/sysconfig/network
======================
NETWORKING=yes
FORWARD_IPV4=false
GATEWAY=192.168.123.254
GATEWAYDEV=eth0
<You can leave your current definitions of hostname and domainname here>

/etc/sysconfig/network-scripts/ifcfg-eth0
=========================================
DEVICE=eth0
IPADDR=192.168.123.<x> ---> What ever your number is on the IP
NETMASK=255.255.255.0
NETWORK=192.168.123.0
BROADCAST=192.168.123.255
ONBOOT=yes

/etc/resolv.conf
================
nameserver <IP ADDR OF NAMESERVER>
nameserver <IP ADDR OF NAMESERVER>

If you get stuck for name servers you can enter the following:

/etc/resolv.conf
================
nameserver 205.166.226.38
nameserver 206.55.70.18

See ya

Dean Thompson

--
+____________________________+____________________________________________+

| Bach. Computing (Hons)     | ICQ     - 45191180                         |
| PhD Student                | Office  - <Off-Campus>                     |
| School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)    |
| MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077                  |
| Melbourne, Australia       |                                            |
+----------------------------+--------------------------------------------+

 
 
 

Networking problem in Linux, but no problem in Windows on same hardware

Post by G Sof » Sun, 08 Apr 2001 16:12:21


Chris,
    One quick thing, if you do a ifconfig -a do you have an eth0?  Try this
dmesg > hlist
grep 3c hlist
This will list any attempts or completions of loading the 3com card.  My
first guess is it is not loading the module for the 3com card.  Also try an
lsmod and see if there is a 3com module loaded.  I use both Caldera and SuSE
and neither have the 3c905 statically linked in the kernel so it would need
to load a module. If there is no listing for the 3c59x.o module try doing a
modprobe 3c59x.
If you would like to repost the results of any of these we can probably
provide some more help.

Phil


Quote:

> To Linux Networking expects...

> You may or may not be able to help me (a true Linux newbie) with this
> problem....

> I have a system with removable hard drives (slide out frames) for
> which I have both Windows 98 and Linux configurations up and running.
> However, while I can get the Windows 98 configuration to connect to
> the internet (through my router), I am not able to get my Linux
> configuration to connect using (what I think) are equivalent
> internet/network card setup parameters.

> I can (and have) set up my Windows 98 configuration two ways: First,
> using DHCP to let the router assign the computer an internet address,
> etc., and Secondly, har coding the internet address, DNS address, etc.
> - and both configurations seem to work fine.   However, when I try to
> do this in Linux, I am not even able to talk to the router's status
> page (at 192.168.123.254 - a local address which my router will
> respond to).

> My ethernet card is working ok in Windows 98, but it may not be
> working in Linux.

> The key hardware on my system:

> P-233, with 64 mb ram.
> 8+ gig Maxtor HD.
> 3Com Etherlink 3c905 (?) class ethernet card.

> I have set up the system with both Caldera and SuSE distributions, but
> with no avail.   What could I be doing wrong, and how can I check the
> scenarios and fix them?

> Thanks in advance....

> Chris

 
 
 

1. supraexpress modems (28.8) problems w/dial-ins

Hello,

        I've configured my linux box to receive calls from two 28.8
SupraExpress modems (both support v.34).  Everything works fine, the
connection, everything.  However, when the user logs off, the modems
literally go bezerks and make the LED display shows pure garbage and
the SD/RD leds blinks relentlessly.  After that, the modem no longer
answer to commands issued by my system or to incoming calls, and I get
this kind of messages inside /var/adm/messages:

Feb 24 14:05:02 zeus kernel: ttyS0: 13 input overrun(s)

        for both ports.  The only solution is to power off the modem
and restart it.  Then, uugetty regains controls and accepts answers.

        Here's a copy of my /etc/default/uugetty.ttyS0 file:

CLEAR = NO
HANGUP=YES
#DEBUG=777
DEBUG=010
INIT="" AT&F2S0=1\r OK
ALTLOCK=cua0
ALTLINE=cua0
#WAITFOR=RING
#CONNECT="" ATs0=1\r CONNECT \s\A
TIMEOUT=60

        Help!

        ...David

--

// Socom technologies, Inc.        Tel: 514/939-0480 Fax: 514/939-0834
   " There are lies, damned lies, and statistics. " -- Mark Twain

2. How can I get console output to an X window?

3. Netscape plug-ins problem

4. Anybody have experience with Acer products

5. Problems with dialing out when dial-ins are enabled

6. Any one using Trident 9400 Video card?

7. Netscape 4.51 and plug-ins problem

8. Serial port ttyb wrongly buffers characters at 300 baud?

9. Windows media Player plug-ins

10. Sherlock linux plug-ins / sherlock for linux?

11. List of plug-ins for linux/netscape please!

12. Errors compiling Wingz 1.4 Add-ins (Linux 1.3.99, GCC 2.6)

13. Linux and Dial-ins (?)