2 votos

chrwahl avatar

El nombre del host local cambia cada pocos segundos cuando NO está conectado a una red

Preguntado el 12 de Agosto, 2014
Cuando se hizo la pregunta
3161 visitas
Cuantas visitas ha tenido la pregunta
2 Respuestas
Cuantas respuestas ha tenido la pregunta
Abierta
Estado actual de la pregunta

Cada vez que despierto mi portátil, pero antes de conectarme a una red, recibo mensajes similares a los siguientes:

This computer's local hostname
"sojourner-896.local" is already in use on
this network. The name has been changed
to "sojourner-972.local"

Si no me conecto a una red y no hago clic en el botón "OK", los nombres de host siguen aumentando. Si me conecto a una red (ya sea con cable o inalámbrica), los nombres dejan de incrementarse.

Reajusto el nombre del host en el panel de preferencias de "Compartir" cuando los nombres de host están en el rango de 5.000 - 6.000 (cada 2-3 días).

¿Alguna idea de qué podría estar causando esto?

Preguntado el 12 de Agosto, 2014 por chrwahl

0 votos

Avatar de Steve Chambers

Este puede ser un duplicado de este hilo: apple.stackexchange.com/questions/125411/

Comentado el 12 de Agosto, 2014 por Steve Chambers

1 votos

Avatar de chrwahl

@SteveChambers Las preguntas anteriores que había visto, tanto en este sitio como en los resultados de Google, implicaban que el ordenador estaba conectado en varias ocasiones a la misma red a través de Ethernet e inalámbrica. Este problema sólo se produce en mi Laptop cuando estoy no conectado a una red. En cuanto me conecto a una red, el nombre deja de incrementarse.

Comentado el 13 de Agosto, 2014 por chrwahl

Respuestas

¿Demasiados anuncios?

1voto

chrwahl avatar
chrwahl Puntos 1

Miré en los registros a través de la aplicación de la consola y encontré que los siguientes registros se generan cada vez que me desconecto de una red:

8/29/14 10:07:59.087 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7647.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:07:59.087 PM mDNSResponder[414]: mDNSCoreReceiveResponse: ProbeCount 2; will deregister    4 sojourner-7647.local. Addr 127.0.0.1
8/29/14 10:07:59.087 PM mDNSResponder[414]: Local Hostname sojourner-7647.local already in use; will try sojourner-7743.local instead
8/29/14 10:08:00.923 PM mDNSResponder[414]: Name Conflict: Updated Local Hostname from "sojourner-7647.local" to "sojourner-7743.local"
8/29/14 10:08:00.944 PM configd[26]: setting hostname to "sojourner-7743.local"
8/29/14 10:08:02.145 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7743.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:02.145 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:    4 sojourner-7743.local. Addr 127.0.0.1
8/29/14 10:08:02.145 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7743.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:02.146 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:   16 sojourner-7743.local. AAAA FE80:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:02.456 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7743.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:02.457 PM mDNSResponder[414]: mDNSCoreReceiveResponse: ProbeCount 2; will deregister    4 sojourner-7743.local. Addr 127.0.0.1
8/29/14 10:08:02.457 PM mDNSResponder[414]: Local Hostname sojourner-7743.local already in use; will try sojourner-7765.local instead
8/29/14 10:08:04.365 PM mDNSResponder[414]: Name Conflict: Updated Local Hostname from "sojourner-7743.local" to "sojourner-7765.local"
8/29/14 10:08:04.375 PM configd[26]: setting hostname to "sojourner-7765.local"
8/29/14 10:08:04.633 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   22 1.0.0.127.in-addr.arpa. PTR sojourner-7743.local.
8/29/14 10:08:04.633 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Unexpected conflict discarding   22 1.0.0.127.in-addr.arpa. PTR sojourner-7765.local.
8/29/14 10:08:04.734 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   22 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR sojourner-7743.local.
8/29/14 10:08:04.734 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Unexpected conflict discarding   22 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR sojourner-7765.local.
8/29/14 10:08:05.839 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7765.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:05.840 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:    4 sojourner-7765.local. Addr 127.0.0.1
8/29/14 10:08:05.840 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7765.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:05.840 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:   16 sojourner-7765.local. AAAA FE80:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:06.141 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7765.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:06.141 PM mDNSResponder[414]: mDNSCoreReceiveResponse: ProbeCount 2; will deregister    4 sojourner-7765.local. Addr 127.0.0.1
8/29/14 10:08:06.141 PM mDNSResponder[414]: Local Hostname sojourner-7765.local already in use; will try sojourner-7802.local instead
8/29/14 10:08:08.006 PM mDNSResponder[414]: Name Conflict: Updated Local Hostname from "sojourner-7765.local" to "sojourner-7802.local"
8/29/14 10:08:08.016 PM configd[26]: setting hostname to "sojourner-7802.local"
8/29/14 10:08:08.268 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   22 1.0.0.127.in-addr.arpa. PTR sojourner-7765.local.
8/29/14 10:08:08.268 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Unexpected conflict discarding   22 1.0.0.127.in-addr.arpa. PTR sojourner-7802.local.
8/29/14 10:08:08.357 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   22 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR sojourner-7765.local.
8/29/14 10:08:08.357 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Unexpected conflict discarding   22 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR sojourner-7802.local.
8/29/14 10:08:09.465 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7802.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:09.465 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:    4 sojourner-7802.local. Addr 127.0.0.1
8/29/14 10:08:09.465 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7802.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:09.465 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:   16 sojourner-7802.local. AAAA FE80:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:09.733 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7802.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:09.733 PM mDNSResponder[414]: mDNSCoreReceiveResponse: ProbeCount 2; will deregister    4 sojourner-7802.local. Addr 127.0.0.1
8/29/14 10:08:09.733 PM mDNSResponder[414]: Local Hostname sojourner-7802.local already in use; will try sojourner-7837.local instead
8/29/14 10:08:11.578 PM mDNSResponder[414]: Name Conflict: Updated Local Hostname from "sojourner-7802.local" to "sojourner-7837.local"
8/29/14 10:08:11.588 PM configd[26]: setting hostname to "sojourner-7837.local"
8/29/14 10:08:11.815 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   22 1.0.0.127.in-addr.arpa. PTR sojourner-7802.local.
8/29/14 10:08:11.815 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Unexpected conflict discarding   22 1.0.0.127.in-addr.arpa. PTR sojourner-7837.local.
8/29/14 10:08:11.915 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   22 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. PTR sojourner-7802.local.
8/29/14 10:08:11.915 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Unexpected conflict discarding   22 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. PTR sojourner-7837.local.
8/29/14 10:08:12.786 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7837.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:12.786 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:    4 sojourner-7837.local. Addr 127.0.0.1
8/29/14 10:08:12.786 PM mDNSResponder[414]: Excessive name conflicts (17) for sojourner-7837.local. (Addr); rate limiting in effect
8/29/14 10:08:12.786 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Received from 127.0.0.1:5353   16 sojourner-7837.local. AAAA 0000:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:12.786 PM mDNSResponder[414]: mDNSCoreReceiveResponse: Resetting to Probing:   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:0000:0000:0000:0001
8/29/14 10:08:12.786 PM mDNSResponder[414]: Excessive name conflicts (18) for sojourner-7837.local. (AAAA); rate limiting in effect
8/29/14 10:08:14.193 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:14.194 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:14.497 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:14.497 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:14.914 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:14.914 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:14.914 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:14.914 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:14.915 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:14.915 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:14.915 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:14.915 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:15.504 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.504 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:15.504 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.504 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:15.504 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.505 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:15.505 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.505 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:15.911 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:16.212 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:16.213 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:16.213 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:16.213 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:16.213 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:16.213 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 8323688E   16 sojourner-7837.local. AAAA FE80:0000:0000:0000:2CBE:08FF:FE8F:BCBA
8/29/14 10:08:16.213 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Pkt Record:        00004008    4 sojourner-7837.local. NSEC Addr
8/29/14 10:08:16.213 PM mDNSResponder[414]: ResolveSimultaneousProbe: 000000000000000A Our Record 3 lost: 002B5510    4 sojourner-7837.local. Addr 172.20.10.2
8/29/14 10:08:19.916 PM digest-service[701]: digest-request: init return domain: SOJOURNER-7647 server: SOJOURNER-7837 indomain was: <NULL>
8/29/14 10:08:19.937 PM digest-service[701]: digest-request: init return domain: SOJOURNER-7837 server: SOJOURNER-7837 indomain was: <NULL>

Volví a activar la red alrededor de las segundas 10:08:14.

El proceso real que estaba cambiando el nombre del host es configd . El hombre página para configd afirma que

The configd daemon is responsible for many configuration aspects of the
local system. configd maintains data reflecting the desired and current
state of the system, provides notifications to applications when this data
changes, and hosts a number of configuration agents in the form of loadable
bundles.

y

At the present time, the majority of the configuration agents (or bundles)
hosted by configd are used to establish and maintain the network
configuration.

Las páginas del hombre enumeran los siguientes archivos relacionados:

 /Library/Preferences/SystemConfiguration/preferences.plist
 /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist
 /Library/Preferences/SystemConfiguration/VirtualNetworkInterfaces.plist

El archivo preferences.plist parece tener las preferencias de red especificadas por el panel de preferencias de red en Preferencias del sistema. Hice una copia de seguridad, la borré, maté configd y realizó un reinicio de bajo nivel:

cd /Library/Preferences/SystemConfiguration/
cp preferences.plist ~/Desktop/preferences.plist
sudo rm -f preferences.plist
sudo killall configd
sudo killall configd
sudo reboot

Después de que el sistema se reinició, el sistema ya no cambió el nombre del host cada pocos segundos cuando NO conectado a una red.

Respondido el 30 de Agosto, 2014 por chrwahl (1 Puntos )

0voto

Steve Chambers avatar
Steve Chambers Puntos 5054

Mientras estaba husmeando, encontré un hilo en el Superusuario que podría ser de ayuda.

https://superuser.com/questions/49891/how-can-i-stop-mac-os-x-overriding-my-hostname-when-i-receive-a-dhcp-request-on

Es muy extraño que esto suceda cuando NO estás conectado a una red, desearía tener una mejor respuesta.

Creo recordar una preferencia enterrada en algún lugar de las Preferencias del Sistema que permite al Mac obtener un nombre de host dinámico del servidor DHCP, pero por mi vida no puedo encontrar el maldito escenario. Así que o estoy recordando mal o eso fue algo de una encarnación anterior de un gatito.

Respondido el 13 de Agosto, 2014 por Steve Chambers (5054 Puntos )

Preguntas relacionadas

Preguntas Destacadas

Etiquetas mas usadas

En nuestra red

AppleAyuda.com

AppleAyuda es una comunidad de usuarios de los productos de Apple en la que puedes resolver tus problemas y dudas.
Puedes consultar las preguntas de otros usuarios, hacer tus propias preguntas o resolver las de los demás.

Powered by:

Yandex
X