[nflug] pulling computer name from network

[Richard Hubbard]

Roger that.  It was early this morning when when I
answered.  

I think my work network goes by a reservation system,
because if I swap hard drives, it will get the same ip
and the same name, no matter what os i bring up.

but the main point is that this is a server issue at
work, not a client issue that he can replicate at home
unless he creates a similar server environment. Most
dhcp servers can be set up relatively easily to enable
a reservation system, so that every mac address gets
the same ip, which will allow you to do a hosts file
entry in each computer.

or, combine it with your own dns system (tinydns???I
forget the name of the one Carla Shroder advocates for
small networks).
In my case, localhost.localdomain is good enough!
--- Dave Andruczyk <djandruczyk at yahoo.com> wrote:

> 
> 
> --- Richard Hubbard <hubbardr at adelphia.net> wrote:
> 
> > The other part of the equation is that the DHCP
> server at work is 
> > configured to give each machine a name. So you
> plug it in a t work, it 
> > gets a name, at home it doesn't.
> 
> Its probably not exactly that.  It's possible to
> link DHCP and DNS together so
> that when the dhcp server gives out an address it
> registers the name associated
> with that request (whether that name be sent by the
> client to the DHCP server
> during it's request, or if the DHCP server has a
> name for that client (static
> reservation)) with the DNS server.  In many cases
> the previous registration for
> the last client that had that IP address still has a
> DNS record associated with
> it. (because many/most/all admins forget to set the
> DNS expiry time for records
> sent in by DHCP servers) so that previous record
> exists.  Many linux distros
> will do a dns lookup on the IP they are given via
> DHCP and set their local
> hostname to whatever returns from the DNS lookup of
> it's IP address.
> 
> You could verify this by noting the client's current
> IP address, removing that
> client from the LAN, making sure DHCP doesn't have a
> static reservation for
> this client and remove any DNS entries that are
> associated to this client's IP
> address (and flush the DNS cache), change the
> hostname on this client and then
> reboot it on the LAN and see if it is given a new
> hostname (or one at all)
> 
> 
> 
> Dave J. Andruczyk
> 
> 
> 	
> 		
> __________________________________ 
> Yahoo! Mail - PC Magazine Editors' Choice 2005 
> http://mail.yahoo.com
> _______________________________________________
> nflug mailing list
> nflug at nflug.org
> http://www.nflug.org/mailman/listinfo/nflug
> 



		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com
_______________________________________________
nflug mailing list
nflug at nflug.org
http://www.nflug.org/mailman/listinfo/nflug