My website won't display on PC but will on Mac

H

haildented

Posts: 6   +0
My website, www dot castbulletsdirect dot com will not display on my PC using any browser but works fine on my Mac. A couple friends checked their PC's and site displayed with no problems. I tried my laptop on another wireless network and site does not display. I believe google displays "Oops, this link appears to be broken and IE8 displays "Internet explorer cannot display the website". The connectivity check shows no issues.
I have followed all the suggestions Microsoft had to isolate the problem. I have reset and cleared everything suggested by anyone. This has included disabling AVG and the windows firewall to test them, starting IE8 with no add ons, ect.
I have pinged (www dot castbulletsdirect dot com) the site from the mac (reslut: shops.shopify.com (204.93.213.44)) and pc ((208.79.238.51) and got different IP address and no results from the pings. I have uninstalled all the other browsers, Chrome and Firefox, from the PC and reinstalled IE8 with no luck. I reinstalled Chrome, no luck. I have reset the router, no luck.
This site was just redone and moved to a different server. The developer uses MAC's and has no problems accessing the site. The only problem appears to be with my PC which is an HP laptop.
 
Loads fine for me on a PC using both Chrome and Firefox 5.0. Try running an ipconfig /flushdns on the machines that can't reach it.
 
As above.. :)

Works here on Debian 6 (Chrome/Iceweasel) and in IE, FF and Chrome in Windows 7.

EDIT:

In Windows 7...

Code: 
C:\Users\Leeky>ping castbulletsdirect.com

Pinging castbulletsdirect.com [64.202.189.170] with 32 byte
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 64.202.189.170:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Leeky>ping www.castbulletsdirect.com

Pinging shops.shopify.com [204.93.213.43] with 32 bytes of
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 204.93.213.43:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Something isn't right there...you got this running on two different servers or something?

Have you correctly setup the nameservers to the correct IP addresses, and allowed them to fully resolve before having these issues?

tracert results

Code: 
C:\Users\Leeky>tracert castbulletsdirect.com

Tracing route to castbulletsdirect.com [64.202.189.170]
over a maximum of 30 hops:

  1     7 ms     7 ms     7 ms  10.167.160.1
  2     8 ms     9 ms     9 ms  pete-core-1b-ae1-2543.network.virginmedia.net [8
0.3.129.157]
  3    12 ms    13 ms    36 ms  popl-bb-1b-as6-0.network.virginmedia.net [212.43
.163.221]
  4    22 ms    15 ms    15 ms  popl-bb-1a-ae0-0.network.virginmedia.net [213.10
5.174.229]
  5    15 ms    15 ms    20 ms  195.50.91.69
  6    16 ms    18 ms    17 ms  ae-34-52.ebr2.London1.Level3.net [4.69.139.97]
  7   161 ms   103 ms   111 ms  ae-43-43.ebr1.NewYork1.Level3.net [4.69.137.74]

  8   106 ms   126 ms   108 ms  ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]

  9   123 ms   105 ms   103 ms  ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33]

 10   120 ms   123 ms   120 ms  ae-3-3.ebr2.Dallas1.Level3.net [4.69.137.121]
 11   122 ms   151 ms   137 ms  ae-72-72.csw2.Dallas1.Level3.net [4.69.151.141]

 12   120 ms   120 ms   120 ms  ae-71-71.ebr1.Dallas1.Level3.net [4.69.151.138]

 13   150 ms   183 ms   160 ms  ae-1-8.bar1.Phoenix1.Level3.net [4.69.133.29]
 14   152 ms   151 ms   151 ms  ae-5-5.car1.Phoenix1.Level3.net [4.69.148.117]
 15   142 ms   143 ms   161 ms  THE-GO-DADD.car1.Phoenix1.Level3.net [4.53.104.2
]
 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.

C:\Users\Leeky>tracert www.castbulletsdirect.com

Tracing route to shops.shopify.com [204.93.213.42]
over a maximum of 30 hops:

  1     7 ms     8 ms     6 ms  10.167.160.1
  2     7 ms     9 ms     7 ms  pete-core-1b-ae1-2543.network.virginmedia.net [8
0.3.129.157]
  3    11 ms    31 ms    23 ms  popl-bb-1b-as6-0.network.virginmedia.net [212.43
.163.221]
  4    34 ms    13 ms    13 ms  popl-tmr-2-ae5-0.network.virginmedia.net [213.10
5.159.6]
  5    15 ms    11 ms    17 ms  tele-ic-2-as0-0.network.virginmedia.net [62.253.
184.6]
  6    91 ms    92 ms   133 ms  eqix.xe-3-3-0.cr2.iad1.us.nlayer.net [206.223.11
5.61]
  7    91 ms    91 ms    93 ms  ae1-30g.cr1.iad1.us.nlayer.net [69.31.31.153]
  8   125 ms   117 ms   113 ms  xe-4-1-0.cr2.ord1.us.nlayer.net [69.22.142.32]
  9   116 ms   123 ms   115 ms  po6.ar2.ord1.us.scnet.net [69.31.111.6]
 10   115 ms   115 ms   117 ms  62.po2.ar2.ord6.us.scnet.net [75.102.3.230]
 11   130 ms   116 ms   132 ms  82.vlan.ar6.ord6.us.scnet.net [204.93.192.210]
 12   114 ms   115 ms   142 ms  unknown.scnet.net [204.93.213.42]
 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.

I would hazard a guess that your issue is bad namesever setup, or lack of it being fully populated.

Below are the results of mine, which are correctly setup:

Code: 
C:\Users\Leeky>tracert www.leekaelin.co.uk

Tracing route to leekaelin.co.uk [174.123.4.253]
over a maximum of 30 hops:

  1     7 ms     7 ms     5 ms  10.167.160.1
  2     8 ms     5 ms     8 ms  pete-core-1a-ae1-2544.network.virginmedia.net [8
0.3.129.37]
  3    10 ms     9 ms     9 ms  nrth-bb-1a-as6-0.network.virginmedia.net [212.43
.163.217]
  4    14 ms    13 ms    13 ms  manc-bb-1b-as4-0.network.virginmedia.net [213.10
5.64.22]
  5    20 ms    21 ms    60 ms  tele-ic-3-ae0-0.network.virginmedia.net [212.43.
163.70]
  6   106 ms   107 ms   105 ms  45-236-228-213.packetexchange.net [213.228.236.4
5]
  7   109 ms   107 ms   106 ms  be-10-cr01.ashburn.va.ibone.comcast.net [68.86.8
4.201]
  8   129 ms   133 ms   122 ms  pos-1-6-0-0-cr01.atlanta.ga.ibone.comcast.net [6
8.86.87.82]
  9   146 ms   141 ms   174 ms  pos-1-12-0-0-cr01.dallas.tx.ibone.comcast.net [6
8.86.85.157]
 10   165 ms   147 ms   147 ms  pos-0-0-0-0-pe01.1950stemmons.tx.ibone.comcast.n
et [68.86.86.90]
 11   134 ms   135 ms   133 ms  theplanet-cr01.dallas.tx.ibone.comcast.net [75.1
49.228.2]
 12   129 ms   129 ms   129 ms  te9-1.dsr01.dllstx3.networklayer.com [70.87.253.
6]
 13   139 ms   139 ms   141 ms  te9-5.dsr01.hstntx2.networklayer.com [70.87.253.
50]
 14   142 ms   143 ms   154 ms  p01.car06.hstntx2.networklayer.com [74.55.252.82
]
 15   142 ms   143 ms   148 ms  42.e1.7aae.static.theplanet.com [174.122.225.66]

 16   142 ms   179 ms   141 ms  fd.4.7bae.static.theplanet.com [174.123.4.253]

Trace complete.

C:\Users\Leeky>tracert leekaelin.co.uk

Tracing route to leekaelin.co.uk [174.123.4.253]
over a maximum of 30 hops:

  1     7 ms     5 ms     7 ms  10.167.160.1
  2     6 ms    29 ms     7 ms  pete-core-1a-ae1-2544.network.virginmedia.net [8
0.3.129.37]
  3     9 ms     9 ms     9 ms  nrth-bb-1a-as6-0.network.virginmedia.net [212.43
.163.217]
  4    14 ms    14 ms    15 ms  manc-bb-1b-as4-0.network.virginmedia.net [213.10
5.64.22]
  5    45 ms    20 ms    23 ms  tele-ic-3-ae0-0.network.virginmedia.net [212.43.
163.70]
  6   106 ms   105 ms   105 ms  45-236-228-213.packetexchange.net [213.228.236.4
5]
  7   110 ms   107 ms   107 ms  be-10-cr01.ashburn.va.ibone.comcast.net [68.86.8
4.201]
  8   119 ms   119 ms   143 ms  pos-1-6-0-0-cr01.atlanta.ga.ibone.comcast.net [6
8.86.87.82]
  9   141 ms   143 ms   167 ms  pos-1-12-0-0-cr01.dallas.tx.ibone.comcast.net [6
8.86.85.157]
 10   143 ms   143 ms   143 ms  pos-0-0-0-0-pe01.1950stemmons.tx.ibone.comcast.n
et [68.86.86.90]
 11   134 ms   133 ms   137 ms  theplanet-cr01.dallas.tx.ibone.comcast.net [75.1
49.228.2]
 12   128 ms   129 ms   129 ms  te9-1.dsr01.dllstx3.networklayer.com [70.87.253.
6]
 13   140 ms   140 ms   140 ms  te9-5.dsr01.hstntx2.networklayer.com [70.87.253.
50]
 14   157 ms   148 ms   167 ms  p01.car06.hstntx2.networklayer.com [74.55.252.82
]
 15   142 ms   143 ms   143 ms  42.e1.7aae.static.theplanet.com [174.122.225.66]

 16   142 ms   141 ms   142 ms  fd.4.7bae.static.theplanet.com [174.123.4.253]

Trace complete.

C:\Users\Leeky>ping www.leekaelin.co.uk

Pinging leekaelin.co.uk [174.123.4.253] with 32 bytes of data:
Reply from 174.123.4.253: bytes=32 time=142ms TTL=53
Reply from 174.123.4.253: bytes=32 time=141ms TTL=53
Reply from 174.123.4.253: bytes=32 time=142ms TTL=53
Reply from 174.123.4.253: bytes=32 time=141ms TTL=53

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

C:\Users\Leeky>ping leekaelin.co.uk

Pinging leekaelin.co.uk [174.123.4.253] with 32 bytes of data:
Reply from 174.123.4.253: bytes=32 time=143ms TTL=53
Reply from 174.123.4.253: bytes=32 time=142ms TTL=53
Reply from 174.123.4.253: bytes=32 time=143ms TTL=53
Reply from 174.123.4.253: bytes=32 time=142ms TTL=53

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

See how regardless of whether I use www. or not at the start of the domain name, they resolve to exactly the same place and IP everytime?

You either have your domain running between two servers, or you have moved your website to a new provider and the new nameservers have not fully populated yet, or you have badly setup nameservers.

Or something else along them lines. I'm not pro, but that just doesn't look right the way its resolving.

So has the site been recently moved?
 
So has the site been recently moved?
Click to expand...
From what Ive read, it looks like he did say the site changed servers.
This site was just redone and moved to a different server.
Click to expand...
So i think your right Leeky, that is probably what is causing his problems.
 
Leeky said:
See how regardless of whether I use www. or not at the start of the domain name, they resolve to exactly the same place and IP everytime?
Click to expand...
Spot on buddy.

www dot castbulletsdirect dot com must work correctly while

having castbulletsdirect dot com work (ie reach the same site) is a courtsey.

Browser design implements this logic
  1. access the user's given URL,
  2. IF the dns reply is not found AND the prefix is not WWW,
    THEN insert the WWW and try again
 
Thanks for all your help!

Yes the site was moved to different servers, I went from a site using Word Press and a Zen shopping cart to a Shopify site. The only thing that carried over was text and images.
I will pass this information on to the guys that made the changes and see if they can find the issue.
Again thanks for all the suggestions and help! I will keep you posted on what is discovered.
 
Appears problem is in my PC somewhere

No other computer has an issue with accessing the website so it appears my laptop is the problem. I have done the ipconfig /flushdns many times but it does not clear up the issue. I am running Windows XP Professional, Version 2002, Service Pack 3. I have used Firefox, Google Chrome and IE 8 as browsers. Any ideas short of reloading Windows?
 
I think this is my problem how do I fix it?

I did an ipconfig /flushdns and then an ipconfig /displaydns. My website URL shows up in the list. How do I get it deleted from there?

wwwcastbulletsdirectcom ----------------------------------------
Record Name . . . . . : wwwcastbulletsdirectcom
Record Type . . . . . : 1
Time To Live . . . . : 603035
Data Length . . . . . : 4
Section . . . . . . . : Answer
A (Host) Record . . . : 208.79.238.5
 
use admin login
  1. ipconfig /flushdns
  2. net stop "dns client"
now use your browser to access the site. if you can get there properly, then the ipconfig /displaydns IS the issue.

(stopping the DNS Client service, forces your system to access the external DNS
via your TCP settings.
You can leave it stopped or restart it using net start "dns client"
)

I'm fishing for a means to clear the /displaydns results . . .
 
Fixed!

ipconfig /flushdns will not fix this. The issue is caused by a entry in C:\WINDOWS\system32\drivers\etc HOST. Open it with notepad and delete the line of code with the url and IP address and the problem in my case went away.
 
haildented said:
ipconfig /flushdns will not fix this. The issue is caused by a entry in C:\WINDOWS\system32\drivers\etc HOST. Open it with notepad and delete the line of code with the url and IP address and the problem in my case went away.
Click to expand...
yea, that would do it !
 
btw: ipconfig /displaydns shows results of the domain names in the HOSTS file;
to trim the output, edit the inputs :)
 
I don't know how it got there

LNCPapa, I don't understand how it got there. I didn't put it there! Until a few days ago I didn't know to look for it there. It has been a learning experience for me and a frustrating one at that. Hindsight being 20/20 I would have done the displaydns command before and after the flush command to know for sure what I accomplished or failed to accomplish. That was my fault for not using better troubleshooting skills as the information about the ipconfig / was right in front of me and just required reading!
 
You must log in or register to reply here.

Similar threads

Cal Jeffrey
QDEL technology set to become the premium display replacement to OLEDs by 2026
Replies
20
Views
125
FaTaL
FaTaL
T
Firefox logging issue
2
Replies
34
Views
2K
Julio Franco
Julio Franco
AlexGrama7
Unable to Connect External Monitor via USB-C on Lenovo Legion 5 (15ARH05H)
Replies
3
Views
947
AlexGrama7
AlexGrama7

Latest posts

Back