Home   Help Search Groups Login Register  
You are not logged in. To get the full experience of these forums, we recommend you log in or register
Plusnet Usergroup » All Users - The Open Forum » Plusnet Network and Technical Issues » Web site taking too long to respond
Pages: 1 2 3 [4] 5
  Print  
Author Topic: Web site taking too long to respond  (Read 24765 times)
kitz

Posts: 4323

WWW
« Reply #45 on: September 25, 2006, 09:05:24 am »

>>> they suggested possible some servers down somewhere.

All seems to be ok from here

C:\Documents and Settings\kitz>tracert www.freewebs.com

Tracing route to www.freewebs.com [38.119.100.2]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.7.100
  2    20 ms    18 ms    27 ms  lo0-plusnet.ptn-ag2.plus.net [195.166.128.53]
  3    16 ms    16 ms    17 ms  ge1-0-0-204.ptn-gw2.plus.net [84.92.3.106]
  4    15 ms    15 ms    18 ms  ge0-0-0-23.pte-gw1.plus.net [212.159.4.25]
  5    16 ms    16 ms    16 ms  gi1-1-22.pte-gw5.plus.net [212.159.4.7]
  6    18 ms    16 ms    16 ms  195.66.224.185
  7    88 ms    89 ms    88 ms  t8-1.mpd03.jfk02.atlas.cogentco.com [66.28.4.41]
  8    94 ms   103 ms    95 ms  t9-4.mpd01.dca01.atlas.cogentco.com [154.54.6.138]
  9    95 ms    95 ms    95 ms  g1-4.mpd01.iad03.atlas.cogentco.com [154.54.5.222]
 10    95 ms    94 ms    98 ms  herndon2-2.freewebs.com [38.119.100.2]

Trace complete.


Other sites seem to be ok too aside from ccgi.doglistener.co.uk which is probably more down to the fact that the cgi servers are playing up - but thats been mentioned in another thread



Dont forget the Geeks!
kitz 2005
mikeb

Posts: 656


« Reply #46 on: September 25, 2006, 09:28:56 am »

All links except the cgi (forum) ones are working fine for me also - on PN connection.

The cgi problem was apparently resolved at 11:34 yesterday although that service.status post was perhaps a bit premature as it was a fair old while later before the DNS responses actually became consistent Wink  Still seem to be some peeps reporting cgi probs in general tho so maybe it's not just the site you're trying to access Sad  Have no idea why the other links don't work for you tho.

Edited to add:

[clutching_at_straws]
I presume you're using Firefox going by the error message "taking too long" rather than "Can't find server or DNS error" Have you tried using IE or some other browser just in case it's some strange cache/cookie/popup/config type issue in Firefox ?  Also, have you checked that you haven't got some dodgy hosts file on your system ?
[/clutching_at_straws]
« Last Edit: September 25, 2006, 10:29:41 am by mikeb »

--
WARNING: The e-mail address on my profile is not my usual address, all messages sent via this site have been redirected elsewhere for test purposes. This could result in messages not being received in a timely manner or potentially not being received at all.
mikeb

Posts: 656


« Reply #47 on: September 25, 2006, 10:11:46 am »

[more_straw_clutching]
OK, bearing in mind my knowledge on DNS stuff is rather limited to say the least, is this of any consequence:

CNAME entry for ccgi.doglistener.co.uk -> ccgi.plus.net

There is NO CNAME entry for ccgi.kitz.co.uk

The other day when cgi stuff was (sort of) working OK, I could access ccgi.kitz.co.uk without problem but ccgi.doglistener.co.uk invariably timed out or at at best took a very long time. Must add that neither work right now tho.
[/more_straw_clutching]

Code:
How I am searching:
Searching for ccgi.doglistener.co.uk ALL record at h.root-servers.net [128.63.2.53]: Got referral to ns1.nic.uk. (zone: uk.) [took 10 ms]
Searching for ccgi.doglistener.co.uk ALL record at ns1.nic.uk. [195.66.240.130]: Got referral to ns1.plusnet.co.uk. (zone: doglistener.co.uk.) [took 235 ms]
Searching for ccgi.doglistener.co.uk ALL record at ns1.plusnet.co.uk. [195.166.128.17]: Got CNAME of ccgi.plus.net. and referral to g.root-servers.net [took 88 ms]
Searching for ccgi.plus.net ALL record at m.root-servers.net [202.12.27.33]: Got referral to I.GTLD-SERVERS.net. (zone: net.) [took 126 ms]
Searching for ccgi.plus.net ALL record at I.GTLD-SERVERS.net. [192.43.172.30]: Got referral to ns2.force9.net. (zone: plus.net.) [took 125 ms]
Searching for ccgi.plus.net ALL record at ns2.force9.net. [195.166.128.17]: Reports ccgi.plus.net. [took 86 ms]

Answer:

Domain Type Class TTL Answer
ccgi.plus.net. A IN 86400 84.92.1.4
plus.net. NS IN 86400 ns1.force9.net.
plus.net. NS IN 86400 ns2.force9.net.
ns1.force9.net. A IN 86400 195.166.128.16
ns2.force9.net. A IN 86400 195.166.128.17

Code:
How I am searching:
Searching for ccgi.kitz.co.uk ALL record at g.root-servers.net [192.112.36.4]: Got referral to NS3.NIC.uk. (zone: uk.) [took 41 ms]
Searching for ccgi.kitz.co.uk ALL record at NS3.NIC.uk. [213.219.13.131]: Got referral to ns2.force9.net. (zone: kitz.co.uk.) [took 81 ms]
Searching for ccgi.kitz.co.uk ALL record at ns2.force9.net. [195.166.128.17]: Reports ccgi.kitz.co.uk. [took 86 ms]

Answer:

Domain Type Class TTL Answer
ccgi.kitz.co.uk. A IN 14400 84.92.1.4
kitz.co.uk. NS IN 14400 ns2.force9.net.
kitz.co.uk. NS IN 14400 ns1.force9.net.
ns1.force9.net. A IN 86400 195.166.128.16
ns2.force9.net. A IN 86400 195.166.128.17





« Last Edit: September 25, 2006, 10:14:18 am by mikeb »

--
WARNING: The e-mail address on my profile is not my usual address, all messages sent via this site have been redirected elsewhere for test purposes. This could result in messages not being received in a timely manner or potentially not being received at all.
Blue

Posts: 29

« Reply #48 on: September 25, 2006, 10:29:54 am »

this is what I got this morning

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\lin>tracert www.freewebs.com

Tracing route to www.freewebs.com [38.119.100.2]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 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.
 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.

C:\Documents and Settings\lin>


Colin
Usergroup Member

Posts: 6339


WWW
« Reply #49 on: September 25, 2006, 11:23:52 am »

Quote
C:\Documents and Settings\lin>tracert www.freewebs.com

Tracing route to www.freewebs.com [38.119.100.2]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.

To me, that looks like an internal problem...

Colin Ogilvie
Plusnet Usergroup Member
Using: Plusnet Extra
kitz

Posts: 4323

WWW
« Reply #50 on: September 25, 2006, 01:22:13 pm »

>> To me, that looks like an internal problem...

It does indeed...
It would seem the request isnt even getting as far as your works router.

Theres no response from the router hop.. nor anything after that..

Dont forget the Geeks!
kitz 2005
mikeb

Posts: 656


« Reply #51 on: September 25, 2006, 04:25:44 pm »

To me, that looks like an internal problem...

That's what I thought ages ago but I got the impression that ping/tracert could be blocked on the network from comments made earlier in the thread.

Blue, try doing a tracert for a site that DOES work reliably and see what you get.  If that returns a sensible response (i.e. similar to the result kitz posted above rather than timing out at every hop) then I think you most definitely need to take a big stick to the "outside guy who looks after our computer systems"  wink  Although, TBH, I think I'd probably have shown him the business end of a pointy stick by now in any case with all the problems you've been having  grin

Go on, you know you want to !!
« Last Edit: September 25, 2006, 04:29:30 pm by mikeb »

--
WARNING: The e-mail address on my profile is not my usual address, all messages sent via this site have been redirected elsewhere for test purposes. This could result in messages not being received in a timely manner or potentially not being received at all.
Blue

Posts: 29

« Reply #52 on: September 25, 2006, 05:12:48 pm »

here is two sites I use quite a lot  and the results

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\lin>tracert www.surreyladieshockeyleague.co.uk

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

  1    <1 ms    <1 ms    <1 ms  brickwall.jdevine.co.uk [192.168.100.6]
  2    69 ms    57 ms    41 ms  lo0-plusnet.pte-ag1.plus.net [195.166.128.64]
  3    25 ms    19 ms    23 ms  ge0-0-0-403.pte-gw1.plus.net [84.92.4.1]
  4    19 ms    19 ms    23 ms  gi1-1-22.pte-gw5.plus.net [212.159.4.7]
  5    24 ms    20 ms    20 ms  lonap-secondary.th.hiway.co.uk [193.203.5.70]
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 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.
 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.


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\lin>tracert www.amazon.co.uk

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

  1    <1 ms    <1 ms    <1 ms  brickwall.jdevine.co.uk [192.168.100.6]
  2    49 ms    77 ms    46 ms  lo0-plusnet.pte-ag1.plus.net [195.166.128.64]
  3    31 ms    25 ms    24 ms  ge0-0-0-403.pte-gw1.plus.net [84.92.4.1]
  4    21 ms    20 ms    28 ms  195.50.117.169
  5    21 ms    23 ms    21 ms  ae-0-51.bbr1.London1.Level3.net [4.68.116.1]
  6    31 ms    33 ms    33 ms  so-2-0.hsa1.Dublin1.Level3.net [4.68.128.114]
  7     *        *        *     Request timed out.
  8     *        *     213.242.106.46  reports: Destination net unreachable.

Trace complete.




www.doglistener.co.uk  -  ccgi .doglistener.co.uk  -   www.freewebs.com   all just time out straight away.



Had a reply from our computer guy and he says it is definatley NOT a problem with our internet connection here, he says the problem is with the website server of the websites I am visiting or trying to visit, so if this is right how do I tell them I have a problem




Colin
Usergroup Member

Posts: 6339


WWW
« Reply #53 on: September 25, 2006, 05:16:49 pm »

If you are getting a tracert full for "Request timed out." for the sites that aren't working, I'm not sure how it can be a problem externally!

Colin Ogilvie
Plusnet Usergroup Member
Using: Plusnet Extra
mikeb

Posts: 656


« Reply #54 on: September 25, 2006, 05:59:46 pm »

Had a reply from our computer guy and he says it is definatley NOT a problem with our internet connection here, he says the problem is with the website server of the websites I am visiting or trying to visit, so if this is right how do I tell them I have a problem

It just has to be most likely a problem with your PC, network or router rather than the actual connection or remote websites (excluding the cgi issues anyway).  I certainly think you need to get the pointy stick out that's for sure !  You could perhaps try getting the guy to look at this thread to see if that convinces him to think again Wink

The first tracert should look something like this:

Code:
1 10 ms 192.168.1.1 Router-adsl
2 29 ms 195.166.128.64 lo0-plusnet.pte-ag1.plus.net
3 27 ms 84.92.4.1 ge0-0-0-403.pte-gw1.plus.net
4 * * no response * - - -
5 24 ms 193.203.5.70 lonap-secondary.th.hiway.co.uk
6 27 ms 195.12.4.223 thouse-gw11.hiway.co.uk
7 39 ms 195.12.0.2 ptl-gw2.hiway.co.uk
8 37 ms 195.12.1.43 ptl-sw3.hiway.co.uk
9 30 ms 195.12.29.1 www.surreyladieshockeyleague.co.uk

BTW, the 'no response' at hop 4 is quite 'normal' for my tracert and is quite likely still due to a long-term and known about checksum error in the response from that piece of kit (212.159.4.7) i.e. a firmware bug !

HOWEVER, I just tried to do an M$ (WIN98) tracert to see what happens there and I get everything timed out after hop 5 just the same as you did !!!  Very, very strange and now I'm *REALLY* confused  cry  I still think it's long past pointy stick time tho Wink  And the best of luck trying to convince him to sort it or at least investigate the problem on site.
« Last Edit: September 25, 2006, 06:05:14 pm by mikeb »

--
WARNING: The e-mail address on my profile is not my usual address, all messages sent via this site have been redirected elsewhere for test purposes. This could result in messages not being received in a timely manner or potentially not being received at all.
Blue

Posts: 29

« Reply #55 on: September 25, 2006, 06:29:38 pm »

Don't know if this helps but I've accessed the www.doglistener.co.uk and ccgi.doglistener.co.uk from home and found out that a lot of people have had the same problem  this is what the owner of the site wrote today

"May be Plusnet and the CGI platform Plusnet are my ISPs. Though on there service update they are telling me that problems exist with the CGI platform. "
Colin
Usergroup Member

Posts: 6339


WWW
« Reply #56 on: September 25, 2006, 06:30:50 pm »

That would affect it but shouldn't stop your traceroutes AFAIK.

Colin Ogilvie
Plusnet Usergroup Member
Using: Plusnet Extra
kitz

Posts: 4323

WWW
« Reply #57 on: September 26, 2006, 01:30:37 am »

Hi Blue

The tracert to http://www.surreyladieshockeyleague.co.uk/ is perfectly normal and there is nothing wrong with that at all.  The asterisks at the end is simply because the webserver is firewalled not to respond to pings.

Although the amazon one looks a bit weird there isnt anything wrong as such with it and I see the same thing

Report for www.amazon.co.uk [87.238.81.129]

Analysis: Connections to HTTP port 80 on host  'www.amazon.co.uk'  are working, but ICMP packets are being blocked past network  "DUBLIN-CUSTOMER-LINKS"  at hop 8. It is a HTTP server (running Server). Node 213.242.106.46 at hop 8 in network  "DUBLIN-CUSTOMER-LINKS"  reports "The destination network is unreachable".


it doesnt actually stop the site from being viewable.


The suggestion to show the network guy this thread is quite a good idea..
but the overwhelming evidence is the fact that you can perform tracert outside of your local network, except for when it comes to the sites that you cant view..  its blocked before it even reaches the router.

It cant be a problem with the remote webserver, because traffic doesnt even get that far.
Therefore it has to be something on the PC or the router thats blocking traffic.

>> found out that a lot of people have had the same problem 

Dont get distracted by that..  there is a problem with the ccgi servers atm, where some people cant access them because they are under heavy load.  Your problem started before this.. and as colin has quite rightly pointed out.. it does not stop you from being able to perform a tracert to them...  your problem is certainly looking to be local.

Dont forget the Geeks!
kitz 2005
Blue

Posts: 29

« Reply #58 on: October 27, 2006, 12:01:27 pm »

Just to give you an update, still can't access the website, still says
The server at ccgi.doglistener.co.uk is taking too long to respond.

Our computer guy says its definatley not here and its the other guys server,
have found out that he uses plus net as well.  (None of the computers in the building are able to access it)

Could there be a problem with his server, if so is there anything that can be done.
kitz

Posts: 4323

WWW
« Reply #59 on: October 30, 2006, 01:47:17 pm »

>> its the other guys server
>> Could there be a problem with his server, if so is there anything that can be done.


  • I can access http://www.doglistener.co.uk/ without any problems.. Tracerts to the site are fine and responding in 25ms
  • Other people on PN connections and non PN connections can access the site fine.
  • VisualRoute shows that all is good with the site and is responding in 24ms
  • Netmonitor SiteUp test reports that all is well with the site - linky

  • Completing a report on the site with silktide reports

    Quote
    This website is very quick to respond - Excellent
    Speed Your website responded in 0.19 seconds, and your homepage downloaded in 0.29 seconds. This is very fast and suggests your website is running on a sufficiently powerful web server.

    Above evidence suggests that there is nothing wrong with the server.

    -----------

    As mentioned above - the ccgi problem was something that PN were aware of a couple of weeks ago and affected all sites for a while, its now been fixed and not related to the problem you are seeing.

    -----------

    >> Our computer guy says its definatley not here

    The fact that the site is accessable and fine from eleswhere aside from the work network would point to the fact that it is their network.

    The overwhelming evidence that the problem is local is that when you perform a tracert it times out before it even reaches the work router.

Dont forget the Geeks!
kitz 2005
Pages: 1 2 3 [4] 5
  Print  
 
Jump to: