+ Responder ao Tópico



  1. Ola a todos, estou tendo o seguinte problema: De uns tempos pra ca, os computadores não conseguem mais encontrar a rede se eu deixo como ip-dinamico. Se eu coloco como ip estático, a rede é encontrada na hora. De uns tempos pra ca, cada vez mais computadores estão tendo esse problema. A maioria das estações é windows xp. Preciso de ajuda...

    Renato

  2. Especifique "achar a rede".....

    Já verificou mascara, gataway e dns? do dhcp?



  3. Sim, parece que esta tudo correto, com exceção da hora do servidor que estava adiantada uma hora (ja consertei). Mas hoje, estava analizando os logs do /var/log/messages e me aparece as seguintes mensagens com alguns erros, porém, nao consegui entender o que eles significam. Preciso de ajuda.

    [root@storage ~]# tail -70 /var/log/messages
    Mar 21 09:24:07 storage dhcpd: DHCPDISCOVER from 00:0f:ea:22:c1:92 (renato) via eth0
    Mar 21 09:24:07 storage dhcpd: DHCPOFFER on 192.168.7.69 to 00:0f:ea:22:c1:92 (renato) via eth0
    Mar 21 09:24:07 storage dhcpd: DHCPDISCOVER from 00:0f:ea:22:c1:92 (renato) via eth0
    Mar 21 09:24:07 storage dhcpd: DHCPOFFER on 192.168.7.69 to 00:0f:ea:22:c1:92 (renato) via eth0
    Mar 21 09:24:10 storage dhcpd: DHCPDISCOVER from 00:0f:ea:22:c1:92 (renato) via eth0
    Mar 21 09:24:10 storage dhcpd: DHCPOFFER on 192.168.7.69 to 00:0f:ea:22:c1:92 (renato) via eth0
    Mar 21 09:24:18 storage dhcpd: DHCPDISCOVER from 00:0f:ea:22:c1:92 (renato) via eth0
    Mar 21 09:24:18 storage dhcpd: DHCPOFFER on 192.168.7.69 to 00:0f:ea:22:c1:92 (renato) via eth0
    Mar 21 09:24:18 storage dhcpd: DHCPREQUEST for 192.168.7.69 (192.168.7.11) from 00:0f:ea:22:c1:92 (renato) via eth0
    Mar 21 09:24:18 storage dhcpd: DHCPACK on 192.168.7.69 to 00:0f:ea:22:c1:92 (renato) via eth0
    Mar 21 09:24:20 storage dhcpd: DHCPINFORM from 192.168.7.69 via eth0: not authoritative for subnet 192.168.7.0
    Mar 21 09:24:20 storage dhcpd: If this DHCP server is authoritative for that subnet,
    Mar 21 09:24:20 storage dhcpd: please write an `authoritative;' directive either in the
    Mar 21 09:24:20 storage dhcpd: subnet declaration or in some scope that encloses the
    Mar 21 09:24:20 storage dhcpd: subnet declaration - for example, write it at the top
    Mar 21 09:24:20 storage dhcpd: of the dhcpd.conf file.
    Mar 21 09:24:23 storage dhcpd: DHCPINFORM from 192.168.7.69 via eth0: not authoritative for subnet 192.168.7.0
    Mar 21 09:24:31 storage dhcpd: DHCPREQUEST for 192.168.7.69 from 00:0f:ea:22:c1:92 (renato) via eth0
    Mar 21 09:24:31 storage dhcpd: DHCPACK on 192.168.7.69 to 00:0f:ea:22:c1:92 (renato) via eth0
    Mar 21 09:24:48 storage sshd(pam_unix)[5873]: authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.7.69 user=root
    Mar 21 09:25:08 storage sshd(pam_unix)[5873]: 1 more authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.7.69 user=root
    Mar 21 09:25:53 storage sshd(pam_unix)[5878]: session opened for user root by root(uid=0)
    Mar 21 09:27:28 storage sshd(pam_unix)[5916]: session opened for user root by root(uid=0)
    Mar 21 09:30:01 storage crond(pam_unix)[5953]: session opened for user root by (uid=0)
    Mar 21 09:30:01 storage crond(pam_unix)[5953]: session closed for user root
    Mar 21 09:31:55 storage smbd[5960]: [2007/03/21 09:31:55, 0] lib/util_sock.c:get_peer_addr(1000)
    Mar 21 09:31:55 storage smbd[5960]: getpeername failed. Error was Ponto final de transporte não está conectado
    Mar 21 09:31:55 storage smbd[5960]: [2007/03/21 09:31:55, 0] lib/access.c:check_access(328)
    Mar 21 09:31:55 storage smbd[5960]: [2007/03/21 09:31:55, 0] lib/util_sock.c:get_peer_addr(1000)
    Mar 21 09:31:55 storage smbd[5960]: getpeername failed. Error was Ponto final de transporte não está conectado
    Mar 21 09:31:55 storage smbd[5960]: Denied connection from (0.0.0.0)
    Mar 21 09:31:55 storage smbd[5960]: [2007/03/21 09:31:55, 0] lib/util_sock.c:write_socket_data(430)
    Mar 21 09:31:55 storage smbd[5960]: write_socket_data: write failure. Error = Conexão fechada pela outra ponta
    Mar 21 09:31:55 storage smbd[5960]: [2007/03/21 09:31:55, 0] lib/util_sock.c:write_socket(455)
    Mar 21 09:31:55 storage smbd[5960]: write_socket: Error writing 5 bytes to socket 22: ERRNO = Conexão fechada pela outra ponta
    Mar 21 09:31:55 storage smbd[5960]: [2007/03/21 09:31:55, 0] lib/util_sock.c:send_smb(647)
    Mar 21 09:31:55 storage smbd[5960]: Error writing 5 bytes to client. -1. (Conexão fechada pela outra ponta)
    Mar 21 09:34:23 storage dhcpd: DHCPREQUEST for 192.168.7.69 from 00:0f:ea:22:c1:92 (renato) via eth0
    Mar 21 09:34:23 storage dhcpd: DHCPACK on 192.168.7.69 to 00:0f:ea:22:c1:92 (renato) via eth0
    Mar 21 09:35:18 storage dhcpd: DHCPREQUEST for 192.168.7.24 from 00:e0:7d:cd:49:65 (jonaina) via eth0
    Mar 21 09:35:18 storage dhcpd: DHCPACK on 192.168.7.24 to 00:e0:7d:cd:49:65 (jonaina) via eth0
    Mar 21 09:38:13 storage smbd[5966]: [2007/03/21 09:38:13, 0] lib/util_sock.c:get_peer_addr(1000)
    Mar 21 09:38:13 storage smbd[5966]: getpeername failed. Error was Ponto final de transporte não está conectado
    Mar 21 09:38:13 storage smbd[5966]: [2007/03/21 09:38:13, 0] lib/util_sock.c:get_peer_addr(1000)
    Mar 21 09:38:13 storage smbd[5966]: getpeername failed. Error was Ponto final de transporte não está conectado
    Mar 21 09:38:13 storage smbd[5966]: [2007/03/21 09:38:13, 0] lib/access.c:check_access(328)
    Mar 21 09:38:13 storage smbd[5966]: [2007/03/21 09:38:13, 0] lib/util_sock.c:get_peer_addr(1000)
    Mar 21 09:38:13 storage smbd[5966]: getpeername failed. Error was Ponto final de transporte não está conectado
    Mar 21 09:38:13 storage smbd[5966]: Denied connection from (0.0.0.0)
    Mar 21 09:38:13 storage smbd[5966]: [2007/03/21 09:38:13, 0] lib/util_sock.c:write_socket_data(430)
    Mar 21 09:38:13 storage smbd[5966]: write_socket_data: write failure. Error = Conexão fechada pela outra ponta
    Mar 21 09:38:13 storage smbd[5966]: [2007/03/21 09:38:13, 0] lib/util_sock.c:write_socket(455)
    Mar 21 09:38:13 storage smbd[5966]: write_socket: Error writing 5 bytes to socket 22: ERRNO = Conexão fechada pela outra ponta
    Mar 21 09:38:13 storage smbd[5966]: [2007/03/21 09:38:13, 0] lib/util_sock.c:send_smb(647)
    Mar 21 09:38:13 storage smbd[5966]: Error writing 5 bytes to client. -1. (Conexão fechada pela outra ponta)
    Mar 21 09:38:47 storage sshd(pam_unix)[5970]: session opened for user root by root(uid=0)
    Mar 21 09:40:01 storage crond(pam_unix)[6004]: session opened for user root by (uid=0)
    Mar 21 09:40:01 storage crond(pam_unix)[6004]: session closed for user root
    Mar 21 09:40:27 storage dhcpd: DHCPDISCOVER from 00:08:54:2b:f6:3d via eth0
    Mar 21 09:40:28 storage dhcpd: DHCPOFFER on 192.168.7.39 to 00:08:54:2b:f6:3d (Mauro) via eth0
    Mar 21 09:40:31 storage dhcpd: DHCPDISCOVER from 00:08:54:2b:f6:3d (Mauro) via eth0
    Mar 21 09:40:31 storage dhcpd: DHCPOFFER on 192.168.7.39 to 00:08:54:2b:f6:3d (Mauro) via eth0
    Mar 21 09:40:40 storage dhcpd: DHCPDISCOVER from 00:08:54:2b:f6:3d (Mauro) via eth0
    Mar 21 09:40:40 storage dhcpd: DHCPOFFER on 192.168.7.39 to 00:08:54:2b:f6:3d (Mauro) via eth0
    Mar 21 09:40:40 storage dhcpd: DHCPREQUEST for 192.168.7.39 (192.168.7.11) from 00:08:54:2b:f6:3d (Mauro) via eth0
    Mar 21 09:40:40 storage dhcpd: DHCPACK on 192.168.7.39 to 00:08:54:2b:f6:3d (Mauro) via eth0
    Mar 21 09:40:42 storage dhcpd: DHCPREQUEST for 192.168.7.39 from 00:08:54:2b:f6:3d (Mauro) via eth0
    Mar 21 09:40:42 storage dhcpd: DHCPACK on 192.168.7.39 to 00:08:54:2b:f6:3d (Mauro) via eth0
    Mar 21 09:43:07 storage dhcpd: DHCPREQUEST for 192.168.7.39 from 00:08:54:2b:f6:3d (Mauro) via eth0
    Mar 21 09:43:07 storage dhcpd: DHCPACK on 192.168.7.39 to 00:08:54:2b:f6:3d (Mauro) via eth0
    [root@storage ~]#

  4. Certo, isso significa que seu dhcp server não está rodando como authoritative, ou seja, ele não dá a resposta ao cliente informando que de fato ele é o servidor dhcp correto.

    Esse tipo de erro (clientes não pegando IP) acontece muito quando o servidor não roda em authoritative porque como ele nao recebe o NAK do dhcpd ele espera o lease anterior expirar. Demora bastante tempo pra ele expirar e por isso os erros são crescentes.

    A solução eu diria que basta fazer o que o próprio log diz, adicione:

    "authoritative;"

    No começo do arquivo dhcpd.conf






Tópicos Similares

  1. Possível problema com dhcp ?
    Por Dedao no fórum Servidores de Rede
    Respostas: 5
    Último Post: 29-06-2007, 11:42
  2. Problema com DHCP ou DNS cliente!
    Por Rogerioc no fórum Servidores de Rede
    Respostas: 1
    Último Post: 28-11-2004, 06:26
  3. Possível problema com roteamento em um gateway
    Por André L. Melim no fórum Servidores de Rede
    Respostas: 9
    Último Post: 17-05-2004, 10:54
  4. Problema com DHCP e Linux
    Por no fórum Servidores de Rede
    Respostas: 1
    Último Post: 11-06-2003, 12:47
  5. problemas com dhcp no redhat 8
    Por no fórum Servidores de Rede
    Respostas: 0
    Último Post: 08-04-2003, 07:17

Visite: BR-Linux ·  VivaOLinux ·  Dicas-L