Resolved [Re: Newbee: No network after install of RH 9]

From: bad hair (badhair_at_invalid.com)
Date: 01/15/04

  • Next message: Chris: "Update"
    Date: Wed, 14 Jan 2004 17:13:07 -0800
    
    

    In article <badhair-D4F9CB.10215513012004@news.west.cox.net>,
     bad hair <badhair@invalid.com> wrote:

    > WARNING: Newbee on the loose!
    >
    > I would greatly appreciate links or other sources to help me gather the
    > requisite knowledge to resolve this issue.
    >
    > Here is the story:
    >
    > I have read the RH9 installation, getting started and customize quides.
    > I have leafed through the reference.
    >
    > I used the graphical install of RedHat 9, booted from CD. It appeared to
    > install properly and the machine boots into Gnome. The only failure on
    > load I have noticed regards a missing audio mixer.
    >
    > The machine is new but I have successfully installed Mandrake on it
    > previously without a hitch. Well, at least any hitch I noticed.
    >
    > Once up and running RH9, I cannot connect to the network. Ping any
    > machine and I get a "host not responding" message.
    >
    > The NIC lights up and is reported to be active.
    > I have entered the normal static IP and DNS information; I have used
    > this information successfully before with Mandrake and RH 7.2.
    > IP: 192.168.181.4
    > DNS: 192.168.181.3, plus two servers at the ISP.
    > Gateway: 192.168.181.1
    > I left hosts file in the default state from the installer.
    >
    > I selected the Server option in the install as I want to use this
    > machine to test and develop a web app. No other server processes are
    > needed; that is, no pop, ftp, dns. Just sendmail and apache. However, I
    > just followed the installer defaults.
    >
    > There is one server in the net now. 192.168.181.3 is the primary web
    > server, email server, DNS, and Windows Domain Master. Works fine. Runs
    > RH7.x.
    >
    > FWIW, I hacked at gateway and hosts but either got nowhere or scuttled
    > the OS.
    >
    > The machine has two NICs. Both are active. eth0 has the static IP,
    > mentioned above. eth1 is set to use DHCP. When I use eth1 it acquires a
    > valid IP address and dns data.
    >
    > I have read a lot but I still don't get it. Any suggestions would be
    > gratefully accepted.

    Well, just in case some is interested here is the resolution:

    This machine has two nic's. One is a RealTek and the other an Intel
    device.

    I de-activated eth1, made certain eth0 was active and assigned to the
    Intel nic. Double checked the network settings, including this time the
    gateway address and hostname.

    Everything worked fine upon reboot.

    Thanks to those who replied.


  • Next message: Chris: "Update"

    Relevant Pages

    • RE: SBS 2003 R2 - Please Help
      ... computers be slow after you install the full SBS 2003 R2 components. ... log on slow is probably refer to incorrect DNS ... as the DNS server on the clients rather than the ISP DNS servers. ...
      (microsoft.public.windows.server.sbs)
    • Re: Upgrading of 2003 domain to 2008 domain, checklist, questions?
      ... Personally i always use the way of fresh install where possible. ... Exchange 2007 will work in the 2008 domain on a 2003 server. ... On the old server open DNS management console and check that you are running ... you can check the version with "schupgr" in a command prompt. ...
      (microsoft.public.windows.server.setup)
    • Re: where is the outlook 2003 product key on the SBS2003 R2 DVD
      ... dynamic updates and create PTR records in DNS. ... tracking is easier from the server. ... I don't install dhcp on the servers, ... I couldn't get the client to ...
      (microsoft.public.windows.server.sbs)
    • Re: where is the outlook 2003 product key on the SBS2003 R2 DVD
      ... tracking is easier from the server. ... The only time I have seen the connectcomputer error you mentioned about DNS ... I don't install dhcp on the servers, ... I couldn't get the client to ...
      (microsoft.public.windows.server.sbs)
    • Re: Upgrading of 2003 domain to 2008 domain, checklist, questions?
      ... Personally i always use the way of fresh install where possible. ... Exchange 2007 will work in the 2008 domain on a 2003 server. ... On the old server open DNS management console and check that you are running ... and "netshell dhcp restore" command ...
      (microsoft.public.windows.server.setup)