Post upgrade problems

Started by Rik, Sep 05, 2010, 19:43:50

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

Rik

If you're having any problems with your service following today's router upgrades, eg you can't reach a particular site or sites, could you please post details (including the URL and the results of pinging it)  in this thread so that we can pass the information onto IDNet.

If the problem goes away, a post to say so would also be appreciated.

Thanks. :)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rikki

#1
Hi there.

We cannot get through to some web sites as 'server errors', and email access is intermittent. Also, my wife has sky sports app on her ipod touch, and this cannot now find any internet. It appears we can't access secure servers or ports, or at least not for any period of time. Thanks . Here's one server we cannot access  vi.ebaydesc.co.uk

Simon

I'm having a problem which seems to be with push email.  This thread refers:

http://www.idnetters.co.uk/forums/index.php?topic=21908
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Conrad

Have been having a few problems since yesterday evening.  Occasional disconnects (last one at aprox 10am). Since then, I have been getting frequent "Ooops.. Firefox could not find the page you are looking for..." messages (or something along those lines). A refresh or two does the trick, but it is way frustrating!  Have also been experiencing something similar to blocked ports - i.e. intermittently unable to connect to my mail servers.
I wasn't even aware of any "Upgrades" taking place - don't we get e-mail notifications of planned works? If not, then we should! ;)

The last webpage I had to "refresh" 3 times before it would load was: http://www.theitjobboard.co.uk/IT-Job/Junior-Java-Web-Developer-Consultant-London-Java-J2EE/7955682/en/?WT.mc_id=A117&xc=63&utm_source=Aggregator&utm_medium=cpc&utm_campaign=Trovit

Pings were not very helpful:
C:\>ping www.theitjobboard.co.uk

Pinging je3.smwebhost.com [62.189.247.98] with 32 bytes of data:

Reply from 62.189.247.98: bytes=32 time=188ms TTL=113
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 62.189.247.98:
   Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
   Minimum = 188ms, Maximum = 188ms, Average = 188ms

C:\>ping -n 20 www.theitjobboard.co.uk

Pinging je3.smwebhost.com [62.189.247.98] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 62.189.247.98:
   Packets: Sent = 17, Received = 0, Lost = 17 (100% loss),
Control-C
^C
C:\>


Tracert:
C:\>tracert www.theitjobboard.co.uk

Tracing route to je3.smwebhost.com [62.189.247.98]
over a maximum of 30 hops:

 1    44 ms    99 ms   100 ms  dsldevice.lan [192.168.1.254]
 2    26 ms    25 ms    26 ms  212.69.63.99
 3    26 ms    26 ms    26 ms  telehouse-gw5-lo1.idnet.net [212.69.63.245]
 4    26 ms    27 ms    26 ms  149.6.148.205
 5    26 ms    26 ms    25 ms  130.117.50.138
 6   102 ms   102 ms   101 ms  te0-0-0-1.mpd22.jfk02.atlas.cogentco.com [154.54
.30.17]
 7   101 ms   102 ms   101 ms  154.54.25.150
 8   107 ms   110 ms   125 ms  154.54.25.238
 9   104 ms   105 ms   104 ms  154.54.30.122
10   104 ms   105 ms   106 ms  verizon.iad01.atlas.cogentco.com [154.54.10.226]

11   105 ms   104 ms   105 ms  0.ae1.XL3.IAD8.ALTER.NET [152.63.33.118]
12   111 ms   111 ms   110 ms  152.63.43.69
13   110 ms   110 ms   111 ms  152.63.43.78
14   188 ms   183 ms   198 ms  146.188.14.174
15   188 ms   187 ms   188 ms  POS2-0.GW9.LND10.ALTER.NET [158.43.150.129]
16   187 ms     *        *     62.189.247.98
17     *        *        *     Request timed out.
18     *        *        *     Request timed out.
19     *        *        *     Request timed out.
20     *        *        *     Request timed out.
21     *        *        *     Request timed out.
22     *     ^C
C:\>


Could the new ios be dumping icmp traffic (among others) under load?  Keep us updated Rik!  Cheers buddy!

scook94

#4
Hi Rik, I'm having problems accessing some sites but strangely it's only on my desktop, my laptop (connected via wi-fi) appears fine! I had assumed I'd got infected somehow but hopefully it's an after effect of these upgrades.

http://en-gb.facebook.com seems to be one, as does http://www.play.com and http://www.crackberry.com

pings return - Ping request could not find host
tracert returns - Unable to resolve target system name.


EDIT: Just realised my laptop is using a VPN connection so I can access my work's intranet, that'll explain why it seems okay.
Steven
--------

Peyr

For me this isn't a problem with any specific URL, more a general problem where I receive a "server not found" error about one third of the time visiting any site at all.

As an example of a consistent problem however I'd cite any live stream, such as this one http://www.justin.tv/competitiveonline  which fails to work at all for me (or indeed any other live stream, not just the ones on that particular website)

Conrad

Same.  Not a specific site issue, just intermittent failures.

zappaDPJ

IDNet's mail server appears to be sending mail out twice.

Just to clarify, that's incoming mail being received twice by me.
zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Zebsy

Having lots of problems using eBay uk on the iPhone thru wifi
I have revolted the router and the phone and it's still not working

zappaDPJ

Quote from: zappaDPJ on Sep 05, 2010, 20:37:35
IDNet's mail server appears to be sending mail out twice.

Just to clarify, that's incoming mail being received twice by me.

On my PC two messages come down more or less at the same time. On my iPhone I get notification of two messages received but there's only one message visible.
zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Simon

Quote from: Zebsy on Sep 05, 2010, 20:43:00
Having lots of problems using eBay uk on the iPhone thru wifi
I have revolted the router and the phone and it's still not working

:welc: :karma:

eBay.co.uk is fine on my iPhone (resolves to wap.ebay.co.uk), as is the eBay app.

Quote from: scook94 on Sep 05, 2010, 20:17:47
Hi Rik, I'm having problems accessing some sites but strangely it's only on my desktop, my laptop (connected via wi-fi) appears fine! I had assumed I'd got infected somehow but hopefully it's an after effect of these upgrades.

http://en-gb.facebook.com seems to be one, as does http://www.play.com and http://www.crackberry.com

pings return - Ping request could not find host
tracert returns - Unable to resolve target system name.


EDIT: Just realised my laptop is using a VPN connection so I can access my work's intranet, that'll explain why it seems okay.

Hi Steven,

No problems here with play.com or crackberry.  Have you tried a DNS flush?
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

scook94

Quote from: Simon on Sep 05, 2010, 20:59:17
:welc: :karma:

eBay.co.uk is fine on my iPhone (resolves to wap.ebay.co.uk), as is the eBay app.

Hi Steven,

No problems here with play.com or crackberry.  Have you tried a DNS flush?

Yes, several times, several router reboots too. Even reset my tcp/ip settings.

ebay.co.uk isn't working for me either.
Steven
--------

Conrad

Now I am having trouble sending e-mails.  Just had to retry 3 times to send via my own server.  Grrrr.

lozcart

Are the current problems possibly area related, my connection went down this morning and my router completely locked out this afternoon due to the idnet updates. However now my connection is flying along and no problems with ebay, Play, Facebook etc.

I'm Birmingham based 0121.

Zebsy

Glad that eBay works for you.
It works intermittently for me, works for a min or so then completely fails
Not good!

JohnH

Quote from: Simon on Sep 05, 2010, 20:59:17
Have you tried a DNS flush?

DNS flush did not work for me, nor router or PC reboot. Only thing that does is refreshing pages, as many as 4-5 times.
Also having problems in sending emails.

Everything was okay until late afternoon.

wecpcs

Quote from: JohnH on Sep 05, 2010, 21:22:03
DNS flush did not work for me, nor router or PC reboot. Only thing that does is refreshing pages, as many as 4-5 times.
Also having problems in sending emails.

Everything was okay until late afternoon.

Snap.

Colin

Zebsy


JB

Unable to access IDNetters from Telefonica in Spain. Traceroute below if it helps.
Presently accessing via a VPN to my UK system on the IDNet system.


Tracing route to www.idnetters.co.uk [212.69.36.28]
over a maximum of 30 hops:

  1     1 ms     1 ms    <1 ms  192.168.0.2
  2    46 ms    43 ms    45 ms  192.168.153.1
  3    45 ms    47 ms    47 ms  145.Red-80-58-116.staticIP.rima-tde.net [80.58.1
16.145]
  4    58 ms    55 ms    57 ms  So5-0-0-0-grtmadno1.red.telefonica-wholesale.net
[84.16.11.49]
  5    53 ms    55 ms    54 ms  Xe7-1-1-0-grtmadpe3.red.telefonica-wholesale.net
[84.16.13.214]
  6    83 ms    81 ms    80 ms  Xe1-1-0-grtparix1.red.telefonica-wholesale.net [
213.140.49.150]
  7    78 ms    78 ms    84 ms  Cogent-1-0-0-grtparix1.red.telefonica-wholesale.
net [213.140.52.134]
  8    77 ms    78 ms    82 ms  Cogent-7-3-0-grtparix1.red.telefonica-wholesale.
net [213.140.52.210]
  9    91 ms    74 ms    79 ms  te0-4-0-4.mpd22.par01.atlas.cogentco.com [130.11
7.1.21]
10    91 ms    90 ms    88 ms  te2-1.mpd01.lon02.atlas.cogentco.com [130.117.50
.137]
11    86 ms    84 ms    84 ms  te2-1.mpd01.lon02.atlas.cogentco.com [130.117.50
.137]
12     *        *        *     Request timed out.
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.
JB

'Keyboard not detected ~ Press F1 to continue'

Lance

About half hour ago I couldn't access idnet.net, idnetters.co.uk or the webmail over my work VPN (BT connection).
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

Steve

I think I've been spared as apart from ppp loss this am I've not noted any issues.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Conrad

I just tried calling IDnet cust svc (01462480092) and got the "we are closed" message.  Didn't leave a voicemail (but I might do soon).  Does anyone know what the official word is on the situation? Is there a number we can call to get an update?  I know the answer will probably just be "Major Service Outage in the BT network", but I'd like to know whether engineers are at least on the case.

Oh, I'm on the Rayleigh exchange if that helps at all.

Steve

It's clearly evident that there are still routing issues and IDNet will be working on them until they are resolved. Although it's very frustrating I don't think there is anything anyone can do except wait. :(
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Azy

i just put in these open dns numbers  208.67.220.220 and 208.67.222.222

and now the internet is working again
What you got back home, little sister, to play your fuzzy warbles on? I bet you got, say, pitiful, portable picnic players. Come with uncle and hear all proper! Hear angels' trumpets and devils' trombones. You are invited!

Conrad

#24
So is it an IDnet DNS server issue?  Can anyone confirm that?

EDIT:  Looks like that may have just been coincidence.  T'internet seems to be working again  :red: on IDnet DNS servers.

Yay!

It appears to have settled down nicely.  NOW don't touch anything!