On Fri, 2009-06-12 at 19:48 -0500, Mike Hammett wrote: > This laptop used to work fine, now it can't get an IP. Other laptops can. > Ideas?
Some unuseful information removed.... > 19:45:12 system,info log rule changed by admin > 19:45:16 dhcp,debug,packet dhcp1 received discover with id 1455243941 from > 0.0.0.0 > 19:45:16 dhcp,debug,packet chaddr = 00:14:A5:87:C3:B0 > 19:45:16 dhcp,debug,packet Msg-Type = discover > 19:45:16 dhcp,debug,packet Host-Name = "Lothson" The discover packet from C3:B0 > 19:45:17 dhcp,debug,packet dhcp1 sending offer with id 1455243941 to > 172.16.11.60 > 19:45:17 dhcp,debug,packet yiaddr = 172.16.11.60 > 19:45:17 dhcp,debug,packet siaddr = 172.16.11.1 > 19:45:17 dhcp,debug,packet chaddr = 00:14:A5:87:C3:B0 > 19:45:17 dhcp,debug,packet Msg-Type = offer Offering 172.16.11.60 to C3:B0 > 19:45:17 dhcp,debug,packet dhcp1 received request with id 1455243941 from > 0.0.0.0 > 19:45:17 dhcp,debug,packet chaddr = 00:14:A5:87:C3:B0 > 19:45:17 dhcp,debug,packet Msg-Type = request > 19:45:17 dhcp,debug,packet Address-Request = 172.16.11.60 C3:B0 says, give me 172.16.11.60 > 19:45:17 dhcp,info,debug dhcp1 assigned 172.16.11.60 to 00:14:A5:87:C3:B0 Server thinks all is well. > 19:45:17 dhcp,debug,packet dhcp1 sending ack with id 1455243941 to > 172.16.11.60 > 19:45:17 dhcp,debug,packet yiaddr = 172.16.11.60 > 19:45:17 dhcp,debug,packet siaddr = 172.16.11.1 > 19:45:17 dhcp,debug,packet chaddr = 00:14:A5:87:C3:B0 > 19:45:17 dhcp,debug,packet Msg-Type = ack OK, C3:B0, you asked for it...that's acceptable by me. > 19:45:17 dhcp,debug,packet dhcp1 received decline with id 1455243941 from > 0.0.0.0 > 19:45:17 dhcp,debug,packet ciaddr = 172.16.11.60 > 19:45:17 dhcp,debug,packet chaddr = 00:14:A5:87:C3:B0 > 19:45:17 dhcp,debug,packet Msg-Type = decline C3:B0..."Now that I think about it, never mind. I don't like that address after all." > 19:45:17 dhcp,info,debug dhcp1 deassigned 172.16.11.60 from 00:14:A5:87:C3:B0 Server: Ok, you don't want it, I'll take it back. This conversation is common. It almost always means that the PC thinks (erroneously, perhaps) that the IP being assigned by DHCP is already in use on the network. I'd bet that if you ran a sniffer on the PC, you'd see an ARP request go out to the network immediately following the DHCP ACK packet with an answer coming back from someone. That's why Windows is declining the IP. NOW, for reasons: 1. There is an 802.11 client bridge in the path somewhere between this PC and the DHCP server. This can often spell problems. 2. There is some device on the network running proxy-arp and is misbehaving. 3. Windows is just being Windows. Always a fun possibility. -- ******************************************************************** * Butch Evans * Professional Network Consultation* * http://www.butchevans.com/ * Network Engineering * * http://www.wispa.org/ * WISPA Board Member * * http://blog.butchevans.com/ * Wired or Wireless Networks * ******************************************************************** _______________________________________________ Mikrotik mailing list Mikrotik@mail.butchevans.com http://www.butchevans.com/mailman/listinfo/mikrotik Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
