[SLE] hhhhhhhheeeeeeeeeeeeeelllllllllllllpppppppp
Hello i hope someone can help me with this problem or else im goin to have to do the unmentionable and change to NT... i have Suse 6.3 installed on a compaq EP6550 which is a pentium III 550mhz with 256mb ram the system works fine untill i try to get it to run on the network (im not a newbie on connecting to a network) i have tried five different network cards 3com 905b, 3com905c, icl etherteam 16/32, intel etherexpress pro 100, intel etherexpress pro 100 wol. now the only way i get the system on the network is by using the intel etherexpress pro 100 wol card in 10mb mode and having it connected to an hp 24 port hub which is then connected to a cisco 2916 switch the funny thing is that this is the only way it works if i try to use another brand of hub or try to dirrectly to connect to the cisco switch it wont work all the other network cards do not work at all, the system sees it fine and loads the aproriate module but it just doesnt get only i did tcpdump and noticed that it sends an arp request for the gateway ip but it doesnt get a reply which is hard to belive what seems to be the problem is that it is not able to recieve or interpret the reply. i was hoping that some one could help out i have booted and tried to use other kernel versions such as 2.0.36 2.2.10 and 2.2.7 but its still the same. same thing is with redhat ive tried suse 5.3 6.0.6.1 6.2 6.3 and redhat 5.2 6.0 and 6.1 all experience the same thing. i hope some one can help me or else all my work is useless and worst of all i would have to convert to NT, the bad news is that if this happens, linux would not be considered to be used in our (big) company in production this machine is supposed to be a pilot project in evaluation linux so someone hhhhhhhheeeeeeeeeeeeellllllllllpppppppppppppppp regards Mat -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Thu, 09 Mar 2000, Mat wrote:
the system works fine untill i try to get it to run on the network (im not a newbie on connecting to a network)
i have tried five different network cards 3com 905b, 3com905c, icl etherteam 16/32, intel etherexpress pro 100, intel etherexpress pro 100 wol.
I'm using a 3com905 card with no problems in my Dell docking station. I also use it 6.3 with a number of other cards including a D-Link 650 PCMCIA card and a couple very generic PCI cards. I'm not up on the specs of all of these cards - are they all PCI? Have you tried different PCI slots? Does the box have any ISA slots? If so, can you try an ISA card?
now the only way i get the system on the network is by using the intel etherexpress pro 100 wol card in 10mb mode and having it connected to an hp 24 port hub which is then connected to a cisco 2916 switch the funny thing is that this is the only way it works if i try to use another brand of hub or try to dirrectly to connect to the cisco switch it wont work
My 3com 905 card also attaches to a hub and then to an Intel switch. Please pardon me for asking obvious questions, but have you tried different ports on the hub? Have you swapped out cables? Do you get link lights with the other cards?
all the other network cards do not work at all, the system sees it fine and loads the aproriate module but it just doesnt get only i did tcpdump and noticed that it sends an arp request for the gateway ip but it doesnt get a reply which is hard to belive what seems to be the problem is that it is not able to recieve or interpret the reply.
Can you ping anything? Including localhost? Are you assigning a static IP or attempting to use DHCP? If DHCP, try it with a static IP address.
i was hoping that some one could help out i have booted and tried to use other kernel versions such as 2.0.36 2.2.10 and 2.2.7 but its still the same. same thing is with redhat ive tried suse 5.3 6.0.6.1 6.2 6.3 and redhat 5.2 6.0 and 6.1 all experience the same thing.
This is the primary reason I believe you have a hardware problem somewhere. I've networked with most of these versions of Linux and some of the versions of the kernel you mention without incident.
i hope some one can help me or else all my work is useless and worst of all i would have to convert to NT, the bad news is that if this happens, linux would not be
Why would putting NT on the box be irreversible? Have you had NT working with networking on this exact box before? If not, try it out. I have to believe you're going to experience networking problems on NT also. Once you've determined it's a hardware issue, blast NT and reload Linux - or dual boot if you must. Can you tell us what you've done to check the integrity of the hardware? Thanks, Troy Denkinger -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Mat wrote:
Hello
i hope someone can help me with this problem or else im goin to have to do the unmentionable and change to NT...
Oh, taunt us and bait us . . .
i have Suse 6.3 installed on a compaq EP6550 which is a pentium III 550mhz with 256mb ram
the system works fine untill i try to get it to run on the network (im not a newbie on connecting to a network)
i have tried five different network cards 3com 905b, 3com905c, icl etherteam 16/32, intel etherexpress pro 100, intel etherexpress pro 100 wol.
now the only way i get the system on the network is by using the intel etherexpress pro 100 wol card in 10mb mode and having it connected to an hp 24 port hub which is then connected to a cisco 2916 switch
Please help me understand the Cisco 2916. It looks like this is pretty esoteric stuff. The Cisco web site that discusses this switch (http://www.cisco.com/warp/public/cc/cisco/mkt/switch/fec/prodlit/faste_an.ht...) calls it Fast EtherChannel, and it mentions only a few companies that support it. Can we assume this hardware configuration worked properly *before* you installed Linux? Or did you just put the stuff together and discover it doesn't work?
the funny thing is that this is the only way it works if i try to use another brand of hub or try to dirrectly to connect to the cisco switch it wont work
The OS has no way of being able to tell what port your cable is connected to. Once you are in the physical layer (or even the data link layer), the OS is irrelevant, so it's not a Linux problem, it's a network problem. I recently had a very similar problem. It turned out that the port was bad on a brand-new switch. Funny thing was, we had the link light, my machine was transmitting, but the switch wasn't receiving. I change out the cable with a known, working cable, and the same thing happened. So we moved the cable to another port. Same thing. After scratching our brains for a few minutes (imagine what you will here), we moved the cable to another port and discovered the first TWO ports were bad. Two bad ports on a new switch - go figure. I guess my middle name is Murphy.
all the other network cards do not work at all, the system sees it fine and loads the aproriate module but it just doesnt get only i did tcpdump and noticed that it sends an arp request for the gateway ip but it doesnt get a reply which is hard to belive what seems to be the problem is that it is not able to recieve or interpret the reply.
Put a packet analyzer on the network separate from the machine in question. NetXRay (commercial product for Windows) or Ethereal for Linux (finally available as an RPM for SuSE - thanks guys). Ethereal has solve tons of problems for me. It's on my laptop and I can take it anywhere. (My ISP hates me because I call them and tell them when their primary DNS is dead - they prefer to assume the customers are idiots and therefore always wrong.)
i was hoping that some one could help out i have booted and tried to use other kernel versions such as 2.0.36 2.2.10 and 2.2.7 but its still the same. same thing is with redhat ive tried suse 5.3 6.0.6.1 6.2 6.3 and redhat 5.2 6.0 and 6.1 all experience the same thing.
Try putting Win95 on this set up without changing the hardware. I'm betting you will find the same problems. I suggest 95 as it's pretty quick to install and you only lose an hour to prove it's not the OS.
i hope some one can help me or else all my work is useless and worst of all i would have to convert to NT, the bad news is that if this happens, linux would not be considered to be used in our (big) company in production this machine is supposed to be a pilot project in evaluation linux so someone hhhhhhhheeeeeeeeeeeeellllllllllpppppppppppppppp
I presume you have to make a formal report to someone about your success? Until you resolve the networking problem, you should be able to stall making any prematurely negative reports about the Linux installation. It would make you look really bad if you said Linux won't work, then put NT on that box and it won't work either. What are you going to say then? Scrap NT? I'm betting that it is hardware, and a protocol analyzer elsewhere on the HUB will prove it. Finally, consider this course of action: 1. Since you must have some Borg brain cells running rampant in your brain, go have a couple beers to kill them off. Maybe three or four, just before you get a real good night's sleep. 2. In the morning, develop a testing plan that will eliminate faulty components. You may have more than one. Prove your hardware works. 3. Execute the plan. Feel free to share the plan with us if you want more ideas. A well thought out plan will save you much frustration. Good luck and keep us posted. George Toft -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (3)
-
grtoft＠yahoo.com -
mat＠riverstreams.com -
troy＠whadda.com