Cable Forum - View Single Post - Belkin F5d7230-4

punkoiuk · 14-04-2007, 21:23

Hello

It does look like there is something going on. We started having router problems related to DHCP. We could connect a pc directly, but the modem would not pick up the DHCP server - the LAN worked fine, just not the WAN.

NTL/Virgin came out and said there was nothing wrong, it must be our router - although we did managed to get a cable modem out of them rather than having to go through the settop box all the time.

We got a new router (SMC) - thought great it is working but within around 20 mins it stopped. We had to go in, turn off our router firewall and then release and renew the DHCP for the router then enable the firewall again. It will then be ok for a little while (less than an hour) then do exactly the same again. Yet it is fine when the pc connect straight in without the router.

The message in the log file says...
04/14/2007 21:05:16 DHCP Client: Could not find DHCP daemon to get information

It seems very strange that too routers have acted similarly - I am having doubts if our old one was really broken.

The only hardware setting I could think it is would be some sort of time out - but I cannot see anything on the router.

I think it is time for me to go back to Virgin to ask what is going on, in the meantime any suggestions appreciated.

14-04-2007, 21:23	#17
punkoiuk Inactive Join Date: Apr 2007 Posts: 2	similar problems with routers too Hello It does look like there is something going on. We started having router problems related to DHCP. We could connect a pc directly, but the modem would not pick up the DHCP server - the LAN worked fine, just not the WAN. NTL/Virgin came out and said there was nothing wrong, it must be our router - although we did managed to get a cable modem out of them rather than having to go through the settop box all the time. We got a new router (SMC) - thought great it is working but within around 20 mins it stopped. We had to go in, turn off our router firewall and then release and renew the DHCP for the router then enable the firewall again. It will then be ok for a little while (less than an hour) then do exactly the same again. Yet it is fine when the pc connect straight in without the router. The message in the log file says... 04/14/2007 21:05:16 DHCP Client: Could not find DHCP daemon to get information It seems very strange that too routers have acted similarly - I am having doubts if our old one was really broken. The only hardware setting I could think it is would be some sort of time out - but I cannot see anything on the router. I think it is time for me to go back to Virgin to ask what is going on, in the meantime any suggestions appreciated.