I've been getting this notice (http://62.6.38.125/index.html and as attached) on and off all day, has anyone else as a matter of interest?
I've also had two really strange phone calls supposedly from BT asking about the problems I'm having with my connection dropping. The caller was so incoherent and there was so much background noise I couldn't even establish it if was the same person calling. Perhaps I'm being paranoid but if IDNet had reported a fault on my line wouldn't it be Openreach calling me?
I wonder if that message is generated by the modem when there's a line fault, Zap? (I'm assuming this is the cable connection?)
Quote from: Rik on Sep 21, 2010, 19:29:54
I wonder if that message is generated by the modem when there's a line fault, Zap? (I'm assuming this is the cable connection?)
I don't think so Rik, I'm getting it on both lines.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\zappaDPJ>tracert 62.6.38.125
Tracing route to crdnsr1.ukcore.bt.net [62.6.38.125]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 11 ms 12 ms 12 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 12 ms 12 ms 12 ms telehouse-gw5-e4-400.idnet.net [212.69.63.245]
4 28 ms 12 ms 20 ms gi8-27.mpd01.lon02.atlas.cogentco.com [149.6.148
.205]
5 12 ms 12 ms 12 ms te1-2.ccr01.lon02.atlas.cogentco.com [130.117.50
.138]
6 56 ms * 12 ms te4-3.ccr01.lon01.atlas.cogentco.com [130.117.1.
217]
7 12 ms 11 ms 12 ms bt.lon01.atlas.cogentco.com [130.117.14.50]
8 12 ms 12 ms 13 ms t2c2-ge2-0-0.uk-lon1.eu.bt.net [166.49.135.109]
9 13 ms 12 ms 14 ms t2c1-p4-0.uk-eal.eu.bt.net [166.49.208.109]
10 14 ms 12 ms 12 ms 166-49-168-22.eu.bt.net [166.49.168.22]
11 13 ms 13 ms * core1-te0-12-0-0.ealing.ukcore.bt.net [62.6.200.
129]
12 14 ms 14 ms 14 ms core1-pos0-7-0-1.ilford.ukcore.bt.net [62.6.201.
49]
13 16 ms 14 ms 13 ms mspaccess1-gig5-0-0.ilford.fixed.bt.net [194.74.
16.66]
14 * 213.121.157.42 reports: Destination net unreachable.
Trace complete.
C:\Users\zappaDPJ>
Bang goes another theory. I've seen a message like that generated by the 2700 when the line is down, but that's as useful as I can be. :( I wonder if they are rebuilding your circuits?
I thought it was generated by BTw when the routing to the ISP realm is broken.
I had a vaguely similar message back in the day when I was on NTL cable and they hadn't registered the line properly. I'm 99.9% sure the problem is not local.
Well it's all got really stupid now. I'm being redirected to that BT URL virtually all the time on both connections. Powering the routers/modems down for five minutes sometimes gets me back for a few minutes but throughput on both my ADSL and FTTC is currently below 1.5 MB. In addition I can't get my email because IDNet's server is rejecting the password I've used from day one. I really don't understand it.
I think someone's got it in for you, Zap. :( FWIW, mail is fine here.
My e-mail password is being rejected also, or was earlier. I think that's a separate issue.
Zappadj, this is probably a case of DNS servers failing.
Go to your router's homepage and check if the DNS is properly filled in, if not you can obtain these from IDNet.net control panel. Fill them in your router's "Basic Settings" page (assuming it's Netgear WGR614) and enter them in your TCP/IPv4 properties.
This should fix it, if not then you could try google or opendns servers!
If none of those work then it's most likely something else..
Thanks for those suggestions. The DNS settings on my ADSL connection are currently set to automatic. I did try to check what's being listed against what's in my IDNet control panel but I can't log in there either. I'm getting an internal server error reported.
I've been able to download my email now but I still can't send anything. The SMTP server is rejecting my login/password.
Can you try different DNS settings like Open DNS Zap?
I tried that early on. It doesn't help with email or my IDNet customer login issues but web pages resolve instantly.
So changing DNS gives you access to the net which proves a point.
The IDNet login is borked Zap, it wont let me in either, tries to load for a loooong time and then throws a 500 error.
QuoteInternal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, support@idnet.net and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 400 Bad Request error was encountered while trying to use an ErrorDocument to handle the request.
Thanks for that, it seems that there are multiple problems and I've been unlucky enough to encounter the lot during the last 24 hours. The two calls last night from BT have left me completely flummoxed if not a little paranoid.
Quote from: zappaDPJ on Sep 22, 2010, 07:31:31
Thanks for that, it seems that there are multiple problems and I've been unlucky enough to encounter the lot during the last 24 hours. The two calls last night from BT have left me completely flummoxed if not a little paranoid.
IDNet did say there could be routing inconsistency yesterday after some more work, you may have been caught up in that, I had no net access in the morning for a while yesterday. Like you I never trust random calls let alone from BT, I would have thought IDNet would contact you about BTw but I really could not say.
Could someone try a few sites for me please:
http://www.tsohost.co.uk/
www.avfcommunications.com
www.ashes-guild.com
www.oap-clan.co.uk
Quote from: Gary on Sep 22, 2010, 08:12:59
IDNet did say there could be routing inconsistency yesterday after some more work, you may have been caught up in that, I had no net access in the morning for a while yesterday. Like you I never trust random calls let alone from BT, I would have thought IDNet would contact you about BTw but I really could not say.
I'll be checking with support a little later, it seems like it's not just me having issues. Thanks for the reply :)
Quote from: zappaDPJ on Sep 22, 2010, 09:23:43
Could someone try a few sites for me please:
http://www.tsohost.co.uk/
www.avfcommunications.com
www.ashes-guild.com
www.oap-clan.co.uk
The sites work from a non IDNet line
Quote from: zappaDPJ on Sep 22, 2010, 09:23:43
Could someone try a few sites for me please:
http://www.tsohost.co.uk/
www.avfcommunications.com
www.ashes-guild.com
www.oap-clan.co.uk
All four fine, Zap.
Quote from: zappaDPJ on Sep 22, 2010, 09:24:43
I'll be checking with support a little later, it seems like it's not just me having issues. Thanks for the reply :)
I wonder if it would be worth entering the IDNet servers manually:
212.69.36.3 Primary
212.69.40.3 Secondary
Hi
all 4 sites working for me OK
Rogerp
All 4 sites working for me as well.
All work fine here Zap
Quote from: zappaDPJ on Sep 22, 2010, 05:56:22
I've been able to download my email now but I still can't send anything. The SMTP server is rejecting my login/password.
Did you see this on the status page, Zap:
Posted: 22 September 2010 08:40:40
Updated: 22 September 2010 09:44:19
Status:Resolved
Message: We are currently experiencing problems with authenticated SMTP connections to smtp.idnet.com. Engineers are currently working on the problem.
Quote from: zappaDPJ on Sep 22, 2010, 09:23:43
Could someone try a few sites for me please:
http://www.tsohost.co.uk/
www.avfcommunications.com
www.ashes-guild.com
www.oap-clan.co.uk
All work for me too, on a FTTC line so it's not that!
Quote from: Rik on Sep 22, 2010, 10:52:34
Did you see this on the status page, Zap:
Posted: 22 September 2010 08:40:40
Updated: 22 September 2010 09:44:19
Status:Resolved
Message: We are currently experiencing problems with authenticated SMTP connections to smtp.idnet.com. Engineers are currently working on the problem.
I didn't Rik, thanks. Where is that posted? The problem does appears to be fixed now :)
I can now also get to the websites I linked. They are all very close in terms of routing so I thought the host had gone down but apparently is was a problem at my end. Thanks for the feedback on that.
Finally, IDNet have sent me a new router to try (not a Modem). The disconnections I'm seeing are user requested which they think points to a faulty router. We'll see what happens :)
It was in the RSS feed, Zap. If the router doesn't cure it, then I think they need to get BT to replace the modem. If that doesn't work, BT should just run you some FTTP. ;)
So has the router solved anything Zap?