• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Determine IP failed.

 
Ranch Hand
Posts: 672
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I just installed redhat 9.0 on a Dell sever. I selected �use DHCP� during installation.
Now it can not connect to my network.
It says �Determine IP failed� during startup at �bring up eth0� step.
Thanks.
 
author and iconoclast
Posts: 24207
46
Mac OS X Eclipse IDE Chrome
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Well, let's look at the obvious things first: is there a DHCP server on your network? Did the driver for your network card initialize OK?
 
Bruce Jin
Ranch Hand
Posts: 672
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
> is there a DHCP server on your network?
Yes. I used to install Mantrake 8 on other PCs the same way. This time I am installing Redhat 9.0 on a Dell server box.
> Did the driver for your network card initialize OK?
How to check this?
Thanks.
 
Ernest Friedman-Hill
author and iconoclast
Posts: 24207
46
Mac OS X Eclipse IDE Chrome
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Use the "dmesg" command to see the messages printed during boot time; look for failures.
Other ideas: search in /var/log/messages for "dhcpcd" and see if you find any useful log messages that explain the problem. If not, stop dhcpcd with "sudo /sbin/dhcpcd -k" and start it again with "sudo /sbin/dhcpcd -d" so it will print debug messages, and you will get more useful data on stdout and in /var/log/messages.
To actually see the debug messages, you have to arrange to get them logged. From the dhcpcd man page:
 
Greenhorn
Posts: 24
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
By the way, why wouldn't you use static ip for your server?
 
Bruce Jin
Ranch Hand
Posts: 672
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks alot.
Our network people figured this out by playing Network config.
dmesg is interesting command.
 
reply
    Bookmark Topic Watch Topic
  • New Topic