Cyclops14
asked on
Cannot access specific website
I am not able to access a specific website. The website is not accessible from home, however, the website IS accessible from ANY other place that I try to access it from (with the same computer), so I know the website is up. This happened about a week ago, I was browsing the website in question at home and all of a sudden: "Internet Explorer cannot display the webpage". None of my computers at home can access the website, but I can take any of these computers to another place and access the website with no problems.
I have tried flushing the DNS, renewing IP, restarting the cable modem and the wireless router.
Ome more thing, if I connect at home to my job's VPN client, I can connect to the website with no problems. That's how I've been getting aroung this issue for the last week at home.
I have tried flushing the DNS, renewing IP, restarting the cable modem and the wireless router.
Ome more thing, if I connect at home to my job's VPN client, I can connect to the website with no problems. That's how I've been getting aroung this issue for the last week at home.
Set your dns to a static ip try any dns server other than your Home ISP.
Sorry here's a list if you need it
http://www.dnsserverlist.org/
http://www.dnsserverlist.org/
ASKER
ecszone:
Ping is not succesfull.
There is no SSL version of the page.
IPS said they are not blocking it.
Ping is not succesfull.
There is no SSL version of the page.
IPS said they are not blocking it.
ASKER
Dawilliams:
I changed the DNS servers to statics using a couple that I found in the website you provided. It still doesn't work. See below for a trace route using my ISP's DNS servers, the static DNS servers from your website, and when connected to my VPN client.
ISP's DNS:
Tracing route to www.marketplace6.com [69.94.7.211]
over a maximum of 30 hops:
1 2 ms 4 ms 2 ms 192.168.1.1
2 * * * Request timed out.
3 31 ms 12 ms 10 ms ge-1-13-ur01.sweetwater.fl
4 54 ms 9 ms 12 ms po-1-ur01.hialeahne.fl.pom
5 20 ms 11 ms 14 ms po-1-ur01.hialeahse.fl.pom
6 20 ms 15 ms 69 ms po-1-ur01.hialeahwest.fl.p
7 56 ms 13 ms 12 ms te-9-4-ur01.hialeahwest.fl
8 14 ms 14 ms 12 ms te-0-0-0-4-cr01.miami.fl.i
9 19 ms 17 ms 13 ms xe-10-0-0.edge2.Miami1.Lev
10 13 ms 14 ms 17 ms ae-32-52.ebr2.Miami1.Level
11 39 ms 36 ms 36 ms ae-2.ebr2.Atlanta2.Level3.
12 32 ms 37 ms 32 ms ae-63-60.ebr3.Atlanta2.Lev
13 42 ms 51 ms 52 ms ae-2.ebr1.Washington1.Leve
14 42 ms 49 ms 40 ms ae-61-61.csw1.Washington1.
15 50 ms 51 ms 54 ms ae-64-64.ebr4.Washington1.
16 48 ms 53 ms 43 ms ae-3-3.ebr1.NewYork1.Level
17 47 ms 51 ms 59 ms ae-61-61.csw1.NewYork1.Lev
18 48 ms 47 ms 47 ms ge-2-0.core1.NewYork1.Leve
19 49 ms 49 ms 51 ms so-0-2-0.onlinemllc4.bbnpl
20 51 ms 56 ms 47 ms 69.94.1.69
21 * * * Request timed out.
22 * * * Request timed out.
Static DNS servers:
Tracing route to www.marketplace6.com [69.94.7.211]
over a maximum of 30 hops:
1 2 ms * 13 ms 192.168.1.1
2 * * * Request timed out.
3 12 ms 7 ms 13 ms ge-1-13-ur01.sweetwater.fl
4 9 ms * 12 ms po-1-ur01.hialeahne.fl.pom
5 11 ms 8 ms 10 ms po-1-ur01.hialeahse.fl.pom
6 11 ms 17 ms 8 ms po-1-ur01.hialeahwest.fl.p
7 14 ms 12 ms 10 ms te-9-4-ur01.hialeahwest.fl
8 13 ms 10 ms 14 ms te-0-0-0-4-cr01.miami.fl.i
9 12 ms 11 ms 16 ms xe-10-0-0.edge2.Miami1.Lev
10 34 ms 11 ms 21 ms ae-32-52.ebr2.Miami1.Level
11 26 ms 35 ms 40 ms ae-2.ebr2.Atlanta2.Level3.
12 39 ms 34 ms 36 ms ae-63-60.ebr3.Atlanta2.Lev
13 41 ms 76 ms 50 ms ae-2.ebr1.Washington1.Leve
14 44 ms 39 ms 49 ms ae-61-61.csw1.Washington1.
15 42 ms 42 ms 57 ms ae-64-64.ebr4.Washington1.
16 86 ms 49 ms 43 ms ae-3-3.ebr1.NewYork1.Level
17 81 ms 52 ms 156 ms ae-61-61.csw1.NewYork1.Lev
18 74 ms 44 ms 44 ms ge-2-0.core1.NewYork1.Leve
19 47 ms 46 ms 47 ms so-0-2-0.onlinemllc4.bbnpl
20 52 ms 49 ms 52 ms 69.94.1.69
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
VPN Client:
Tracing route to www.marketplace6.com [69.94.7.211]
over a maximum of 30 hops:
1 60 ms 53 ms 78 ms 0.150.84.12
2 70 ms 59 ms 65 ms 57.250.242.254
3 93 ms 67 ms 79 ms 57.68.27.46
4 155 ms 153 ms 153 ms 57.68.0.98
5 * 61 ms 72 ms 57.68.0.110
6 63 ms 78 ms 68 ms 193.251.255.21
7 84 ms 78 ms 193 ms ge-7-6.car2.Atlanta1.Level
8 114 ms 152 ms 153 ms ae-2-52.bbr2.Atlanta1.Leve
9 131 ms 146 ms 246 ms ae-0-0.bbr2.NewYork1.Level
10 378 ms 307 ms 307 ms vlan69.csw1.NewYork1.Level
11 87 ms 182 ms 102 ms ge-2-0.core1.NewYork1.Leve
12 220 ms 250 ms 261 ms so-0-2-0.onlinemllc4.bbnpl
13 134 ms 153 ms 153 ms 69.94.1.69
14 280 ms 256 ms 255 ms 69.94.7.211
Trace complete.
I changed the DNS servers to statics using a couple that I found in the website you provided. It still doesn't work. See below for a trace route using my ISP's DNS servers, the static DNS servers from your website, and when connected to my VPN client.
ISP's DNS:
Tracing route to www.marketplace6.com [69.94.7.211]
over a maximum of 30 hops:
1 2 ms 4 ms 2 ms 192.168.1.1
2 * * * Request timed out.
3 31 ms 12 ms 10 ms ge-1-13-ur01.sweetwater.fl
4 54 ms 9 ms 12 ms po-1-ur01.hialeahne.fl.pom
5 20 ms 11 ms 14 ms po-1-ur01.hialeahse.fl.pom
6 20 ms 15 ms 69 ms po-1-ur01.hialeahwest.fl.p
7 56 ms 13 ms 12 ms te-9-4-ur01.hialeahwest.fl
8 14 ms 14 ms 12 ms te-0-0-0-4-cr01.miami.fl.i
9 19 ms 17 ms 13 ms xe-10-0-0.edge2.Miami1.Lev
10 13 ms 14 ms 17 ms ae-32-52.ebr2.Miami1.Level
11 39 ms 36 ms 36 ms ae-2.ebr2.Atlanta2.Level3.
12 32 ms 37 ms 32 ms ae-63-60.ebr3.Atlanta2.Lev
13 42 ms 51 ms 52 ms ae-2.ebr1.Washington1.Leve
14 42 ms 49 ms 40 ms ae-61-61.csw1.Washington1.
15 50 ms 51 ms 54 ms ae-64-64.ebr4.Washington1.
16 48 ms 53 ms 43 ms ae-3-3.ebr1.NewYork1.Level
17 47 ms 51 ms 59 ms ae-61-61.csw1.NewYork1.Lev
18 48 ms 47 ms 47 ms ge-2-0.core1.NewYork1.Leve
19 49 ms 49 ms 51 ms so-0-2-0.onlinemllc4.bbnpl
20 51 ms 56 ms 47 ms 69.94.1.69
21 * * * Request timed out.
22 * * * Request timed out.
Static DNS servers:
Tracing route to www.marketplace6.com [69.94.7.211]
over a maximum of 30 hops:
1 2 ms * 13 ms 192.168.1.1
2 * * * Request timed out.
3 12 ms 7 ms 13 ms ge-1-13-ur01.sweetwater.fl
4 9 ms * 12 ms po-1-ur01.hialeahne.fl.pom
5 11 ms 8 ms 10 ms po-1-ur01.hialeahse.fl.pom
6 11 ms 17 ms 8 ms po-1-ur01.hialeahwest.fl.p
7 14 ms 12 ms 10 ms te-9-4-ur01.hialeahwest.fl
8 13 ms 10 ms 14 ms te-0-0-0-4-cr01.miami.fl.i
9 12 ms 11 ms 16 ms xe-10-0-0.edge2.Miami1.Lev
10 34 ms 11 ms 21 ms ae-32-52.ebr2.Miami1.Level
11 26 ms 35 ms 40 ms ae-2.ebr2.Atlanta2.Level3.
12 39 ms 34 ms 36 ms ae-63-60.ebr3.Atlanta2.Lev
13 41 ms 76 ms 50 ms ae-2.ebr1.Washington1.Leve
14 44 ms 39 ms 49 ms ae-61-61.csw1.Washington1.
15 42 ms 42 ms 57 ms ae-64-64.ebr4.Washington1.
16 86 ms 49 ms 43 ms ae-3-3.ebr1.NewYork1.Level
17 81 ms 52 ms 156 ms ae-61-61.csw1.NewYork1.Lev
18 74 ms 44 ms 44 ms ge-2-0.core1.NewYork1.Leve
19 47 ms 46 ms 47 ms so-0-2-0.onlinemllc4.bbnpl
20 52 ms 49 ms 52 ms 69.94.1.69
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
VPN Client:
Tracing route to www.marketplace6.com [69.94.7.211]
over a maximum of 30 hops:
1 60 ms 53 ms 78 ms 0.150.84.12
2 70 ms 59 ms 65 ms 57.250.242.254
3 93 ms 67 ms 79 ms 57.68.27.46
4 155 ms 153 ms 153 ms 57.68.0.98
5 * 61 ms 72 ms 57.68.0.110
6 63 ms 78 ms 68 ms 193.251.255.21
7 84 ms 78 ms 193 ms ge-7-6.car2.Atlanta1.Level
8 114 ms 152 ms 153 ms ae-2-52.bbr2.Atlanta1.Leve
9 131 ms 146 ms 246 ms ae-0-0.bbr2.NewYork1.Level
10 378 ms 307 ms 307 ms vlan69.csw1.NewYork1.Level
11 87 ms 182 ms 102 ms ge-2-0.core1.NewYork1.Leve
12 220 ms 250 ms 261 ms so-0-2-0.onlinemllc4.bbnpl
13 134 ms 153 ms 153 ms 69.94.1.69
14 280 ms 256 ms 255 ms 69.94.7.211
Trace complete.
It's not a dns issue as this machine is resolving the name to ip, interesting that the site is acutally http://gm.marketplace6.com but the tracert dose'n show that like when you tracert google it comes back
www.l.google.com, Also it looks like your tracert is stopping at there front door based on the ip's. Not sure what to say at this point,
www.l.google.com, Also it looks like your tracert is stopping at there front door based on the ip's. Not sure what to say at this point,
ASKER
Thanks for trying to help.
If someone has any ideas, let me know please...
If someone has any ideas, let me know please...
THis is a stretch. Maybe the site is setup wierd... not doing proper port forwarding.. or somethign?
when it works you on a different subnet. From your subnet it does not. 192.168.1.1
is the most common subnet. I always avoid this subnet.
2 things to test this.
-hook directly to your cablemodem. This usually requires powering off the modem for 30 seconds, then back on (otherwise it wont see a new mac address and you wont get an IP) Once you have a public IP test again.
-or change your subnet. remember to change the dhcp first so that you dont lose connectivityh first. then change the private ip subnet from 192.168.1.x to 192.168.xxx.x
use something uncommon like 67 or whatever.
I have had some applications that choke if the remote private network is the same IP subnet as the local subnet. Hence the more unique the better.
when it works you on a different subnet. From your subnet it does not. 192.168.1.1
is the most common subnet. I always avoid this subnet.
2 things to test this.
-hook directly to your cablemodem. This usually requires powering off the modem for 30 seconds, then back on (otherwise it wont see a new mac address and you wont get an IP) Once you have a public IP test again.
-or change your subnet. remember to change the dhcp first so that you dont lose connectivityh first. then change the private ip subnet from 192.168.1.x to 192.168.xxx.x
use something uncommon like 67 or whatever.
I have had some applications that choke if the remote private network is the same IP subnet as the local subnet. Hence the more unique the better.
The server at: www.marketplace6.com is forwarding to: gm.marketplace6.com
Not sure why.... 'gm' host resolving on a different IP address than 'www'.
Question for you: why 22 hops to get there? I'm in California, and 11 hops gets me to either host.
Name: www.marketplace6.com
IP Address: 69.94.7.211
Location: Bridgeport (41.261N, 73.211W)
Network: TRUM-0001
Name: gm.marketplace6.com
IP Address: 69.94.7.201
Location: Bridgeport (41.261N, 73.211W)
Network: TRUM-0001
Not sure why.... 'gm' host resolving on a different IP address than 'www'.
Question for you: why 22 hops to get there? I'm in California, and 11 hops gets me to either host.
Name: www.marketplace6.com
IP Address: 69.94.7.211
Location: Bridgeport (41.261N, 73.211W)
Network: TRUM-0001
Name: gm.marketplace6.com
IP Address: 69.94.7.201
Location: Bridgeport (41.261N, 73.211W)
Network: TRUM-0001
ASKER
aleghart:
I wouldn't know why 22 hops to get there, I subscribe to Comcast, and the first 8 hops or so are just to get out of the comcast.com domain dns servers. It might be an inefficiency on the comcast dns servers, one would assume that 1 or 2 hops is enough for your domain's dns servers to figure out where to send you.
I wouldn't know why 22 hops to get there, I subscribe to Comcast, and the first 8 hops or so are just to get out of the comcast.com domain dns servers. It might be an inefficiency on the comcast dns servers, one would assume that 1 or 2 hops is enough for your domain's dns servers to figure out where to send you.
ASKER
ecszone:
- I tried changing my subnet to 192.168.57.xxx... didn't work. I still can't reach the website.
- I didn't get to try your other suggestion about connecting directly to the router, however, even if that worked, it would still not solve my problem as I wouldn't like to spend the whole time directly attached to the router... :-)
Thanks.
- I tried changing my subnet to 192.168.57.xxx... didn't work. I still can't reach the website.
- I didn't get to try your other suggestion about connecting directly to the router, however, even if that worked, it would still not solve my problem as I wouldn't like to spend the whole time directly attached to the router... :-)
Thanks.
It would just rule out your router. when your on the vpn the traffic is masked to your router.
It could be some type of issue with your router.. i cant imagine whta unless you did some significant non-standard changes.
Its an odd problem I give you that
It could be some type of issue with your router.. i cant imagine whta unless you did some significant non-standard changes.
Its an odd problem I give you that
>It might be an inefficiency on the comcast dns servers
DNS servers only resolve a host name to an IP address. Thereafter, routers direct traffic to the next hop. At that hop, more routers direct to the next hop.
DNS servers only resolve a host name to an IP address. Thereafter, routers direct traffic to the next hop. At that hop, more routers direct to the next hop.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
See if its a browser only issue. Try a SSL version of the same URL.
Your testing really narrows down the possibilities.
Maybe find out if your ISP is blocking it for some reasoN?