Re: Nodename issue

From	Michael Moeller <mmoel@t-online.de>
Newsgroups	comp.sys.sun.admin
Subject	Re: Nodename issue
Date	2015-04-08 20:48 +0200
Message-ID	<colbg4FgkueU1@mid.individual.net> (permalink)
References	(4 earlier) <cokh81F9l5iU1@mid.individual.net> <552510b1$0$2945$e4fe514c@news2.news.xs4all.nl> <cokmg7FavnsU1@mid.individual.net> <55252745$0$2854$e4fe514c@news2.news.xs4all.nl> <55256831.609DB804@nomail.com>

Show all headers | View raw

Am 04/08/2015 07:41 PM, schrieb Gary:
> Didn't think of that! Good point. For what it's worth I've encountered the
> same issue on newer versions of Solaris as well. I'll see if I can find time
> to test the change to /etc/default/dhcp on one of my lab boxes.
>
> "Casper H.S. Dik" wrote:
>
>> Michael Moeller <mmoel@t-online.de> writes:
>>
>>> 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.
>>
>> Is it the name returned by DNS?
>>
>> I believe you can remove what the DHCP client asks for by
>> editing /etc/default/dhcp and drop the hostname (param 12)
>>
>> But Solaris 2.6 is, of course, a very old release (end of 1997?)
>> and a lot of things have changed; I also do not have a Solaris 2.6
>> system to check this on.
>>
>> Casper
>
/etc/default/dhcp is called /etc/dhcp/dhcptags on Solais 2.6.
Param 12 deals with the hostname, though. There are some remarks
which strongly discourage messing around with the settings.

Why it worked before I assigned a new address to the router still
is the big question.

Could it be DHCP behaves different on a subnet router compared to
one running PPPoE at the WAN side? Newer machines can handle this
while the Sun can't?


Michael

Back to comp.sys.sun.admin | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

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