DPChallenge: A Digital Photography Contest You are not logged in. (log in or register
 

DPChallenge Forums >> Stock Photography >> is Microstockgroup down for you?
Pages:  
Showing posts 1 - 25 of 31, (reverse)
AuthorThread
05/30/2009 06:03:16 AM · #1
This sounds like a sorry attempt at begging for traffic, but I am trying to come to the bottom of a problem.

I have had some complaints, primarily from users from Germany that they can't access the site. I am wondering how many other people are experiencing the same thing. The member(s) with access problems seem to think it is a fairly large area that can't access the site but i haven't had any other complaints. If I do a ping test from various locations, it says the site is up so my web host doesn't see any problems, but yet I still have users having problems.

If you have a second can you check out
microstockgroup.com

and write two things.
could you view the site:
where are you located: ->country is fine, or if you want you can say the town as well.

or any other suggestions on how to see who can and can't access the site?
05/30/2009 06:26:59 AM · #2
Works from Munich, Germany, ISP T-Online.
05/30/2009 06:40:13 AM · #3
Works from Whangarei, NZ (top of the country)
05/30/2009 07:09:43 AM · #4
Works from NJ, USA
05/30/2009 07:52:23 AM · #5
You're up and running in Virginia, US.
05/30/2009 08:24:42 AM · #6
Works from Poplar Bluff, Missouri.

If you can get there from here, you can get there from anywhere...
05/30/2009 10:51:25 AM · #7
works in western north carolina, usa. :)
05/30/2009 03:17:25 PM · #8
thanks guys. It is good to know it seems to be up most places.

It makes it awfully hard to problem solve when I can't see that members problem or where the problem is coming from. I would say it is just him but he says he 'asked around' and others couldn't see the site either. hmmm... ?:(
05/30/2009 05:03:16 PM · #9
It dosn't load for me. I'm in Austin, Texas. The error I get is Network Timeout error. The server at www.microstockgroup.com is taking too long to respond.
05/30/2009 05:09:31 PM · #10
It's loading here mate but it's very, very slow

UK based

ETA: Hmmm when I ping it's not showing it to be as slow as the site is actually performing:

Pinging microstockgroup.com [69.65.98.2] with 32 bytes of data:
Reply from 69.65.98.2: bytes=32 time=123ms TTL=53
Reply from 69.65.98.2: bytes=32 time=97ms TTL=53
Reply from 69.65.98.2: bytes=32 time=102ms TTL=53
Reply from 69.65.98.2: bytes=32 time=104ms TTL=53

Ping statistics for 69.65.98.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 97ms, Maximum = 123ms, Average = 106ms

Message edited by author 2009-05-30 17:13:00.
05/30/2009 06:19:01 PM · #11
Worked great in the Big Sky Country/USA
05/30/2009 06:38:14 PM · #12
Loaded quickly in South Florida.
05/30/2009 06:49:21 PM · #13
Works in Buffalo, NY
05/30/2009 07:05:55 PM · #14
Working in South Africa.
05/30/2009 07:27:26 PM · #15
Originally posted by yanko:

It dosn't load for me. I'm in Austin, Texas. The error I get is Network Timeout error. The server at www.microstockgroup.com is taking too long to respond.


hmm.. well nice to find one problem spot... anyone know how to go about complaining to the web host about this? I can't really just say 'someone' has a problem. I need to have something they can see, or something I can report.
05/30/2009 07:41:10 PM · #16
Get a tracert from the user mate and present that to your host it will give them some idea of where the problem lies.

Incase you are not aware how to:

Open a DOS command prompt and type: tracert www.microstockgroup.com

It will give you a readout like this:

Tracing route to microstockgroup.com [69.65.98.2]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 25 ms 59 ms 20 ms 10.29.40.1
3 25 ms 17 ms 21 ms bmly-cam-1a-v100.network.virginmedia.net [80.1.226.101]
4 55 ms 56 ms 65 ms bmly-t3core-1a-ge-010-0.network.virginmedia.net [80.1.225.41]
5 14 ms 31 ms 18 ms pop-bb-a-so-320-0.network.virginmedia.net [212.43.162.57]
6 51 ms 22 ms 17 ms bre-bb-b-as4-0.network.virginmedia.net [62.255.81.238]
7 40 ms 30 ms 12 ms telc-ic-1-as0-0.network.virginmedia.net [62.253.185.74]
8 23 ms 12 ms 34 ms ldn-b2-link.telia.net [213.248.100.97]
9 22 ms 15 ms 29 ms ldn-bb2-link.telia.net [80.91.252.13]
10 109 ms 97 ms 111 ms ash-bb1-link.telia.net [80.91.251.209]
11 100 ms 99 ms 86 ms hurricane-ic-124167-ash-bb1.c.telia.net [213.248.98.94]
12 113 ms 110 ms 107 ms 209.51.161.10
13 110 ms 141 ms 131 ms r01.iad.keepitsecure.net [69.65.112.1]
14 105 ms 101 ms 112 ms aggr-sw2.iad.defenderhosting.com [69.65.112.94]
15 113 ms 112 ms * eqash9.keepitsecure.net [69.65.115.47]
16 99 ms 115 ms 109 ms vps125.sgvps.net [69.65.98.2]

Trace complete.

05/31/2009 04:59:24 AM · #17
except the site works for me, so my tracert would look good.

I wonder if it could be that I am sharing an IP address with some other site that the IP in some locations decided to block.
05/31/2009 05:26:35 AM · #18
Sorry Leaf I mean't ask those with problems for a tracert report :)
05/31/2009 06:46:45 PM · #19
ah yeah, i see :)

anyone want to offer up their tracert report? or just the problem area? I have sent the info to the person who cannot access the site. Hopefully he is able to give some info as well

Message edited by author 2009-05-31 18:46:58.
05/31/2009 09:06:01 PM · #20
FYI, it's working for me now.
05/31/2009 10:16:47 PM · #21
Originally posted by leaf:

I wonder if it could be that I am sharing an IP address with some other site that the IP in some locations decided to block.

Try to find out if the user is behind a firewall, especially a work-related one.

I think sometimes a corporate IT admin or an ISP will block a whole range of IP addresses, not just the particular one hosting your site, so you could get blocked out because of some other site hosted by your ISP.

PS: the site seems to load up OK for me from Oakland, CA -- it was working yesterday as well.

Message edited by author 2009-05-31 22:18:11.
06/01/2009 01:20:03 AM · #22
Originally posted by GeneralE:

Originally posted by leaf:

I wonder if it could be that I am sharing an IP address with some other site that the IP in some locations decided to block.

Try to find out if the user is behind a firewall, especially a work-related one.

I think sometimes a corporate IT admin or an ISP will block a whole range of IP addresses, not just the particular one hosting your site, so you could get blocked out because of some other site hosted by your ISP.

PS: the site seems to load up OK for me from Oakland, CA -- it was working yesterday as well.


Even if that's not the case getting a dedicated IP just makes good business sense.

Message edited by author 2009-06-01 01:20:18.
06/01/2009 02:40:18 AM · #23
Originally posted by yanko:

Originally posted by GeneralE:

Originally posted by leaf:

I wonder if it could be that I am sharing an IP address with some other site that the IP in some locations decided to block.

Try to find out if the user is behind a firewall, especially a work-related one.

I think sometimes a corporate IT admin or an ISP will block a whole range of IP addresses, not just the particular one hosting your site, so you could get blocked out because of some other site hosted by your ISP.

PS: the site seems to load up OK for me from Oakland, CA -- it was working yesterday as well.


Even if that's not the case getting a dedicated IP just makes good business sense.

She HAS a dedicated IP address -- that's how the DNS servers find her files when someone types in the name of the website.

But the person who has the trouble, their ISP may be blocking (for example) all IP addresses between 000.000.000.128 through 000.000.000.254 because several domains resolving to addresses within that range are objectionable. If her IP address happens to be 000.000.000.167 it could get blocked along with all the others.
06/01/2009 04:26:38 AM · #24
Originally posted by GeneralE:

Originally posted by yanko:

Originally posted by GeneralE:

Originally posted by leaf:

I wonder if it could be that I am sharing an IP address with some other site that the IP in some locations decided to block.

Try to find out if the user is behind a firewall, especially a work-related one.

I think sometimes a corporate IT admin or an ISP will block a whole range of IP addresses, not just the particular one hosting your site, so you could get blocked out because of some other site hosted by your ISP.

PS: the site seems to load up OK for me from Oakland, CA -- it was working yesterday as well.


Even if that's not the case getting a dedicated IP just makes good business sense.

She HAS a dedicated IP address -- that's how the DNS servers find her files when someone types in the name of the website.

But the person who has the trouble, their ISP may be blocking (for example) all IP addresses between 000.000.000.128 through 000.000.000.254 because several domains resolving to addresses within that range are objectionable. If her IP address happens to be 000.000.000.167 it could get blocked along with all the others.


No she doesn't appear to have a dedicated IP. It looks like she is sharing one. I looked up her IP address via IP check and when I try it in a browser (i.e. //69.65.98.2/) her website doesn't load. If she had a dedicated IP it should take me straight to her site just like when I typed in her domain name. She is on a shared hosting plan which is cheaper than a dedicated hosting plan but you don't get the unique IP address. It typically only costs around $1-$2 dollars a month to own your own IP. She should get it. It makes sense to do so. It's just too easy to get blacklisted by an ISP or penalized by a search engines when you share your IP with hundreds of other web sites. As a business why risk that?

Message edited by author 2009-06-01 04:27:47.
06/01/2009 04:37:03 AM · #25
It is true what Richard says but even when running from a dedicated server you can still share the same IP (albeit with your own sites) I run 20 odd sites from 5 IPs the only ones I allocate a unique IP for are those that are https (which then has to have a dedicated IP anyway). The main flaw in your plan though Richard is that most webhosts are allocated a range of IPs to use so even getting a dedicated one doesn't stop you from being blocked in the scenario that GeneralE gives.

ETA: Spelling :(

Message edited by author 2009-06-01 04:38:54.
Pages:  
Current Server Time: 10/31/2020 07:00:11 AM

Please log in or register to post to the forums.


Home - Challenges - Community - League - Photos - Cameras - Lenses - Learn - Prints! - Help - Terms of Use - Privacy - Top ^
DPChallenge, and website content and design, Copyright © 2001-2020 Challenging Technologies, LLC.
All digital photo copyrights belong to the photographers and may not be used without permission.
Proudly hosted by Sargasso Networks. Current Server Time: 10/31/2020 07:00:11 AM EDT.