Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.sun.admin > #237

Re: Nodename issue

Show all headers | View raw

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.


Michael


Am 04/08/2015 01:05 AM, schrieb Gary:
> I think you're up against the DHCP server renaming the box. I've
> never had good luck with DHCP. You might see if you can configure
> the DHCP server with a reserved name and IP for your MAC. Other
> than that, reserve the MAC/IP in the DHCP server and set a static
> IP on the Sun.
>
> mmoel wrote:
>
>> Thats what I expected to work too. After reboot
>> the entry always is reset to 'new-host-3' by the
>> system.
>> A comparison with a backup of /etc shows that any
>> occurence of the workstations given name now has
>> changed to 'new-host-3', except in file 'nodename'.
>>
>> Michael
>>
>> On Tue, 7 Apr 2015, Bruce Esquibel wrote:
>>
>>> Michael Moeller <mmoel@t-online.de> wrote:
>>>> Hi,
>>>
>>>> in the course of a network expansion I had to connect an SS5,
>>>> Sol 2.6, to a new subrouter.
>>>
>>>> Oddly enough, a first trial using 'route add default <NEW IP>'
>>>> followed by 'ifconfig le0 auto-dhcp' failed, so I changed the
>>>> routers address in /etc/defaultrouter and did a reboot.
>>>
>>>> This worked but the machine changed its name to 'new-host-3',
>>>> which is undesirable. /etc/nodename still contains the right
>>>> name, though.
>>>
>>>> Where do I miss something?
>>>
>>> My WAG is /etc/hosts
>>>
>>> Something like:
>>>
>>> 192.168.1.123 whatever.domain.com   whatever
>>>
>>> with the IP address of the machine should fix it using 2.6.
>>>
>>> -bruce
>>> bje@ripco.com
>>>
>

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