Hello all,
ok i'm a complete boob i mean newb to linux. downloaded suse linux 10 installed to an older dell p3 1ghz with 384 ram. here is my problem. machine boots no problem and dhcp picks up all the right settings for my internet connection but then when trying to access the network or internet no connection nothing can be pinged until i unplug the the linux boxes' ethernet cable from the router. then i get about 10 15 seconds of connection before it drops. the router is a linksys wrt54gx2. the router also has 3 other computers (xp) 1 wired, 2 wireless, linksys tech support no help (linux what's linux??) i don't think it is a problem with linux because it is picking up the settings on boot. anyone have any thoughts??
thanks

Go to the Linksys web site, download the latest firmware for your router, and install it in the router. That made a world of difference with my WRT54G router.

I've watched this for a day or two waiting for someone to respond with something more than I had. I've got almost the identical setup; using a PC that is directly connected to the my WRT54G (now a WRT54GS) that also connects a Windows PC, another Linux PC and a wireless laptop. Works without a problem.
I'd support stress_junkie about the firmware update; they've significantly updated it.
I'd also just do basic IP checkup stuff you may already have done:
From your description, it could be NIC in Linux PC that's messing all up. I'd try pinging 127.0.0.0 which is the loopback address. Should work.
Then I'd bypass router and connecting Linux PC directly to your DSL or cable modem, assuming that's what your're using.
Reset the router to factory defaults
Check that you have WPA password setup so that neighbors' access isn't an issue
All PCs set to DHCP instead of static IPs
Turn off all Windows PC's to isolate if Linux can work alone

Thanks for the responses,
stress_junkie-- updating the firmware was the only thing linksys told me to try. it is at the most current level.

RedBoot-- i brainfaded on pinging the loopback will try that tonight to be sure. last night i tried direct connect to the cable modem no joy. would not pick up any dchp from provider but i got called into work last night and really didn't do much other than bootup the machine. gonna pick up a NIC tonight just in case. can always return it. also got my old linksys wired router to try if the NIC is good.
thanks again.

Actually I had forgotten something when I responded. I'm having the same problem!!! I had to power cycle my router today because I wasn't getting DNS from my ISP. That reminded me that this happened once before after I upgraded the firmware. I generally don't use my Windows machines to access the Internet. Maybe I will give one of them a try the next time that my router appears to be unresponsive to my Linux machines.

OK I got the internet on my linux box woohoo! Figured i let you what fixed it. ethernet cable. (duh) even though it worked fine when the machine was a windows box. i'm not complaining mind you, just found it odd. thanks for the responses.
v

Just curious: Was it a bad patch cable, or was it a crossover cable that caused such a problem?

i know this is a really old posting, but just to let everyone know.. i updated the firmware on my WRT54GX2 linksys router because of the same problem everyone else is having. at 12:01 am everynight my WRT54GX2 refuses to pickup my new ip from my provider. i have to power reset my WRT54GX2 just to grab a new ip when it is renewed by my provider.... and your correct with linksys tech support, it was VERY hard to even understand they, let alone them actually helping me with the peoblem. there's a blemish on linksys's backside as far as i am concerned...