WRT54g Ver 2.2 DHCPNACK

Discussion in 'Cisco/Linksys Wireless Routers' started by csilano, Mar 23, 2005.

  1. csilano

    csilano Network Guru Member

    to all!
    I am new to this forum and I have an issue I hope you can help me solve. I recently purchased a Wrt54g an loaded the latest linksys firmware on it 3.03.6. After most pc reboots or when the lease is up I receive an error in my event log. Event ID 1002 Source DHCP. The error basically states the DHCP server 192.168.1.1 (Router) issued a DHCPNACK for the workststion 192.168.1.101 (my pc). This happens on both pc's connected to lan. I spoke to Linksys Support 2x's the first time they told me it was a Microsoft problem the second time I made it to 2nd level support and they told me to use static ip's. Well that works but is not the answer I am looking for. Do I have a bad router??? Thanks for your help.
    S/N CDF70DCI0033

    Chris
     
  2. csilano

    csilano Network Guru Member

    no one???????
     
  3. SometimesLinkyFan

    SometimesLinkyFan Network Guru Member

    This is "normal" behavior.

    What's happening is that the IP address that your PC *had* before the attempt to reconnect is being refused (the DHCPNACK message). This could be because some other PC has been assigned that address; it also may be the sometimes-inscrutable Linksys DHCP logic.

    What then happens is that the router's DHCP logic assigns a *new* address; you'll see a TCPIP message (4201) saying, in effect, that your network card was connected, albeit with a different address.

    I see this all the time with my BEFW11S4 version 4; magically, however, all five PCs here get an address, even if they change from boot to boot.
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice