Carl Lowenstein wrote: > On Mon, Dec 1, 2008 at 4:07 PM, Michael Lynch <[EMAIL PROTECTED]> wrote: >> >> The ethernet device is built into the motherboard >> of this paricular computer >> Do you think I would have better luck with >> an installed PCI NIC? >> > > Why don't you boot a memory-resident operating system, such as > Knoppix. That will let you try your hardware with a different OS > without having to reload everything.
Booting to another OS is certainly easy and may be a good diagnostic (if you have a Knoppix or other "live-cd" disk). And here are some other considerations. It doesn't make a whole lot of sense (to me) that there is a problem with your server hardware or driver if it worked on the residential system. Just changing from business/static to residential/dhcp would not seem to explain the symptoms. Although, I suppose it could be a subtle configuration error in the static setup. - How are you configuring the server? What config tools (programs) are you using? You have already reported the content of /etc/resolv.conf, but perhaps it would be useful to post the contents of /etc/sysconfig/network-scripts/ifcfg-eth0 It has already been suggested that other components are worth noting. You say your business line comes into the cisco and then thru a switch to the server, if I recall correctly. - Is there _anything_ else plugged into the cisco or switch? If so can you (perhaps temporarily) remove them and repeat the ping test? - Can you bypass the switch and plug directly into the cisco, and then repeat the ping test? - Can you (then) change to a different the cable from server to cisco? And perhaps you could cut-n-paste the results of running ifconfig -a route -n (Note: If you wish to preserve privacy of your public IP space, you could X-over the first couple/three portions of the IP values displayed in the output from the above -- as, eg: XXX-XXX-XXX.17) For the record, you say a substitute for the server worked plugged into teh business system where the server is, I think. - are you positive the substitute was net-configured the same as the server? - did you use the same cable and hookup (including exact same ports on switch/cisco)? I presume the cisco is preconfigured by cox, and you haven't been asked to do any configuring there, eh? If this seems tedious --it is! But these kind of problems can sometimes be a very fussy challenge. But if we can figure out the cause it _will_ be a learning experience! Regards, ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
