News:

Welcome to the Golf Club Atlas Discussion Group!

Each user is approved by the Golf Club Atlas editorial staff. For any new inquiries, please contact us.


BCrosby

  • Karma: +0/-0
Log on problems
« on: July 11, 2008, 05:08:04 PM »
I continue to be unable to open this site during normal business hours. Is this just me or are others also having the same problems? BTW, I've had this problem for about a month. Is it a matter of overload/too many visitors?

If it is just me, does anyone have any ideas about what I should do differently to open this site?

Or have I and I alone deeply offended someone very important?

Bob


Sean_Tully

  • Karma: +0/-0
Re: Log on problems
« Reply #1 on: July 11, 2008, 05:13:36 PM »
Bob,

Same here. It is rather hit or miss, but mostly miss. Hope there is some solution to this.

Tully

RSLivingston_III

  • Karma: +0/-0
Re: Log on problems
« Reply #2 on: July 11, 2008, 05:22:20 PM »
I continue to be unable to open this site during normal business hours. Is this just me or are others also having the same problems? BTW, I've had this problem for about a month. Is it a matter of overload/too many visitors?

If it is just me, does anyone have any ideas about what I should do differently to open this site?

Or have I and I alone deeply offended someone very important?

Bob



Once you get a post count over 4000 everything will work right...
"You need to start with the hickories as I truly believe it is hard to get inside the mind of the great architects from days gone by if one doesn't have any sense of how the equipment played way back when!"  
       Our Fearless Leader

BCrosby

  • Karma: +0/-0
Re: Log on problems
« Reply #3 on: July 11, 2008, 05:22:55 PM »
Tully -

Misery loves company. Is the site overloaded? I can't even get the main page to open up 9 to 5.

Bob

BCrosby

  • Karma: +0/-0
Re: Log on problems
« Reply #4 on: July 11, 2008, 05:24:13 PM »
Ralph - So it's merit-based?   ;)

Kalen Braley

  • Karma: +0/-0
Re: Log on problems
« Reply #5 on: July 11, 2008, 05:26:38 PM »
Bob,

Where do you live?  It could be that your local Metro Network just gets swamped during business hours in your particular area and gives up on your Http requests.  Do you have problems hitting other small sites during these same hours?

Kalen

BCrosby

  • Karma: +0/-0
Re: Log on problems
« Reply #6 on: July 11, 2008, 05:33:16 PM »
Kalen -

I have about 25 sites on my favorites list. I have this problem only with GCA. So I doubt its an area network overload issue.

Bob 

Peter Wagner

Re: Log on problems
« Reply #7 on: July 11, 2008, 05:50:14 PM »
Bob,

It doesn't matter where you live.  Try this:

Open your 'cookies' folder in your browser;
delete all cookies pertaining to GCA.com;
delete all junk cookies;
close and restart your browser;
reopen GCA.com and login with your online name and password.

This will create a new cookie which might fix your problem.  It sounds like you have a conflict there.

I hope that fixes the problem.

- Peter


BCrosby

  • Karma: +0/-0
Re: Log on problems
« Reply #8 on: July 11, 2008, 05:53:15 PM »
Thanks Peter. I will give it a try. 

Bob

John Kirk

  • Karma: +0/-0
Re: Log on problems
« Reply #9 on: July 11, 2008, 05:54:16 PM »
Bob,

I have trouble opening up the site about 20% of the time over the last 3 months.

Just adding data.

JK

Kalen Braley

  • Karma: +0/-0
Re: Log on problems
« Reply #10 on: July 11, 2008, 05:57:20 PM »
Bob,

It very well could matter where you live because you may have a different physical path to Australia.  Are you on the east coast or west coast?

After running some diagnostics, I found the following on GCA.com's IP address which is: 202.76.250.102

The registered host is:

inetnum:      202.76.248.0 - 202.76.251.255
netname:      SITESUITE
descr:        SiteSuite Australiasia P/L,
descr:        Website / Content Management provider.
descr:        Broadway, Sydney - Australia.
country:      AU
« Last Edit: July 11, 2008, 06:12:24 PM by Kalen Braley »

Kalen Braley

  • Karma: +0/-0
Re: Log on problems
« Reply #11 on: July 11, 2008, 06:19:51 PM »
Bob,

You can use this tool to see how you connect to GCA.com in Australia. http://visualroute.visualware.com/


In my case I go from SLC, to Dallas, to Phoneix, to LA, then SJ.  From there it takes a router hop to NZ, before finally being re-directed to the Sydney area.  I suspect you take a different route there.

Just select "My Computer" as the starting point and GCA.com's IP address (202.76.250.102) as the destination and push the start button.  ;)
« Last Edit: July 11, 2008, 06:25:39 PM by Kalen Braley »

Scott Szabo

  • Karma: +0/-0
Re: Log on problems
« Reply #12 on: July 11, 2008, 06:46:48 PM »
I have been having the same problems for the better part of a couple weeks.  Glad I'm hearing that I'm not alone in this.....
"So your man hit it into a fairway bunker, hit the wrong side of the green, and couldn't hit a hybrid off a sidehill lie to take advantage of his length? We apologize for testing him so thoroughly." - Tom Doak, 6/29/10

Joe Bausch

  • Karma: +0/-0
Re: Log on problems
« Reply #13 on: July 11, 2008, 07:08:25 PM »
I'm a pseudo computer geek and like this tracing stuff.  Here is the route from Wayne PA to GCA.com using the unix command traceroute:

powerbook.local:bausch%traceroute golfclubatlas.com
traceroute to golfclubatlas.com (202.76.250.102), 64 hops max, 40 byte packets
 1  10.0.1.1 (10.0.1.1)  3.307 ms  1.135 ms  0.955 ms
 2  * * *
 3  ge-2-2-ur01.upperdarby.pa.panjde.comcast.net (68.86.154.145)  8.960 ms  9.698 ms  8.298 ms
 4  te-1-1-ur01.wallingford.pa.panjde.comcast.net (68.86.208.182)  9.823 ms  76.000 ms  21.303 ms
 5  po-10-ur02.wallingford.pa.panjde.comcast.net (68.86.208.186)  62.547 ms  10.854 ms  10.824 ms
 6  po-70-ar01.wallingford.pa.panjde.comcast.net (68.86.208.190)  9.985 ms  12.035 ms  70.346 ms
 7  te-3-2-ar01.401nbroadst.pa.panjde.comcast.net (68.86.90.14)  14.022 ms  11.773 ms  75.990 ms
 8  pos-0-5-0-0-cr01.philadelphia.pa.ibone.comcast.net (68.86.90.13)  12.117 ms  9.894 ms  78.656 ms
 9  pos-0-9-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.85.14)  18.545 ms  30.151 ms  25.452 ms
10  xe-10-1-0.edge1.newyork2.level3.net (4.78.169.45)  14.416 ms  14.475 ms  14.879 ms
11  4.68.63.150 (4.68.63.150)  151.711 ms  17.147 ms  26.985 ms
12  ae-2.r21.nycmny01.us.bb.gin.ntt.net (129.250.2.40)  20.560 ms  38.015 ms  13.100 ms
13  p64-2-0-0.r20.chcgil09.us.bb.gin.ntt.net (129.250.5.4)  46.589 ms  48.076 ms  47.608 ms
14  ae-0.r21.chcgil09.us.bb.gin.ntt.net (129.250.3.98)  134.386 ms  48.055 ms  45.564 ms
15  p64-3-1-0.r20.snjsca04.us.bb.gin.ntt.net (129.250.5.20)  112.530 ms  113.260 ms  114.531 ms
16  ae-1.r21.plalca01.us.bb.gin.ntt.net (129.250.5.32)  118.678 ms  124.157 ms  113.781 ms
17  xe-3-4.r03.plalca01.us.bb.gin.ntt.net (129.250.4.246)  125.895 ms  113.665 ms  114.397 ms
18  ge-0.tnzi.plalca01.us.bb.gin.ntt.net (129.250.10.74)  116.331 ms  113.270 ms  114.616 ms
19  * p5-1.sjbr1.global-gateway.net.nz (202.37.245.229)  99.866 ms *
20  * * *
21  * * *
22  * * *
23  gigabitethernet2-0.cor3.syd.connect.com.au (203.63.170.240)  253.026 ms  252.012 ms *
24  dpow3179-11.gw.connect.com.au (210.9.81.233)  253.037 ms * *
25  as24483-1.syd1.webcentral.com.au (210.247.196.73)  251.469 ms  252.953 ms gigabitethernet2-0.cor3.syd.connect.com.au (203.63.170.240)  257.126 ms
26  as24483-1.syd1.webcentral.com.au (210.247.196.73)  263.303 ms  270.315 ms  251.471 ms

I have no idea why it stalls for many seconds in New Zealand.... must be some crazy Kiwis watching a cricket match instead of IP requests.  ;)
@jwbausch (for new photo albums)
The site for the Cobb's Creek project:  https://cobbscreek.org/
Nearly all Delaware Valley golf courses in photo albums: Bausch Collection

MargaretC

Re: Log on problems
« Reply #14 on: July 11, 2008, 07:45:52 PM »
I continue to be unable to open this site during normal business hours. Is this just me or are others also having the same problems? BTW, I've had this problem for about a month. Is it a matter of overload/too many visitors?

If it is just me, does anyone have any ideas about what I should do differently to open this site?

Or have I and I alone deeply offended someone very important?

Bob



Hi, Bob!

I was unable to log onto this site from my office and just assumed that the IT folks did something.  ::)  Whatever the case, I go to "google" and "search" Golf Club Atlas.com and and use that link to get into the site.  Never had a problem since.  Not a direct approach, but it works!   8)

Meg

Kevin_Reilly

  • Karma: +0/-0
Re: Log on problems
« Reply #15 on: July 11, 2008, 11:01:29 PM »
I posted in the other thread that I've had the same problem accessing the site from my office in SF for the past month or so.  Very hit or miss.  More miss than hit.
"GOLF COURSES SHOULD BE ENJOYED RATHER THAN RATED" - Tom Watson

TEPaul

Re: Log on problems
« Reply #16 on: July 11, 2008, 11:14:25 PM »
Bob:

I put a thread on here around 12:30 about your problem just after I talked to you about 12:30. I figured the contributors out there may be able to address your problem better than Ran or Ben could. It got a lot of play but it's already on the second page.

I think threads are "streaming" a little too fast on this website these days.

BCrosby

  • Karma: +0/-0
Re: Log on problems
« Reply #17 on: July 12, 2008, 09:33:23 AM »
Thanks Tom.

Margaret - I had the same clever idea, but was not successful. I searched GCA on Google, up it popped, I clicked on the home page, boom, that "can't locate server" thingy pops up.

Perhaps its the path to ATL, though I got IM'ed from a friend down the street who said he is having no problems.

It sounds like others are having similar problems in other parts of the US. My best guess is that the site server is getting overwhelmed during the day. I hope Ben Dewar or someone will look into it.

Bob 

TEPaul

Re: Log on problems
« Reply #18 on: July 12, 2008, 10:43:56 AM »
BobC:

As I said on the other thread it might be appropriate to check with your office manager. Maybe he just loaded GOLFCLUBATLAS.com into the office "site blocker" software with all those child pornography websites and such.

Tags:
Tags:

An Error Has Occurred!

Call to undefined function theme_linktree()
Back