• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 907
  • Last Modified:

Qwest DSL Blocking Website? Page Cannot Be Displayed

We just moved and had to get Qwest DSL.

I can reach all websites EXCEPT the ones hosted by my friend like: www.nata2.org
(My own personal website is hosted there and this is where I retrieve my e-mail so I would REALLY like to be able to connect to these sites!)

I receive the "This page cannot be displayed" error on any of his sites.  I've called qwest and they say it must be my friend.  I've called my friend and since I can get to his websites at work or even the library that it must be Qwest.  I'm going crazy!

Below is my tracert.  Any help would be greatly appreciated.  I'm not a network guru so if you need any specific PC info I'll need a description on how to retrieve it.  

Unfortunately my apartment has a contract through Qwest which limits my high-speed internet options.


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

C:\Documents and Settings\Janise>tracert www.nata2.org

Tracing route to www.nata2.org [199.218.1.3]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     4 ms     2 ms     2 ms  192.168.0.1
  3    50 ms    42 ms    44 ms  dnvr-dsl-gw05.dnvr.qwest.net [207.225.101.5]
  4    46 ms    42 ms    43 ms  dnvr-agw1.inet.qwest.net [207.225.101.125]
  5    47 ms    42 ms    42 ms  thn-core-02.inet.qwest.net [206.196.128.247]
  6    47 ms    42 ms    44 ms  dia-core-01.inet.qwest.net [205.171.208.13]
  7    63 ms    57 ms    57 ms  kcm-core-01.inet.qwest.net [205.171.8.138]
  8    63 ms    57 ms    57 ms  kcm-core-03.inet.qwest.net [205.171.29.122]
  9    76 ms    69 ms    71 ms  cer-core-02.inet.qwest.net [205.171.8.169]
 10    76 ms    98 ms    70 ms  cer-core-01.inet.qwest.net [205.171.139.1]
 11    72 ms    67 ms    67 ms  chi-core-02.inet.qwest.net [205.171.205.33]
 12    72 ms    65 ms    67 ms  chi-edge-20.inet.qwest.net [205.171.20.182]
 13    79 ms    72 ms    72 ms  208.44.132.22
 14    78 ms    72 ms    72 ms  cncnc-r0-ge7-0s381.core.oar.net [199.18.164.49]

 15    81 ms    75 ms    75 ms  clmbn-r0-po0-0.core.oar.net [199.18.145.34]
 16    80 ms    75 ms    76 ms  199.18.152.49
 17    81 ms    75 ms    75 ms  lap1-vlan10.columbus.oar.net [199.18.198.8]
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
0
Janise
Asked:
Janise
  • 12
  • 5
  • 4
  • +4
1 Solution
 
Asta CuCommented:
Checked for Virus/trojan/worm activity and unwanted items in the HOSTS file?  Maybe Spyware or some other rerouter interfering with you?  When you ping the link directly, also times out?
0
 
Asta CuCommented:
In your Browser, also try to add the link to your IE - Security tab and trusted zone as well as pasting into the Privacy tab to allow and then close IE and try again, perhaps.
0
 
JaniseAuthor Commented:
No Virus/trojan/worms/spyware... problem is on all 4 of our machines.  Including my work machine which is regularly scanned.  They all could access www.nata2.org before we started using DSL.  My work machine can access it at work.

When I ping www.nata2.org it also times out.  Correct.

I added the link to trusted zones and I still receive the Page Cannot Be Displayed error.

I could access these sites fine before we moved and started using Qwest.  =)
0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
Asta CuCommented:
This may be a silly question, but here goes....  Could it be that the Qwest number you're using is not close enough to you?  Perhaps they have other options for you that go through less loops?  Maybe some link in their network is down?  If you're sure the setup is correct; wonder if it could be a bandwidth problem such as too many concurrent users?  Really tough to say, given all you've tried.
0
 
Asta CuCommented:
Is your Qwest package one which includes MSN and if so, can you go to MSN directly?  Have you tried resetting the DSL router/modem to test?  Anything here that might be of help to you?
http://www.qwest.com/internet/
0
 
ridCommented:
I have problems reaching the site you mention as well. A "ping" gets resolved to the IP you gave above, but I get no reply. Browser cannot get anything. I know that my ISP is not filtering or blocking http traffic or ping. Can you query your friend about his connection - perhaps there's a problem at that end?
/RID
0
 
Asta CuCommented:
You beat me to it, rid, also timed out here.
0
 
JaniseAuthor Commented:
Our ISP is Qwest.net so we don't use MSN.  I've reset our DSL modem a few times to no avail.

I'm just not sure where the problem can lie... if I can access everything fine from work why am I not able to here at home?  Astaec/Rid are you both using Qwest or another ISP?  

My friend has sworn up and down that it isn't his server/service.  He's not blocking anything and no one else that uses his site has had a similar problem.  =(  

Argh!
=)
0
 
Asta CuCommented:
Sorry, don't use Qwest, did a lot of research and that's all I could find.  Checking with a friend who has used Qwest in the hopes they'll have some insight.
0
 
Asta CuCommented:
Silly question, but here goes... You've verified your login info and password on this system to ensure they're correct?  When you did the reset.... did you turn it off, unplug it and wait for at least 2-3 minutes?
0
 
ridCommented:
I'm in Sweden... haven't heard of Qwest before this... :)
/RID
0
 
HoweverCommaCommented:
His site is broken.
I use Bellsouth and it doesn't work.
I have an RDP connection to an AllTel site & It can not access the site nor can one with a T3 provider I have no idea.
It doesn't work for anyone here, me in 3 locations or you. It is dead.
0
 
JaniseAuthor Commented:
astaec - Silly questions are usually valid.  =)  My login is fine via qwest I can access other sites.  When I reset I unplugged it and came back 1/2 hour later or so.  Good thinking though!

rid - boy are you lucky you don't have Qwest.  =)  The setup was a nightmare... and now this issue.  Argh!  =)

HoweverComma - I am able to access this site from my local library and work... but I'll let him know you can't connect either.  Thanks!

0
 
Asta CuCommented:
ARGH is right!  Gads, this should be so simple!  Yet.... well; it's family day.  Will return tomorrow and hope the solutions will be there.  If not, we're all here to help you achieve what you deserve ....  "A" level results!  Sent this link to a friend who had Qwest, and hoped he'd have been here, but perhaps his family day as well, LOL.  Halloween and all that entails.
":0) Asta
0
 
Fatal_ExceptionCommented:
Ok.. just scanned this thread and I would suggest this as a possibility..

There are occasions when some sites get 'black-listed'.  This usually occurs when an email smtp server is using an open relay.  Once a site gets black listed, it is very hard to get the site taken off the list.  If this is the case, it is your ISP that has blocked the site, and that is where you should start.  Your first attempt at speaking with them (Qwest) brought a negative and usual response of "It is not our fault"..  this is so typical with these Service Providers..  I suspect the it is their fault, or the actual provider that they are leasing their lines from...

FE
0
 
Fatal_ExceptionCommented:
BTW:  just so you understand why these are black listed (and since I have a few minutes)..  Spammers use open relays to disguise their spam..   When found that an email server is considered 'open', it is put on one of these lists...  For example, here is a link to one of the many lists that cirulate among Providers:

http://www.email-policy.com/Spam-black-lists.htm

Now, sometimes an ISP will determine on its own that an email provider should be blacklisted from their routers...  This happened to one of my clients last year.  Took several calls to Time Warner Roadrunner to get the route opened, and after pulling hairs for a week, we finally were able to access the client's remote mail server...  a real pain, but a learning experience..  

So, first get with your friend and make sure he is not running an open relay.  Then, regardless, I would point the problem back at Qwest, and ask them to trace down the solution.  The unfortunate part is that they have a virtual monopoly in your case, and may just shelve it since they really have no motivation to solve it....

FE
0
 
Eric AKA NetminderCommented:
Janise,

It's definitely NOT a QWest issue; I'm using Comcast and can't get to it either. I ran a traceroute on it, and it appears as though it's being blocked by either QWest in Chicago, OR oar.net in Columbus, Ohio, and more likely the latter, based on the response times.

Sorry about the formatting...

Hop      IP                 Hostname                                          last [ms]      min [ms]      max [ms]      ava. [ms]      var. [ms]      total Loss      
1      10.250.40.1      10.250.40.1                                          12                 7                  465                         31                    85            
2      67.181.0.117      c-67-181-1-117.we.client2.attbi.com      9               8               294                      28                 64
3      67.181.0.1      c-67-181-1-1.we.client2.attbi.com         41                 8                 277                        32                    64               1
4      67.181.0.22      c-67-181-1-22.we.client2.attbi.com      12               8               424                        38                  80
5      12.127.32.53      12.127.32.53                                        13               10               397                        28                  66            
6      12.123.13.177      tbr2-p013701.sffca.ip.att.net                  14                 11                 313                        34                    67
7      12.123.13.194      ggr2-p390.sffca.ip.att.net                   12                   10              309               30                     62
8      192.205.32.82      att-gw.sfo.qwest.net                            13             12            276                  30                   59
9      205.171.214.137      svx-core-02.inet.qwest.net               12               12               318                  25                  52
10      205.171.14.81      svl-core-03.inet.qwest.net               17               12               318                        33                  66
11      205.171.8.194      chi-core-01.inet.qwest.net               62               56               365                        76                  64
12      205.171.20.186      chi-edge-20.inet.qwest.net               63               41              483                      76               69
13      208.44.132.22      208.44.132.22                                    98            78            388                  96                     54
14      199.18.164.49      cncnc-r0-ge7-0s381.core.oar.net            87            78           283                 92                   44
15      199.18.145.34      clmbn-r0-po0-0.core.oar.net               79               77            324                    91               47
16      199.18.152.49      199.18.152.49                                    83            78           535                  99                     65
17      199.18.198.8      lap1-vlan10.columbus.oar.net               82               78            544                   105             88
18      *      *                              
0
 
Asta CuCommented:
Thank you, ericpete, with the same interface as Asker think this is so important.  Asta
0
 
Fatal_ExceptionCommented:
As mentioned in my earlier comment, I am suggesting that this has been blacklisted.  You should contact either Qwest or the Oar.net organization to have them troubleshoot this...

http://www.oar.net/
0
 
JaniseAuthor Commented:
I talked to my friend and qwest - it seems they recently added some new IPs in the Denver area and for some reason my friend's servers were not picking them up.  He fixed this and now everyone should be able to access the sites.  Thanks so much for everyone looking into this.  
0
 
Asta CuCommented:
YIPEE!!  Happy to hear that the mystery is solved.  You can close this in any way you like; including splitting points between participants.  Check the link below on the Question and Answer Tips for guidance, if needed.  Feel free to exclude me.
Asta
0
 
Asta CuCommented:
Can you tell us what else we can do or have we served your needs here?
0
 
Eric AKA NetminderCommented:
Janise,

http://www.experts-exchange.com/help.jsp#hs5

And I can pretty much guarantee that none of the Experts involved here care.

As an aside, you should know that it can take two or three days for a new set of IP addresses to be propogated through the WWW -- the various servers involved don't update RIGHT NOW, so that could be why the name wouldn't resolve.

ep
0
 
Fatal_ExceptionCommented:
Yea, from what I can see of the experts involved here, none of really care about points, so that is a non-issue...  And that is correct, these addresses do need to propagate through the appropriate DNS servers for name resolution, but I wonder about those additional IP addresses...  It must have to do with DNS, and not the addresses alone..
0
 
Eric AKA NetminderCommented:
F_E,

It's a two-way street. If the domain names don't get updated, then logically, neither would the IPs.

ep
0
 
Fatal_ExceptionCommented:
Yea, that was what I was implying in my statement.. guess I did not state it very well, eh?  :)
0
 
GhostModCommented:
PAQd, 500 points refunded.

GhostMod
Community Support Moderator
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 12
  • 5
  • 4
  • +4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now