Groups | Search | Server Info | Keyboard shortcuts | Login | Register
Groups > comp.sys.sun.admin > #241
| Message-ID | <552566E3.473AF032@nomail.com> (permalink) |
|---|---|
| Date | 2015-04-08 13:35 -0400 |
| From | Gary <nobody@nomail.com> |
| Newsgroups | comp.sys.sun.admin |
| Subject | Re: Nodename issue |
| References | (2 earlier) <Pine.GSO.4.64.1504071531220.423@new-host-3> <552462AC.AD63534C@nomail.com> <cokh81F9l5iU1@mid.individual.net> <552510b1$0$2945$e4fe514c@news2.news.xs4all.nl> <cokmg7FavnsU1@mid.individual.net> |
I've never had good luck using DHCP with Suns. I think what happens is after the RARP from the DHCP server the sun does an nslookup on its IP and takes that as its name. The best I've ever been able to come up with is reserving the MAC/IP in the DHCP server and doing static on the Sun. That means you'll also need to setup the DNS server info on the Sun as well, as that is normally passed from the DHCP server. (As is the default route). The servers I've managed were always placed in a reserved range on the DHCP server. That was since they were offering various services, clients needed a stable name/IP to access them. We also always had DNS A records set accordingly. Michael Moeller wrote: > Am 04/08/2015 01:27 PM, schrieb Casper H.S. Dik: > > Michael Moeller <mmoel@t-online.de> writes: > > > >> Some PCs and Macs are connected to this router without any > >> problems and until last week it worked with the Sun too. > >> Giving the router another IP is no reason for silently renaming > >> the Sun. Maybe thats an uninformed assumption but I'd rather > >> presume I triggered this behaviour on the client side somehow. > >> If I can't figure out whats going on I'll have to try the > >> static IP. Thanks. > > > > This is likely caused because the new nodename is what is define > > in DNS. When a system is configured to use DHCP, it likely gets > > all information including the hostname from the DHCP server. > > > > Casper > > > > Perhaps it's important to say the server is a Cisco business router. > Afaik it doesn't care about the clients names and I changed them at > times without difficulty. Since it worked before the fault is likely > to be client sided. None of the other machines names were altered by > DHCP. > > To come a little closer to a solution let me put it another way: > Is it under my control at all (regrading a client on a Sun Sparc, > Sol 2.6) whether the server overrides the clients hostname or not? > And if so, whats the right course of action in the respective case? > I didn't find something useful in the documentation, so far. > > Michael
Back to comp.sys.sun.admin | Previous | Next — Previous in thread | Find similar
Nodename issue Michael Moeller <mmoel@t-online.de> - 2015-04-06 14:23 +0200
Re: Nodename issue Bruce Esquibel <bje@ripco.com> - 2015-04-07 12:31 +0000
Re: Nodename issue mmoel <mic1@t-online.de> - 2015-04-07 15:48 +0200
Re: Nodename issue Gary <nobody@nomail.com> - 2015-04-07 19:05 -0400
Re: Nodename issue Michael Moeller <mmoel@t-online.de> - 2015-04-08 13:20 +0200
Re: Nodename issue Casper H.S. Dik <Casper.Dik@OrSPaMcle.COM> - 2015-04-08 11:27 +0000
Re: Nodename issue Michael Moeller <mmoel@t-online.de> - 2015-04-08 14:50 +0200
Re: Nodename issue Casper H.S. Dik <Casper.Dik@OrSPaMcle.COM> - 2015-04-08 13:04 +0000
Re: Nodename issue Gary <nobody@nomail.com> - 2015-04-08 13:41 -0400
Re: Nodename issue Michael Moeller <mmoel@t-online.de> - 2015-04-08 20:48 +0200
Re: Nodename issue Casper H.S. Dik <Casper.Dik@OrSPaMcle.COM> - 2015-04-08 21:40 +0000
Re: Nodename issue Michael Moeller <mmoel@t-online.de> - 2015-04-09 12:24 +0200
Re: Nodename issue Gary <nobody@nomail.com> - 2015-04-09 06:32 -0400
Re: Nodename issue Michael Moeller <mmoel@t-online.de> - 2015-04-09 12:43 +0200
Re: Nodename issue Michael Moeller <mmoel@t-online.de> - 2015-04-09 12:34 +0200
Re: Nodename issue Casper H.S. Dik <Casper.Dik@OrSPaMcle.COM> - 2015-04-09 11:27 +0000
Re: Nodename issue Michael Moeller <mmoel@t-online.de> - 2015-04-09 14:21 +0200
Re: Nodename issue Casper H.S. Dik <Casper.Dik@OrSPaMcle.COM> - 2015-04-09 12:48 +0000
Re: Nodename issue Michael Moeller <mmoel@t-online.de> - 2015-04-09 16:13 +0200
Re: Nodename issue Gary <nobody@nomail.com> - 2015-04-08 13:35 -0400
csiph-web