Error 721.

InKursion · 5 Jan 2007 at 23:16

Hey all,

Since migrating to a new ISP (Tiscali to Pipex, leave the jokes for later eh), I have not been able to connect because of a recurring error 721 with my dial-up connection; something about remote computers being refusing and pains in the arses.

As I'm sure you can understand this is very frustrating, and typically customer support at the internet service provider offices is sub-par and unhelpful. I'd like to have a BT engineer come and inspect my home setup, but to my ISP this is simply impossible. So- anyone with experience of this error?

Sometimes I can connect, normally after a fresh modem reinstall or a reformat. But then it returns and it's quite incurable- no amount of configuration or resetting will change it. So, I'm assuming it's hardware/driver based or something on the phoneline/DSLAM.

Appreciated!

Edit; I have bought new modem(s), tried with entirely new computers (both are intermittent and unreliable with the connection), reformatted, reinstalled drivers, refitted ADSL filters, and also tried to connect to the bt_test@startup_domain address multiple times to no avail.

tolien · 6 Jan 2007 at 00:16

What modems did you try, and have you tried them on a connection that you know works?

The ideal would be to get your hands on a router - that way you eliminate drivers and all that crap.

InKursion · 6 Jan 2007 at 12:43

I have used two USB ADSL WAN modems- a Zoom one and a Sagem one, both which have caused driver problems as you have mentioned. Whenever I take out the USB cables on my ASUS A8N-E nForce4 motherboard it causes an IRQL_NOT_LESS_THAN_EQUAL BSOD. Also that motherboard-nvidia set-up has generally always caused me problems when it comes to USB hub, USB controllers etc. Nightmare.

When I run the USB modem on an old Dell Dimension (with different mobo and chipset drivers), the Internet connects fine. Although the difference that my ISP thought was that the Dell is connected to my Master Socket (original phone jack), but the other newer system and other USB modem is connected to a freshly installed socket that was specially installed for the room. Apparently not having a broadband connection on the master socket can cause problems; but I had smooth and uninterrupted service on my old ISP prior to the migration.

Even when I reformat and clean-install the 'troubled' system- with only the USB drivers and display adapters installed, I still recieve the same error. Which makes me suspicious that it is the socket... I'm not giving the computer any faulty drivers or complications that can cause conflicts etc.

Any suggestions? Error 721 seems to be quite hard to find a 'fix' for on the Internet- most people seem to encounter it when connecting to VPN's, whereas mine is dial-up related (DUN).

tolien · 6 Jan 2007 at 14:00

They're half right. You generally want the modem to be on the master socket to eliminate any issues with your extension wiring, but it isn't a necessity.

The only suggestion is try a router on the extension. At least that way you won't have any USB problems, though I haven't had any real issue with my A8N.

InKursion · 6 Jan 2007 at 17:46

Hey,

I have now purchased a wireless BT router, which is running fine (and allowing me to view this forum on my own computer for the first time in weeks!).

My only problem is that the downloads are very slow; < 10kbps, when it is an 8.3Mbps connection, with an 'Excellent' signal strength of 54Mbps. What causes this download slowness? Also, I have connected the router via both an ethernet lead and wireless connection- would this cause any issues? I cannot seem to load the Internet or connect to anything when I *just* use the RJ45 ethernet lead, even though the router detects it as an Nvidia Onboard LAN.

InKursion · 6 Jan 2007 at 20:19

Still experiencing slow download speeds of less than 30 kbps.

Would this be router related or ISP peak time throttling? I've looked through all of my advanced router settings and can't seem to find anything at all.

tolien · 6 Jan 2007 at 20:29

It could be either or both.

What's the router reporting as far as connection statistics go (SNR margin, attenuation etc)?
It might be an idea to try the BT Speedtest as well, which would at least eliminate your ISP.

InKursion · 6 Jan 2007 at 20:44

This means nothing to me but here's my line stats:

Line attenuation downstream: 10.0 dB
Line attenuation upstream: 4.5 dB

Noise margin (down): 14.8 dB
Noise margin (up): 21.0 dB

Mean much to anyone?

I'm on Pipex currently, who are apparently notoriously bad for throttling during peaktimes. Although I'm a fresh customer, this policy (allegedly) affects all users. I don't have anything to be sure on this- it's more of a hope than anything else... rules out the possibility of me making more changes ;-)

.

Edit: Just completed the BT Speedtester; showed a pretty abysmal throughput of 1700-ish, when my expected is nearer 8000. However, even that measly bandwidth should achieve higher than 50kbps? Haven't seen that speed yet.

InKursion · 6 Jan 2007 at 22:29

I have heard from a few friends of mine that are on wireless that during the first week or so of their set-up they experienced slow download speeds also. It seems that we all experienced/experience normal browsing, average pings but badly affected downloads after the early setup of wireless routers.

Is this an established habit or known trait or is that simply coincedence? I'm not making a statement- asking a question

. Still do not have a clue what could be causing this; but the 20kbp/s average speed is tear-inducing after a fresh reformat. All of the software and patches that I need to download are taking forever!

EDIT: something that I feel I should mention- my router isn't on my master socket. I have an 'extra' installed socket/terminal in my house that is not the original (i.e. not the original direct-phoneline socket), yet was still installed by a BT engineer. As far as I can see it only makes a difference in the way that there's about 8 metres more cabling because of the longer distance. Could this have an effect? It is a lot of hassle to move desktop systems and routing equipment around to merely test this idea.