>>> On Thu, Aug 30, 2007 at 7:26 PM, in message <[EMAIL PROTECTED]>, David Stuart <[EMAIL PROTECTED]> wrote: -snip- > I also issued the "route" and "route -n". route took several seconds to
That's because it was trying to use DNS to resolve the names. > return. The last line of the route -n does show the correct default gateway > for eth0. Again, so far, so good. Good. > However, I am still unable to connect to eth0. A ping in from my PC and > from other hosts on the same subnet still time out. And a ping out still > says Destination host unreachable. Progress is that I also receive the > Destination host unreachable when pinging out to my PC. So it picked up the > route and default gateway and tried to use it. Can you ping your default gateway from the Linux system? If not, check with your network hardware folks. They may have turned off the switch port since your end was inactive for so long (don't ask me how I know that might happen). If you can ping the gateway, then see what a "traceroute -n" from the Linux system to your PC shows you. > Also, where is a good place to read up on rebuilding initrd and running > zipl. I have no experience with either. Pretty much "man mkinitrd" is all you need. To re-run zipl, just type in the command. You should get back something like this: # zipl Using config file '/etc/zipl.conf' Building bootmap in '/boot/zipl' Adding IPL section 'ipl' (default) Preparing boot device: dasda (0150). Done. Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
