PDA

View Full Version : Weird DHCP problem (Guildford area)


RenOfHeavens
26-07-2004, 23:05
Been having some odd problems tonight, hopefully someone here can shed some light on them.

At around 20:32 (TY Trillian :P) I lost the internet. Logged into the router, as that's usually the first problem. Tried DHCP Release/Renew but with no luck. Power cycled the router, no luck either. Then I went & power cycled the Modem & Router. This time the router had an IP, but unfortunatley it was 10.41.*.* (Almost identical to the modems IP).

I thought I'd give a static IP setting in the router a try, and being as sad as I am, I've got the IP, Gateway, Subnet Mask, DNS1&2 memorised. Whacked that in, and the internet came back to life.

Then, at 22:18 I lost the internet again. Tried DHCP, but was back to 10.41.*.* ¬_Ãà †â€™ÃƒÂ¢Ã¢â€šÂ¬Ã…¡Ãƒâ€šÃ‚¬ Back onto static again, but I'm not sure how long it'll hold out.

Anyone know why I can't get a real IP from the DHCP? Also, is it alright for me to be using a static IP?

Random possibly useful info:
600Kbps through a Pace 1000 series STB
BEFSR41 Router, serving 2 PCs & 1 Xbox
Post Code area: KT15

Also, this can't be good can it? O.o

Tracing route to cableforum.co.uk [66.199.235.18]
over a maximum of 30 hops:

1 10 ms 31 ms 13 ms 10.41.0.1
2 12 ms 12 ms 13 ms herm-t2cam1-a-ge94.inet.ntl.com [80.3.34.5]
3 13 ms 12 ms 11 ms herm-t2core-a-ge-wan61.inet.ntl.com [80.3.33.5]
4 14 ms 12 ms 12 ms bre-bb-a-so-300-0.inet.ntl.com [62.253.187.17]
5 15 ms 14 ms 16 ms gfd-bb-b-so-700-0.inet.ntl.com [213.105.172.150]
6 58 ms 43 ms 26 ms tele-ic-2-so-100-0.inet.ntl.com [62.253.185.74]
7 18 ms 17 ms 16 ms linx.ge-0-0-0.gbr1.ltn.nac.net [195.66.224.94]
8 86 ms 86 ms 85 ms 0.ge-6-2-0.gbr2.nyc.nac.net [209.123.11.181]
9 83 ms 85 ms 85 ms 94.gi4-2.esd1.nyc.nac.net [64.21.102.14]
10 88 ms 87 ms 89 ms 10.gi1-1.esd1.tlw.nac.net [209.123.11.230]
11 * 108 ms 90 ms ezzi-2.customer.tlw.nac.net [207.99.110.174]
12 101 ms 89 ms 88 ms 65.125.239.146
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Stuartbe
26-07-2004, 23:40
Nothing on the server status page !

Can you post the webmin page from the modem ?

Tezcatlipoca
26-07-2004, 23:41
Been having some odd problems tonight, hopefully someone here can shed some light on them.

:welcome: to CF, Ren :)

At around 20:32 (TY Trillian :P) I lost the internet. Logged into the router, as that's usually the first problem. Tried DHCP Release/Renew but with no luck. Power cycled the router, no luck either. Then I went & power cycled the Modem & Router. This time the router had an IP, but unfortunatley it was 10.41.*.* (Almost identical to the modems IP).

I thought I'd give a static IP setting in the router a try, and being as sad as I am, I've got the IP, Gateway, Subnet Mask, DNS1&2 memorised. Whacked that in, and the internet came back to life.

Then, at 22:18 I lost the internet again. Tried DHCP, but was back to 10.41.*.* ¬_Ãà †â€™ÃƒÂ¢Ã¢â€šÂ¬Ã…¡Ãƒâ€šÃ‚¬ Back onto static again, but I'm not sure how long it'll hold out.

Anyone know why I can't get a real IP from the DHCP? Also, is it alright for me to be using a static IP?

Random possibly useful info:
600Kbps through a Pace 1000 series STB
BEFSR41 Router, serving 2 PCs & 1 Xbox
Post Code area: KT15

Also, this can't be good can it? O.o

There has recently been some work in the Guildford area (& others), so maybe that has been part of your problem?

(see http://www.ntl-isp.ntl.com/ServiceStatus/)

Also, I believe the Linksys BEFSR41 has had DHCP issues with certain firmware versions.

Which firmware version do you have?

There is a thread about the new firmware here: http://www.cableforum.co.uk/board/showthread.php?t=13338

Also, a thread here about someone having connection problems with a BEFSR41: http://www.cableforum.co.uk/board/showthread.php?t=14577 (not really the same problem as yours, though)

Static IP...you shouldn't really use a static IP....


Have you tried phoning NTL's Tech Support about this?


Other than all that...can't think of much else, I'm afraid. I'm sure someone else will be along with more help soon.

Stuartbe
26-07-2004, 23:48
Excuse my manners - :welcome: to the forum (my bad) I did not spot that one... Good job matt is awake :D

RenOfHeavens
26-07-2004, 23:57
Can you post the webmin page from the modem ? I wasn't aware you could get a webadmin page off a STB?
I believe the Linksys BEFSR41 has had DHCP issues with certain firmware versions.

Which firmware version do you have? I'm on v1.45.7 (Rev. 2) which up until recently was the latest version, I'll grab the updates in a sec.
Static IP...you shouldn't really use a static IP Didn't think so... was my last resort to getting online :o
Have you tried phoning NTL's Tech Support about this? Whoops, I lied. Phoning NTL is my last resort XD

Cheers for the welcomes, not sure why I haven't posted around here. I was a long-term member of NTHellWorld (.com flavour) but when that went down, I sort of stopped visiting :\

BBKing
27-07-2004, 01:43
What's the exact IP? I have a suspicion it'll be in the range for provisioning, which means that the DHCP server asks the provisioning system what address to give you and is told you're not provisioned, so gives you a provisioning address

It's extremely rare to have an entry corrupt in provisioning but I've seen it occassionally (twice in four years, in fact).

When you have the 10.41.x.x address have you tried browsing to the 172.16.30.83/4 provisioning page and re-provisioning?

Also, you haven't changed the MAC address in the router config have you? That could cause it.

RenOfHeavens
27-07-2004, 18:33
Well, after I had flashed the BIOS & cloned the MAC I tried it again. Didn't work, so I left the modem unplugged all night. Tried again in the morning, but nothing. Went out for the day & phoned NTL when I got back.

They suggested trying the 172.16.30.83 page after power cycling it for a bit, but I couldn't reach the page. After that, I decided to ditch the router & try for a direct connection. Plugged it in, and I was online instantly.

Decided to clone my NIC MAC accross to the router, and plugged the internet back in. Did a DHCP Release/Renew, but it went back to 10.41.14.31 O.o Went off & had dinnner, did another Release/Renew for the hell of it when I came back, and it was online again :D No idea why it didn't get it the first time.

As always, many thanks for all your suggestions! http://members.lycos.nl/renofheavens/emot-worship.gif

Satch
27-07-2004, 23:10
NTL Service in parts of the Guildford/Woking area has been vile at times over the past weeks. Tonight it is about as bad as it has ever been. For example, it took nearly 30 seconds to load this thread! Now this is unusual, for over the past 18 months overall service has been good.

But, once again, I am told that there is no problem at all. Well pardon me, but if this degraded service has been the source of recent common complaint by just about everyone we know who uses NTL in this area, surely there must be some issue?

No Sir, all working perfectly. Must be your equipment.:dunce:

RenOfHeavens
28-07-2004, 10:32
Try changing your proxy server, my connection occasionally got like that when it was on an overcrowded proxy. There's a list of the NTL Proxys here (http://homepage.ntlworld.com/robin.d.h.walker/cmtips/trancache.html#ntl), and instructions on how to change your proxy just above it. My connection has been fine, apart from when it died the other day (Using cache2-glfd.server.ntli.net)

stormrider
28-07-2004, 20:46
No problems here (Woking) for a while now. Occasionally get the modem dropping but thats about it.

Hom3r
28-07-2004, 20:55
On Monday night about google were hit by a new strain of mydoom and slowed the entire net right down.


I even had problems in Harlow

(BBC technology website gave details)