Can't access anything linking to bitgravity.com

  • Thread starter Thread starter Charles May
  • Start date Start date
C

Charles May

I apologize in advance for the length of this post but I want to give as
much detail as possible.

Recently when I go to revision3's site on a particular pc, I cannot access
any of the videos as they are hosted on bitgravity.com . The videos are
linked to bitcase-a.bitgravity.com and always fail.

Here is what I have tried.
A second PC on the same network works fine so I used it to test certain
situations

I am primarily using FireFox 2.0.0.11 but have tried this with IE7 and Opera
I have cleared all cache both manually and using CCleaner along with
cleaning the registry up with CCleaner.
I have disabled any protection in SpywareBlaster and then un-installed it
I have disabled any protection in Spybot S&D and then un-installed it
I have shut down my firewall and made sure none of its process were still
running (Kerio)
I ran a full ALL FILES virus scan using AVG - Nothing Found
I ran RootKit Revealer - Nothing Found
I shut down all programs in Startup through MSConfig
I went in and started killing processes to see if something running was
causing it but to no avail.
I even booted to safe mode with networking support and had the same problem.

Of course, when I booted with a Ubuntu LiveCD on that pc I was able to
access them So that tells me I have something that is blocking access to
that site.

Even though I'm using Firefox, I opened Internet Options and checked the
list of sites that are blocked in IE7 found nothing even close to
bitgravity.

On the other PC everything works fine so...
For the rest of this PC1 will refer to the troublesome pc and PC2 will be
the one that works. These two PCs are side by side and use the same router.

On PC1 I did a ping to bitcast-a.bitgravity.com which timed out
I pinged with PC2 and resulted in 24ms access times
On PC2 I did a tracert to bitcast-a.bitgravity.com which resulted in 8 hops
with the max being 25 ms this tracert took < 10 seconds
So I decided to try tracert on PC1 which timed out.

Now... Looking at the tracert results on PC2 I decided to try to tracert to
the actual IP address on PC1
This resulted in displaying 8 hops much like it did on PC2 and pretty much
the same times except that it took almost 2 minutes to complete.

I have checked my hosts file, along with comparing all the other files in
the etc folder with the ones on PC2 and find no differences.

I guess my question is, what else can I look for? What else can cause this
to happen?

I'm pulling my hair out.

By the way, I cannot even visit www.bitgravity.com it times out.
 
I apologize in advance for the length of this post but I want to give as
much detail as possible.

Recently when I go to revision3's site on a particular pc, I cannot access
any of the videos as they are hosted on bitgravity.com . The videos are
linked to bitcase-a.bitgravity.com and always fail.

Here is what I have tried.
A second PC on the same network works fine so I used it to test certain
situations

I am primarily using FireFox 2.0.0.11 but have tried this with IE7 and Opera
I have cleared all cache both manually and using CCleaner along with
cleaning the registry up with CCleaner.
I have disabled any protection in SpywareBlaster and then un-installed it
I have disabled any protection in Spybot S&D and then un-installed it
I have shut down my firewall and made sure none of its process were still
running (Kerio)
I ran a full ALL FILES virus scan using AVG - Nothing Found
I ran RootKit Revealer - Nothing Found
I shut down all programs in Startup through MSConfig
I went in and started killing processes to see if something running was
causing it but to no avail.
I even booted to safe mode with networking support and had the same problem.

Of course, when I booted with a Ubuntu LiveCD on that pc I was able to
access them So that tells me I have something that is blocking access to
that site.

Even though I'm using Firefox, I opened Internet Options and checked the
list of sites that are blocked in IE7 found nothing even close to
bitgravity.

On the other PC everything works fine so...
For the rest of this PC1 will refer to the troublesome pc and PC2 will be
the one that works. These two PCs are side by side and use the same router.

On PC1 I did a ping to bitcast-a.bitgravity.com which timed out
I pinged with PC2 and resulted in 24ms access times
On PC2 I did a tracert to bitcast-a.bitgravity.com which resulted in 8 hops
with the max being 25 ms this tracert took < 10 seconds
So I decided to try tracert on PC1 which timed out.

Now... Looking at the tracert results on PC2 I decided to try to tracert to
the actual IP address on PC1
This resulted in displaying 8 hops much like it did on PC2 and pretty much
the same times except that it took almost 2 minutes to complete.

I have checked my hosts file, along with comparing all the other files in
the etc folder with the ones on PC2 and find no differences.

I guess my question is, what else can I look for? What else can cause this
to happen?

I'm pulling my hair out.

By the way, I cannot even visit www.bitgravity.com it times out.

Charles,

Your symptoms, however lightly analysed, bear resemblance to an MTU problem.
Check your max MTU setting.
<http://nitecruzr.blogspot.com/2007/06/determining-mtu-to-single-server.html>
http://nitecruzr.blogspot.com/2007/06/determining-mtu-to-single-server.html

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
 
Hi there,

We would be more than happy to help out, it sounds like you are having
some network problems.

We serve video to millions of people per-hour and this is the first
message I have seen like this in the existence of our service. :)

Just email (e-mail address removed) and we'll get you fixed up.

-Barrett

BitGravity, CTO
 
Barrett,
Thanks, I was actually going to email support but then realized this was on
my end since I could ping your IP address successfully.

Anyway, the problem ended up being a wrong primary dns in my network
settings. I guess I overlooked it since it appeared your site was the only
thing not working for me (that I had come across).

Thanks for your offer,

Charlie
 
Back
Top