Has anyone seen the like of the following please I've got quite an extensive network - multiple laptops, iPhones, iPads, wireless printer, Devolo Ethernet over power with a remote AP all wirelessly connected. All has been working perfectly fine until recently... However now, one of the laptops (an Acer running Win Vista) has difficulty establishing a network connection to the TG582n when using DHCP - it is the only device having the issue. I boot the machine up and it takes ages attempting to acquire a DHCP address, it fails and self configures an IP address. The TG582n however clearly shows that a DHCP address has been allocated and believes the device to be active. There are other APs (BT / Talk / SKY) which the Acer's WiFi is seeing (it is located at the furthest point away from the TG582n albeit not far from the Devolo WiFi AP) to which it 'roams' and quite readily acquires an IP address in the BT network. If I 'burn' a static IP address into the laptop, it quite readily connects to the internet via the TG582n, is shown in the device list with a static IP, however it is not accessible (network shares, ping etc) from other devices on the network. Either the name cannot be resolved (DNS issue) or the MAC address cannot be found (Destination unreachable) which I understand is an ARC issue. It is as though the DHCP server has issued the address allocation, but it has not been received or applied by the client laptop.
Anyone have any thoughts or diagnostic suggestions please? UPDATE: As if this issue is not strange enough in its own right - router to all intents and purposes working fine for all other device DHCP requests - I just performed a cold restart and the problem (in respect of said Win Vista laptop) has 'gone away'. Looks like the TG582's DHCP server process was part borked. If anyone with expert knowledge in this area can add insight, this might prove useful to anyone else encountering the problem. I also uncovered this symptom as part of the diagnostic process - http://social.technet.microsoft.com/Forums/windows/en-US/fa961e16-5624-4bd2-984c-b0d7cd75fef5/error-... - however none of this explains non-addressability when the IP address has been hard coded and the TG582n has recognised the same.