LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   HELP!!! Networking Problem (https://www.linuxquestions.org/questions/slackware-14/help-networking-problem-113041/)

suhanduman 11-06-2003 09:47 AM

HELP!!! Networking Problem
 
Hi all;

I have downloaded Slack9.0 and install it. And i have also configure the network parameters correctly. (netconfig) But i can not ping any of the IP's on my network even the gateway and DNS.

I have used RedHat, and GelecekLinux (a local distro) before, and the network was reachable with both of them.

I am suspecting somethings:

1. I can not set network parameters correctly or i miss something.
If i run "ifconfig", it seems ok. But we are not in a domain environment, instead, here is a WORKGROUP. But i can not leave blank the domain name under "netconfig". Anyway i tried to delete/modify the "search" line in /etc/resolv.conf.

2. My network card is not known.
I am using Cnet Pro2000 (windoze2k says that). But under linux it is known as Davicon (may be it's chipset). And Slack detect it as "tulip", but under dmesg it says it is Davicon. (I think it's true)
Also i have compiled the kernel with another drivers, but the result was same.

3. IRQ problem.
Under windoze2k, the nic irq is 22. Under slack it is 9. (I/O range is ok 800-8ff). Is irq a problem or not, i don't know. After first install, there was a conflict with usb and nic, but i have disabled the hot-plug option, and now there is no usb. (irq 9 now belongs to nic)

I want to use Slackware, but i couldn't!!!

Thank you for your helps.

GAVollink 11-06-2003 10:30 AM

Re: HELP!!! Networking Problem
 
Quote:

Originally posted by suhanduman
[1. I can not set network parameters correctly or i miss something.
If i run "ifconfig", it seems ok. But we are not in a domain environment, instead, here is a WORKGROUP. But i can not leave blank the domain name under "netconfig". Anyway i tried to delete/modify the "search" line in /etc/resolv.conf.
The word domain can be used in a "windows" context or an Internet context. They are two different things. I point this out, because you specify "WORKGROUP", and workgroup is entirely a "Windows/SMB" thing, and has nothing to do with Internet or DNS.

For instance, I use a "workgroup" between my Windows and SMB/Linux machines (SMB is the file sharing protocol for Windows machines - see samba.org). My workgroup is "CORVU". However, I am also on the internet, and my Internet domain is "corvu.com". That said, you should find what other machines are set up to use for "DNS" settings.

The "search" line is only used when you try to find unqualified server names through DNS. For instance - my search line says "corvu.com", so if I "ping billpc", then DNS will look for "billpc.", and failing that will then tack on the search extension, searching for "billpc.corvu.com." If search isn't there, it will only effect local traffic, not global internet use. More important is that you have properly configured DNS server addresses within your resolv.conf.

Quote:

Originally posted by suhanduman
2. My network card is not known.
I am using Cnet Pro2000 (windoze2k says that). But under linux it is known as Davicon (may be it's chipset). And Slack detect it as "tulip", but under dmesg it says it is Davicon. (I think it's true)
Also i have compiled the kernel with another drivers, but the result was same.
So long as "ifconfig" will show you that your card is there, and has an IP address - it is probably fine. That said you should try to ping the IP address that is claimed by the network card. "ping xxx.xxx.xxx.xxx" where the xxx sets are replaced by the NUMBERS that represent the ethernet card's IP address.

Quote:

Originally posted by suhanduman
3. IRQ problem.
Under windoze2k, the nic irq is 22. Under slack it is 9. (I/O range is ok 800-8ff). Is irq a problem or not, i don't know. After first install, there was a conflict with usb and nic, but i have disabled the hot-plug option, and now there is no usb. (irq 9 now belongs to nic)

I want to use Slackware, but i couldn't!!!

Thank you for your helps.
It is quite likely that the troubleshooting done at step 2 will tell you what's going on with your IRQ stuff. Let us know!

suhanduman 11-06-2003 11:18 AM

Hi;
Thank you for your superb fast reply.

Ok, our network is like that;

DNS:172.16.1.63
GW:172.16.1.1
ME:172.16.1.92
Sub-Mask:255.255.248.0

There is windows and AIX machines.

We are not login to a domain, but if you meant "i am pinging the machines on the same subnet?" yes; but i can get reply. (172.16.1.0/21)
I know the differences between Workgroup and Domain. I gave the domain name as same with our AIX machines on the same subnet in /etc/resolv.conf. (which is ozel.gelirler.gov.tr)

I can not understand; with other distros, everything was ok. But with slack i have problems. And i don't want to give up, instead i want to solve it. (or you can not learn linux isn't it?)

Here is my config:


dmesg |grep eth0:

eth0: Davicom DM9102/DM9102A rev 64 at 0xd800, 00:08:A1:26:CB:69, IRQ 9.


ifconfig -a:

eth0 Link encap:Ethernet HWaddr 00:08:A1:26:CB:69
inet addr:172.16.1.92 Bcast:172.16.7.255 Mask:255.255.248.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:235 errors:0 dropped:0 overruns:0 frame:0
TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:105234 (102.7 Kb) TX bytes:518 (518.0 b)
Interrupt:9 Base address:0xd800

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:99 (99.0 b) TX bytes:99 (99.0 b)


netstat -rt:

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
localnet * 255.255.248.0 U 40 0 0 eth0
loopback * 255.0.0.0 U 40 0 0 lo
default 172.16.1.1 0.0.0.0 UG 40 0 0 eth0

Thanks again.

GAVollink 11-07-2003 10:05 PM

OK - if you can ping 172.16.1.92 (your own Ethernet address) - that will tell you that the card is probably working.

Second, try to see if you can ping your gateway: 172.16.1.1, if this works - you know your card and machine are working properly, but the DNS configuration may be messed up still.

Then try to ping your DNS server at: 172.16.1.63. If this doesn't work - double-check to verify that your DNS server is correct. If it does work, try to see if you can resolve DNS entries with it...

% dig www.google.com

If you recieve an output (that doesn't look like an error) then you are good there as well). I doubt you'll get this far though - if you can ping your DNS server, and another computer using the same DNS server can "dig" a DNS entry... then you should check to see if your slack install/configuration enabled a Firewall that's blocking your DNS responses (shouldn't be - but I've seen stranger things happen).

suhanduman 11-08-2003 05:16 AM

Hi;
I can successfuly ping my own host. (ping 172.16.1.92 / ping localhost)
But still can't get any response from GW, DNS or other computer on the same subnet.
Anyway, I have tried with Knoppix CD to check the parameters.
The IRQ, Nic driver, /etc/resolv.conf and other settings are same. And i can ping and access internet using Knoppix. May be you are right about the firewall settings.

littlescott 12-17-2003 06:23 PM

Hey, let you know your'e not alone.. :)

i too have the exact same problem in slackware as you with a davicom chipset..,

had a macronix, everything worked sweet, swapped with a cnet pro200, no network, although everything SEEMS in order, can ping away to myself not a prob, can ping no-one else..,

so, i let that stew for a while., (amazing how much school work you can get done without chat clients going :P), and finally did a re-install today...

BANG, same problem, on the outside, she looks like she is fine., but still can't ping anything but herself.

i can even see my switch flashing away with the ping calls... :/

card is not bung, cause i use it in Windows...,

Anyone else come across this problem? or even a solution? heh

GAVollink 12-29-2003 09:22 PM

OK - so I was an unbeliever when I posted previously - but oddly enough I had this same issue with a Debian install (mind you, never with slack) - everything was exactly as it was supposed to be - everything - but yet, nothing /quite/ worked. So, I re-installed it again, using a different default kernel, and poof - it works. Seems like a strange idea perhaps, but perhaps if you try another slack kernel like bareacpi.i or similar (especially on a laptop) this may magically "fix" your problem like it did mine? Just a shot in the dark.


All times are GMT -5. The time now is 09:15 PM.