Re: install fedora 3 over lan ftp or nfs not seen by the client machine

From: Tim (tim_at_mail.localhost.invalid)
Date: 04/21/05 

Date: Thu, 21 Apr 2005 21:03:21 +0930

nntp_usr <urjunkhere@foobar.nit> posted:

> The correct driver is assigned the network adapter, per the control-alt
> F3 terminal.

You'd hope so, though I've had some grief trying to get a network install
to run through an RTL8139 chipset LAN NIC. The NIC works, is supported by
Linux, but the install routine seems finicky.

> I used the "boot.img" from the DVD. The image gets me through to picking
> a language, assigning an IP to the client.

Which would sound like you have the right one, then.

> I tried the DNS entry of the lan, but that doesn't work either.

You tried what for what purpose? DNS = "domain name system". Did you try
accessing something using a domain name? Did you type in the IP address
of your DNS server? I'm not sure what you're doing.

> Nevertheless, the client machine to-get-the-install should not even try
> to use DNS, it seems to me, as I provide all the information myself,
> not relying on DNS. Yet the installer insists on locating host name /
> IP.

My experience with network installlations goes along these lines:

I might let the installer configure the network settings on the machine to
be installed to using DHCP. My LAN's DHCP daemon will configure it with
an IP, a host address, a hostname, and tell it the IP addresses to use for
this LAN's DNS server.

Or, I manually type in an IP address for the computer being installed to,
a netmask, a hostname for this computer, then DNS server and gateway IP
addresses.

When I get to asking where to fetch the install files from, I can either
type in the server location using its IP address (and no DNS lookups will
be needed), or I can enter in a server hostname (and DNS lookups will be
used to find the IP address for that hostname). Either way, about all
that's left is the path to the install files.

I stuck to using HTTP or NFS, since I already had those services running
smoothly. I've not done much tinkering with FTP and don't have an FTP
server up and running on my LAN.

What files are you serving? The DVD itself? Copies of the files from it
on a hard drive?

> The output is: transering ftp://x.x.x.x/pub/rh/Fedora/base/netstg2.img to
> a fd

What's "fd"? 

-- 
If you insist on e-mailing me, use the reply-to address (it's real but
temporary).  But please reply to the group, like you're supposed to. 
This message was sent without a virus, please delete some files yourself.

Relevant Pages

  • Re: Preparing network connection after AD install
    ... I didn't install exchange yet. ... known symptoms of having exchange installed on DC and bad DNS ... Do not place the ISP DNS server or any other DNS on the ...
    (microsoft.public.windows.server.active_directory)
  • Re: Preparing network connection after AD install
    ... only reason I installed active directory is because when I tried to install exchnage on that machine it told me it was required. ... So I just want the minimal required to run exchange. ... Are all known symptoms of having exchange installed on DC and bad DNS configuration. ... Do not place the ISP DNS server or any other DNS on the client or DNS Server NIC properties, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Migrate from NT to Win2K3 question
    ... DNS server is my old DNS server which running on a Win NT platform. ... created a primary zone "int.abc.com" under Forward Lookup Zone. ... do I also know install DNS and WINS. ...
    (microsoft.public.windows.server.migration)
  • Re: Preparing network connection after AD install
    ... My win2k3 machine which I want to install exchange on thus am installing ... the DNS setting is set to. ... -Make sure that each DNS server points to itself under NIC preferred DNS. ... client or DNS Server NIC properties, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Domain users
    ... for the DNS Server. ... User in the Domain and an Administrator in Windows XP still has all its ... > "George Hester" wrote in message ... >>> As a regular user they will not be able to install much of anything. ...
    (microsoft.public.win2000.group_policy)