Networking (BB) woes, trying to narrow down the problem

ambro25

Hi guys'n gals,

I've been having some extreme problems with my NTL BB connection for nearly a week now, and I am trying to find the solution myself (inasmuch as it can be attributed to hardware on my side of the line, which is not a given), and so need some help from networking luminaries here - pretty please.

Most of the info about the symptoms and troubleshooting that I've attempted to date are in this thread, but I'm not wanting to hijack that any further (not that I haven't made a serious effort to, by the look of things, I know ).

Briefly:
* NTL BB (cable) connection, initially on 300kb at install (Sept04) then upgraded to 1MB, never a bother at all until last Wednesday.
* NTL cable modem looks like a 100/120 series, but marked '200' on the back. Has always been plugged in my D-Link 514 (or 524 can't remember) for WiFi to my laptop + wired to my desktop.

* Symptoms are:
_ NTL modem config panel (192.168.100.1) shows everything's good (all signals, SNR values, etc. nominal).
_ Both the desktop and the laptop are showing lots of timeouts across the tracert loops (e.g. to www.google.com, www.bbc.co.uk), but not bad response times (e.g. loop 1: 5ms * 9ms bla.bla.bla.inet [1.12.123.5], loop 2: * * 12ms bla.bli.bli.inet [1.12.125.9], etc. wherein * = timeout)
_download speed from heanet (OpenCD ftp test) are sub-5kb/s, take minutes to show a download rate on the pop-up download box, and the rate tapers down to sub-1kb/s after a while, to next to nothing.
_email is same, irregular timeouts on 3 different mail servers.

*Attempted troubleshoots so far:
(i) plugged the cable modem straight into the desktop LAN + same again on laptop (has LAN port).
(ii) switched off software Firewall + windows XP Firewall + turned off AVG, Adaware & Spybot (not smart I know, but what the hell!).
(iii) switched off all non-essential processes after a clean boot (only 30 to begin with, down to about 20).
(iv) all of the above together.

That's all after grabbing the latest virus/malware/etc. defs on a USB key, upgrading the security apps and running each one twice to make sure both PCs are clean.

I have since (last night) tried the cable modem on USB instead - surprise! it worked-ish, still lots of timeouts but noweher near as many, and good enough for a heavily lagged BF2 session (never such lag before). Then, after a couple of hours - plop, at it again, same as above.

Now, I'd have ruled out cables and/or my PCs, since:
(a) I can connect to the NTL modem control panel (192.168.100.1) in LAN or USB mode, either with either the desktop or the laptop,
(b) I can ping the NTL modem from each computer and each computer to itself (to check hardware issues) and no loss, everything under 1ms as it should,
(c) I haven't installed any new software on the laptop for at least a month before the problem started (nor used the laptop for a week before the problem started).

What have I missed? Is NTL taking the proverbial p*ss when they tell me 'the line is fine' and 'they can't understand where the problem is, it must be with the PC'?:(

ambro25

NTL BB help called me last night after I emailed them the tracert results (as screengrabs). Still no joy

The guy I spoke to was adamant it must be a process running on my PC, since pings (from him-) to my modem unplugged from the PC were fine, then pings (from him-) to my modem plugged in the PC started the timeout problm again.

Things improved a bit when I killed the alg.exe process (and stopped it from starting at boot using services.msc). But it's still very erratic (running with no cache, so that any access loads the page from the line, Google.com will load in two seconds like it will load in 30 to 50 seconds).

And irishisptest is giving me anything between 80 and 105 kbps Down, 80 to 99 kbps Up. And sometimes a higher Up (i.e. 95) than Down (i.e. 83). (supposed to be 1MB connection).

Short of trying with a third computer (any volunteers?), I'm at my wits'end here... Any help? Please? (I'd rather try Boardsies' suggestions than drop the f*cking thing at PC World, where I'm quite certain they'll takes my €€€s to let me know they couldn't find anything :rolleyes: ... most likely after 3 weeks).

aaf

I know it may seem a bit drastic but what about a complete reintall of windows? I know it might be a bit of hassle but at least you'll have a nice clean system and can rule out any dodgy processes that may be running at present. You could end up spending hours upon hours trying to resolve this problem. Well, that's my 2c's anyway.

ambro25

Not that drastic, 'was actually thinking of that myself (especially since I've actually uninstalled pretty much everything last night, save for AVG, Office'03 and BF2, then run RegVac and tidied the whole thing as far down to bare-bones as I dared).

But I've never reinstalled winXP before so I'm a bit apprehensive about it, as I'm not sure how to go about it (just plop DVD in?) (plus what of my apps/docs?)

Also planning BIOS update and reinstalling mobo drivers (d'ld both this morning). Apparently the mobo (ASUS K8N8 made for HP, socket 754, codename 'Diablo' - nVidia nForce3 150 chipset) has got a built-in firewall of some sort as well (which I can't see as a running process, so... ?), so I'm wondering if that's got anything to do with it.

aaf

ambro25 wrote:

Not that drastic, 'was actually thinking of that myself (especially since I've actually uninstalled pretty much everything last night, save for AVG, Office'03 and BF2, then run RegVac and tidied the whole thing as far down to bare-bones as I dared).

But I've never reinstalled winXP before so I'm a bit apprehensive about it, as I'm not sure how to go about it (just plop DVD in?) (plus what of my apps/docs?)

Also planning BIOS update and reinstalling mobo drivers (d'ld both this morning). Apparently the mobo (ASUS K8N8 made for HP, socket 754, codename 'Diablo' - nVidia nForce3 150 chipset) has got a built-in firewall of some sort as well (which I can't see as a running process, so... ?), so I'm wondering if that's got anything to do with it.

First install of windows then. You'll need all the drivers before you install such as graphics, networking (which probably is in the motherboard driver package you downloaded) etc. You'll also need to backup all your docs, bookmarks/favourites, emails (if you use Thunderbird or Outlook/Outlook Express). If your hard drive is a SATA disk, you'll also need to have the SATA drivers on a floppy as you'll need them when installing XP. If it seems like a bit much for you, I'll show you how for a small fee Of course, you'll probably get tonnes of help here.

gaui3d0pnbz86o

Before you reinstall windows, try this first(back up your regestry first naturally)

coped and pasted from http://www.duxcw.com/faq/network/slowbb.htm

I was having similer problems and this sorted them out for me, you problem may not be the exact same but it could be worth a try

another possibility, when using the TCP/IP protocol, is an improper Windows registry setting. The Windows registry should be backed-up before you start. To do that, go to Start, Run, enter regedit, Help, and look under Import and Export or in the Help Index under backing-up the registry files... The process is at http://cable-dsl.home.att.net/#IncreasingWindow. You may find the instructions at the link a little confusing. So here are mine... In the second column of the table, choose your version of Windows (e.g., Windows 95/98/Me), right-click the appropriate file (e.g., TCPRW32K.REG) with your mouse, choose Save Target As... in the resulting menu, and select a location to save the file (e.g., your Desktop). Go to that location and double-click the file. Restart Windows. To undo the "damage," use the appropriate file in the fourth column. Editing (or tweaking) the Windows registry can get you in a lot of trouble and may make Windows unusable. This procedure is therefore a last resort and should not be done before troubleshoot the hardware. This procedure may also fix slow Local Area Network connections. Note: this procedure may mess-up dial-up connections if you are still using a MODEM.

ambro25

mmm...interesting. Nothing to lose by trying, I suppose.

However, I don't appear to suffer from latency, only bad loss: e.g. on any "tracert" that I've run, hops have usually been in the low 2-figures (20/30/40), with lots of timeouts, rather than 100+ ms.

I'll give this one a go tonight, after upgrading AVG with today's definitions & running that through
* failing that I'll 'repair' XP instead of a full re-install,
* failing that I'll zap the mobo drivers and re-install the mobo drivers afresh,
* failing that I'll upgrade the BIOS,
* failing that I'll wait until the NTL engineer has been on Tuesday (he's bringing a new modem - I still think it's the modem, given that I've got the problem on 2 PCs)

I'm not gonna try anything on the 2nd PC (lappie ), because I'm in airport tomorrow to wait for a friend, so I'm gonna take the lappie and check WiFi functionality - if it works there, then it must beNTL

ambro25

ambro25 wrote:

I'll give this one a go tonight, after upgrading AVG with today's definitions & running that through

Update @ 09/02 - no joy with this registry hack.

ambro25 wrote:

(i) failing that I'll 'repair' XP instead of a full re-install,
(ii) failing that I'll zap the mobo drivers and re-install the mobo drivers afresh,
(iii) failing that I'll upgrade the BIOS,
(iv) failing that I'll wait until the NTL engineer has been on Tuesday

None of the above fixed nothing. Nor did a full XP SP1 reinstall on the lappie. Still sub-1kb/s downstream (and very infrequently up to 600kb/s, e.g. Monday night for about 30 mins).

Didn't get to try airport WiFi as flight was cancelled, but took lappie to work and have asked IT guy to just hook it up to the LAN and see what browsing's like.

NTL engineer didn't show up Tuesday, was again booked for Friday... and then NTL decided to cancel it unilaterally since their BB support team had logged "that line and modem are fine". Nasty email has followed, of course. If my lappie browses web with no bother through work LAN, then I'll know and be 110% sure that it's not my hardware (and I'll be seriously contemplating serving writ on NTL in small claims court :mad: :mad: :mad: ). F*cking jesting kn0bj0ckeys, the lot of them :mad:

Gurgle

At the risk of pointing out the obvious, have you tried turning off the cable modem & disconnecting from everything?

- Oh yeah, is your download capped and have you checked your usage?
Maybe some prick is leeching off your wireless router. I know some (like IBB) turn your connection speed down automatically when you hit the download limit.

http://www.boards.ie/vbulletin/showthread.php?t=2054886285&page=4

ambro25

Gurgle wrote:

At the risk of pointing out the obvious, have you tried turning off the cable modem & disconnecting from everything?

Yep. Quite sure I've already posted that earlier in-thread.
Tried booting the modem (on-off) NTL AP + LAN-connected
Tried booting the modem (on-off) NTL AP + USB-connected
Tried booting the modem (on-off) NTL AP - connected only (then plug in LAN)
Tried booting the modem (on-off) NTL AP - connected only (then plug in USB)
Tried booting the modem (on-off) decoupled from everything then plugging NTL AP and LAN in
Tried booting the modem (on-off) decoupled from everything then plugging NTL AP and USB in

Oh yeah, is your download capped and have you checked your usage?

No - as in not checked my usage, which is indeed capped in theory (which I have yet to ever reach/I haven't got that much free time ), but then I'm sure NTL BB support would have told me that was the problem, no?

I have had that problem for about two weeks now (you try & reach your CAP with sub-1kbps downstream ) + not downloaded or P2P'd anything for 3 weeks before that.

Maybe some prick is leeching off your wireless router. I know some (like IBB) turn your connection speed down automatically when you hit the download limit.

First thing I checked when the problem started 2 weeks ago (in case some eejit managed to crack my WEP).

Router is 128bit-WEP protected + DHCP possible leases limited to two IP addresses only. Checked router log, no other leases than my desktop or laptop since earliest log date (in June 05).

Plus, I've not ever had the cable modem not plugged into the router, which has built-in f'wall, nor have I ever had the router unsecured through at least WEP. And I can't remember the last time I got trojan'd or infected by anything (I don't browse 'hi-risk' sites nor have much emails/spams coming in).

I'm now just waiting for the Missus to drop me the lappie at work this afternoon and satisfy myself that it can browse Web happily, so that I can turn the fangs on NTL :mad:

ambro25

F*CKING KNEW IT!

Sorry for the expletives, but by Eck & by Gum I'm about to f... sorry to explode on the phone to NTL: laptop has been tested at work, is working absolutely fine, I've just been browsing with no hiccups or timeouts what-so-ever using work LAN. I've even had the IT crew give it a quick 5 mins once-over, it's all peachy/kosher, prefectly config'd.

NTL, after giving me the runaround for 2 weeks, telling me it's my hardware, my setup, etc. -even though I kept telling them it could absolutely not be- have now officially made my hate-list...

... and it's a bad place to be :mad: :mad: :mad: :mad: :mad:

What's the number for the Indo again?

ambro25

For anyone who posted in this thread to help me with my NTL BB woes - a deep thank you.

For anyone interested: it was the f*cking modem (changed at lunchtime today). Acc to the engineer, some internal component must have fried/got heat damage.

Result: 3 week with no BB, first round of Boards.ie Battlefield 2 tourny missed - when I told them within a week that it could only be the modem and after they told me (twice) that the modemn was "checking out just fine".

Two thumbs down at NTL :mad: :mad: