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 24758 times)
kitz

Posts: 4323

WWW
« Reply #15 on: September 12, 2006, 05:49:49 pm »

Does this help

How to perform a tracecert

How to save or output ping/tracert results

Dont forget the Geeks!
kitz 2005
Mistral

Posts: 22

« Reply #16 on: September 12, 2006, 06:28:02 pm »

I have tried closing down my computer and re starting but still no joy,

I'll ask my boss to reboot the system tomorrow if you think that may help

If you are failing to get the first hop back on a local lan then either something serious is up or your office has some sort of firewall in it. Chances are its the later of the to.

and the firewall is probably there to keep people out on the outside and keep people doing what they are meant to be doing ont he inside.

Blue

Posts: 29

« Reply #17 on: September 13, 2006, 09:47:00 am »

Hi everyone,

firstly our system re boots every morning.

Secondly  I tried to do what Mystery FCM suggested with the "tracert.bat"  I pasted the details into notepad, saved it as "tracert.bat" on desktop.   that gave me an icon on my front screen, which when I double click gave me a black box with the heading
c:\windows\system32/cmd.exe   then nothing else happens

I also tried to use Kitz how to perform a tracert and how to save or output ping/tracert results and guess what

I get The server at www.kitz.co.uk is taking too long to respond.

what I don't understand is on Monday it worked perfectly then on Tuesday I get the timed out message, why would this happen ?
Blue

Posts: 29

« Reply #18 on: September 13, 2006, 10:11:51 am »

I tjhink I've done the tracert  these are the results

Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

C:\DOCUME~1\LIN>tracert www.doglistener.co.uk

Tracing route to homepages.plus.net [212.159.9.131]
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.
kitz

Posts: 4323

WWW
« Reply #19 on: September 13, 2006, 10:21:39 am »

>> I get The server at www.kitz.co.uk is taking too long to respond.

hmmm....  so you cant get to my site either... 
theres a surprise since it also resolves to [212.159.9.131] rolleyes

Who configures the network.. (since it happens on all the PCs there) is this a firewall issue?

Dont forget the Geeks!
kitz 2005
Blue

Posts: 29

« Reply #20 on: September 13, 2006, 10:28:09 am »

Thank you for replying, its not a firewall issue or so I've been told.  We have an outside guy who looks after our computer systems.

I don't understand why it was all working perfectly ok on Monday but not on Tuesday.

Is this something I'm just going to have to wait and see if it resolves itself
Blue

Posts: 29

« Reply #21 on: September 13, 2006, 11:19:03 am »

Well, even more strange now,  have I got gremlins in my computer  huh

I'm back into the www.doglistener.co.uk  site  grin

I just tried it and up it came.  I've been in contact with the person that owns the site and explained what has been going on just in case its his end.



OK OK spoke to soon, just went to go back in and its gone again,  this is very strange. huh huh huh
« Last Edit: September 13, 2006, 11:28:07 am by Blue »
kitz

Posts: 4323

WWW
« Reply #22 on: September 13, 2006, 11:38:12 am »

>> so I guess it's not my end thats got the trouble is it

Not so sure...  There's something thats blocking access from that location.

You also couldnt get to my site which is also hosted on the same server.
TBH..  if people were having problems accessing my site then there would likely be murmurs somewhere or other.

Dont forget the Geeks!
kitz 2005
Blue

Posts: 29

« Reply #23 on: September 13, 2006, 11:43:25 am »

you say there might be something blocking access, any ideas as to what that could be,

as I say one minute it lets me access the website, then it goes again
James

Posts: 1010


3567190798

« Reply #24 on: September 13, 2006, 01:59:22 pm »

Could one possibility could be differing rules on firewalls/proxy servers?
Perhaps one time your network routes your connection through one, and another time through a different one with different rules set on it?

Tracerts can also be blocked seperately, so the lack of tracert could be related, or completely seperate.

Not much help I'm afraid.

Best Wishes - James

Tell me and I'll forget; show me and I may remember; involve me and I'll understand. - Chinese Proverb
Blue

Posts: 29

« Reply #25 on: September 13, 2006, 02:10:51 pm »

No one here would block access to a website, we're allowed to use the internet.

Its baffling isn't it.  huh
Blue

Posts: 29

« Reply #26 on: September 15, 2006, 09:08:57 am »

OK so I can now access the home page, it just came back up,   I can get into everything in the menu except the forum pages

http://ccgi.doglistener.co.uk/cgi-bin/DGLforum/YaBB.pl#dog_chat
http://ccgi.doglistener.co.uk/cgi-bin/DGLforum/YaBB.pl

   I have been in contact with the guy who's web page it is and he has said that everyone else is ok and can get access.

Any ideas as to why I can't access this page ?


BTW Kitz I can now access your website as well

« Last Edit: September 15, 2006, 10:26:03 am by Blue »
mikeb

Posts: 656


« Reply #27 on: September 15, 2006, 10:35:55 am »

lookup on doglistener.co.uk = 212.159.8.1 (doglistener.co.uk)

lookup on www.doglistener.co.uk = 212.159.9.131 (homepages.plus.net)

lookup on ccgi.doglistener.co.uk = 84.92.1.4 (ccgi.plus.net)

Erhm, I don't pretend to understand I know how domain names,  DNS lookups and routing etc. work but that looks 'interesting' (AKA confusing !)  Is there something a bit cooky with the DNS there or am I being stupid ?

Incidentally, just tried the links above and they didn't work - timed out eventually.  Tried again and the same. Tried again and no probs.  Hmmmm, I've seen this before and get something similar on a variety of different sites myself quite often.  It almost looks like the first time (or few times) you try to access a particular site nothing happens but a couple of tries or refreshes later it works without problem and then continues to do so thereafter. Now it can't possibly be that the sites in question just happened to be down or whatever at that particular time so something DNS or cache related methinks  undecided

--
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.
Colin
Usergroup Member

Posts: 6339


WWW
« Reply #28 on: September 15, 2006, 10:41:07 am »

lookup on doglistener.co.uk = 212.159.8.1 (doglistener.co.uk)

lookup on www.doglistener.co.uk = 212.159.9.131 (homepages.plus.net)

lookup on ccgi.doglistener.co.uk = 84.92.1.4 (ccgi.plus.net)

Erhm, I don't pretend to understand I know how domain names,  DNS lookups and routing etc. work but that looks 'interesting' (AKA confusing !)  Is there something a bit cooky with the DNS there or am I being stupid ?

All looks fine to me...

Colin Ogilvie
Plusnet Usergroup Member
Using: Plusnet Extra
MysteryFCM

Posts: 124


WWW
« Reply #29 on: September 15, 2006, 10:42:56 am »

lookup on doglistener.co.uk = 212.159.8.1 (doglistener.co.uk)

lookup on www.doglistener.co.uk = 212.159.9.131 (homepages.plus.net)

lookup on ccgi.doglistener.co.uk = 84.92.1.4 (ccgi.plus.net)

Erhm, I don't pretend to understand I know how domain names,  DNS lookups and routing etc. work but that looks 'interesting' (AKA confusing !)  Is there something a bit cooky with the DNS there or am I being stupid ?

Nope, the DNS is correct .......

Incidentally, just tried the links above and they didn't work - timed out eventually.  Tried again and the same. Tried again and no probs.  Hmmmm, I've seen this before and get something similar on a variety of different sites myself quite often.  It almost looks like the first time (or few times) you try to access a particular site nothing happens but a couple of tries or refreshes later it works without problem and then continues to do so thereafter. Now it can't possibly be that the sites in question just happened to be down or whatever at that particular time so something DNS or cache related methinks  undecided

Couldn't access the links here either. Tried earlier aswell and it timed out then aswell.

Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk
Pages: 1 [2] 3 4 5
  Print  
 
Jump to: