Given that you have 4 machines set up to get their IP allocations via DHCP,
you must have initially contact the ISP and asked for 4 or 5 ip's.
SOME ISP's allocate IP's based upon the machines NAME...
Let's say you have a LAN with 9 computers, but the ISP is only giving you 5
IP's...
In this case they would tell you to set the NAME of your computer to
something they know (or is in their database...) I.E.
ic-connect-@home-20322 ic-connect-@home-2033, etc.
In a situation such as this, you must set your Linux box up to utilize the
same hostname and domain as your ISP is expecting. In this manner your DHCP
client will be understood, and it will get an IP address...
You might want to refer to the @home DSL/CABLE howtos which discuss this in
detail.
-JMS
> -----Original Message-----
> From: Rick Commo [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, February 04, 2001 12:28 PM
> To: Newbie
> Cc: [EMAIL PROTECTED]
> Subject: RE: [newbie] LAN settings - (was: Setting up NIC under 7.2)
>
> Jose,
>
> Thanks. Yes, I had rebooted. I still have to do some more playing
> around. My knowledge in this whole area is just generally rather weak. I
> would have presumed that the LinkSys actually provided the DNS server
> names once it got them from Verizon, my ISP.
>
> Currently I have all my machines (a whopping 4, including my laptop) set
> for DHCP so creating a hosts file is somewhat problematic unless there are
> some hosts semantics that I am not aware of.
>
> If it becomes too painful I will supply static IPs to all but the laptop.
> The laptop has to span 3 different environments and DHCP is required in 2
> out the 3.
>
> Cheers,
> -rick
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, February 04, 2001 1:32 AM
> To: [EMAIL PROTECTED]; Newbie
> Subject: RE: [newbie] LAN settings - (was: Setting up NIC under 7.2)
>
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, February 04, 2001 3:43 AM
> To: Newbie
> Subject: RE: [newbie] LAN settings - (was: Setting up NIC under 7.2)
>
> Figured it out after a bit. Either the mainboard has a bad PCI slot or
> the NIC was not seated properly. More likely the latter. I moved it to
> another slot and that made it happy. I will try moving it back to the
> original slot at some point in future.
>
> On to the next questions.
>
> The network here consists of a DSL modem into a LinkSys Router/Switch. I
> set eth0 up for DHCP and that seems to work, but I had to set the DNS
> manually. Is this normal?
> [|JMS> ]
>
> Have you rebooted?
>
> If you configured your eth0 card for dhcp address allocation, you might
> have to reboot to get DNS info from your ISP.
>
> Some ISP's DHCP servers may also not be configured to provide this
> information to your machine.
>
> Watch your machine's hostname after a reboot. If it changes to something
> you did not type in, your ISP is providing info...
>
> ---
>
>
> My reason for asking is that my Win2K box is set up for DHCP and as part
> of getting its address it also gets the gateway and DNS addresses as well.
> So I did an ipconfig/all on the Win2K box as a quick and dirty way to
> print out the DNS servers.
>
> [|JMS> ] See above
>
> ----
>
> Is it necessary to have a fully qualified domain when the machine is
> behind a router and part of a private network? I can resolve names "out
> there" on the other side of the router, but my Linux box can't resolve the
> name of my Win2K box and they are both on the same subnet.
>
> [|JMS> ]
>
> Yes and no.
>
> Your Linux machine has to "know" about machines on your private lan. How
> you go about this is up to you. /etc/hosts is the quick and dirty way for
> small LANs. DNS/BIND with the DHCP update script is much more elegant.
>
> Until you set up one or the other, Linux will not know about your other
> machines. For that matter Windows doesn't either.
>
> Remember your ISP's DNS can't "see" your private LAN, so Linux has no way
> of obtaining HOST information unless you set something up.
>
>
> [|JMS> ] -JMS
>
winmail.dat
