I have had the above Router for around 2 years, it has survived a house move and very temporary setup arrangements. Recently it has refused to connect when the PC is started until the router is rebooted.
So, I thought, 2 years is an OKish life for a router; Amazon had an identical new one for around £38, so this was purchased and installed. After about 4 days the new router is exhibiting exactly the same problem.
This tends to suggest that the problem is not with the router but either with the PC, phone line or the ISP.
Router No 1 was using DGTeam firmware v.5.01.16
Router No 2 is using the supplied software/firmware v.5.01.16
Both are using OpenDNS DNS servers
Nothing significant has changed in the PC Software:
OS is Windows xpSP3
Main browser is Pale Moon 15.3.2
Firewall is Private firewall 7.0.28.1
Not much in the router log:-
Sat, 2000-01-01 00:01:01 - Initialize LCP.
Sat, 2000-01-01 00:01:01 - LCP is allowed to come up.
Sat, 2000-01-01 00:01:02 - CHAP authentication success
Sat, 2000-01-01 00:01:08 - Send out NTP request to time-g.netgear.com
Mon, 2013-01-14 15:35:14 - Receive NTP Reply from time-g.netgear.com
Mon, 2013-01-14 16:34:05 - Router start up
Mon, 2013-01-14 16:59:09 - Administrator login successful - IP:192.168.0.2
The system Event Viewer has the following:-
The IP address lease 192.168.0.1 for the Network Card with network
address 001xxxxxxxxx has been denied by the DHCP server 192.168.0.1
[ The DHCP Server sent a DHCPNACK message].
Microsoft give the following explanation:-
Explanation
The DHCP Server service did not extend the lease on your computer's IP address, so your computer temporarily lost its connection with the network.
This could be caused by a scope change. For example, when a roaming laptop moves from one network to another, its IP address lease might need renewal. When the DHCP Client service tries to renew the address, that request might go to a different server that will not extend the lease either because it does not know about this address lease or because it has already issued the address lease to another client.
This also happens when two DHCP servers are configured to give out addresses in the same IP address range.
User Action
No user action is required. The DHCP Client service will continue trying to obtain a working IP address until it succeeds, and DHCP establishes the network connection on its own.
I suspect this may be the problem, but is there anything I can do about it
http://forum.kitz.co.uk/Smileys/kitzemotes/cry.gif ?