unable to load ONE web site.. ;

[sc]

Hi,
I would appreciate any/all suggestions/feedback how to resolve this. thanks
in advance!

I've been trying for weeks to access a web site (http://www.elmomc.com/)
that I can get to from outside of my home network but not at home..

I am using Comcast DSL, I several workstations and non can access this site.
Although, if i take one of those workstation somewhere else, it gets the
site. I've called comcast and they're unable to say why this is happending.
I did a tracert and this is what i see..

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

C:\Documents and Settings\Administrator>ping elmomc.com

Pinging elmomc.com [199.203.54.191] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

C:\Documents and Settings\Administrator>tracert 199.203.54.191

Tracing route to vl654.host191.netvision.net.il [199.203.54.191]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.2.1
2 14 ms 14 ms 17 ms 10.221.180.1
3 15 ms 12 ms 13 ms bar01-p6-1-0.sctthe1.ma.attbb.net
[65.96.0.149]

4 13 ms 13 ms 14 ms 24.91.0.5
5 13 ms 14 ms 15 ms bar01-p0-0.brtnhe1.ma.attbb.net
[65.96.0.249]
6 15 ms 14 ms 20 ms bic01-p4-0.ndhmhe1.ma.attbb.net
[24.91.0.177]
7 18 ms 14 ms 14 ms 12.125.33.33
8 14 ms 14 ms 13 ms gbr1-p60.cb1ma.ip.att.net [12.123.40.138]
9 16 ms 16 ms 22 ms tbr1-p013402.cb1ma.ip.att.net [12.122.5.53]
10 20 ms 24 ms 21 ms tbr2-cl1.n54ny.ip.att.net [12.122.10.22]
11 31 ms 21 ms 19 ms ggr2-p390.n54ny.ip.att.net [12.123.3.62]
12 20 ms 20 ms 20 ms 0.so-2-1-0.BR1.NYC4.ALTER.NET
[204.255.168.1]
13 22 ms 19 ms 21 ms 0.so-6-0-0.XL1.NYC4.ALTER.NET [152.63.21.78]
14 20 ms 21 ms 20 ms 0.POS6-0.GW12.NYC4.ALTER.NET [152.63.22.77]
15 39 ms 38 ms 20 ms netvision2-gw.customer.alter.net
[157.130.25.38]

16 186 ms 165 ms 168 ms pos2-4.core2.hfa.nv.net.il [212.143.12.14]
17 180 ms 162 ms 167 ms gi1-2.srvc01.hfa.nv.net.il [212.143.8.71]
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.

 

[Jan Il]

Hi sc

Here are a few things you might try:

Internet Explorer Cannot Connect to Secure Web Sites
http://www.helpwithwindows.com/WindowsXP/troub-10.html

or....

Why can't I browse certain websites
http://www.dslreports.com/faq/10082

Cannot Connect to Secure Sites

http://www.duxcw.com/faq/win/xp/secure.htm


and...........

1.) HOSTS file located @/in %WinDir%\system32\drivers\etc

(Open it with Notepad.exe and see if those sites are equated to ANY IP
address - this is because this file can either speedup OR block sites.
Equating a site's URL to 127.0.0.1 will block that site, and/or possibly
equating it to a REAL IP address for the purposes of speeding up a site can
misfire IF the site owners change the IP address of that URL for said
concerned website)

The HOSTS file needs only 1 entry -

localhost 127.0.0.1

(And, you can get away without one period, IF your system is not attached to
a LAN/WAN network... a standalone system can operate without HOSTS period!)

2.) This area in the registry, for HOSTS file databasepath redirections:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

The default from Microsoft for the "DataBasePath" entry is
%WinDir%\system32\drivers\etc (as mentioned above in #1)... if it is
otherwise, change it to that, or (using C:\WINNT for Windows 2000 or
C:\WINDOWS for Windows XP/2003) to C:\WINDOWS\System32\Drivers\etc

3.) IPSecurity Policies in secpol.msc - this can be used for the purposes of
blocking out sites, i.e.-> A "poor man's" firewall of sorts.

4.) Any firewall program you use – Zone Alarm, for instance/example, can
block out sites and their cookies (which some sites require for using their
stuff).

EDIT PART> Adding to #4, some sites NEED you to take their cookies and 3rd
party cookies too... you might want to look @ or OVERRIDE your cookies
policies in 'Internet Options' via Control Panel again & the Privacy tab
too!

5.) Try disabling the XP SP2 firewall and see if that helps.

If these steps do not resolve your problem, or you need help with the above,
please post back to this thread with the details and any error messages.

Hope this helps

Jan
Smiles are meant to be shared,
that's why they're so contagious.

Replies are posted only to the newsgroup for the benefit or other readers.
How to make a good newsgroup post:
http://www.dts-l.org/goodpost.htm

Hi,
I would appreciate any/all suggestions/feedback how to resolve this. thanks
in advance!

I've been trying for weeks to access a web site (http://www.elmomc.com/)
that I can get to from outside of my home network but not at home..

I am using Comcast DSL, I several workstations and non can access this site.
Although, if i take one of those workstation somewhere else, it gets the
site. I've called comcast and they're unable to say why this is happending.
I did a tracert and this is what i see..

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

C:\Documents and Settings\Administrator>ping elmomc.com

Pinging elmomc.com [199.203.54.191] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

C:\Documents and Settings\Administrator>tracert 199.203.54.191

Tracing route to vl654.host191.netvision.net.il [199.203.54.191]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.2.1
2 14 ms 14 ms 17 ms 10.221.180.1
3 15 ms 12 ms 13 ms bar01-p6-1-0.sctthe1.ma.attbb.net
[65.96.0.149]

4 13 ms 13 ms 14 ms 24.91.0.5
5 13 ms 14 ms 15 ms bar01-p0-0.brtnhe1.ma.attbb.net
[65.96.0.249]
6 15 ms 14 ms 20 ms bic01-p4-0.ndhmhe1.ma.attbb.net
[24.91.0.177]
7 18 ms 14 ms 14 ms 12.125.33.33
8 14 ms 14 ms 13 ms gbr1-p60.cb1ma.ip.att.net [12.123.40.138]

9 16 ms 16 ms 22 ms tbr1-p013402.cb1ma.ip.att.net [12.122.5.53]
10 20 ms 24 ms 21 ms tbr2-cl1.n54ny.ip.att.net [12.122.10.22]
11 31 ms 21 ms 19 ms ggr2-p390.n54ny.ip.att.net [12.123.3.62]
12 20 ms 20 ms 20 ms 0.so-2-1-0.BR1.NYC4.ALTER.NET
[204.255.168.1]
13 22 ms 19 ms 21 ms 0.so-6-0-0.XL1.NYC4.ALTER.NET [152.63.21.78]
14 20 ms 21 ms 20 ms 0.POS6-0.GW12.NYC4.ALTER.NET [152.63.22.77]
15 39 ms 38 ms 20 ms netvision2-gw.customer.alter.net
[157.130.25.38]

16 186 ms 165 ms 168 ms pos2-4.core2.hfa.nv.net.il [212.143.12.14]
17 180 ms 162 ms 167 ms gi1-2.srvc01.hfa.nv.net.il [212.143.8.71]
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.

 

[Robert Aldwinckle]

....

I've been trying for weeks to access a web site (http://www.elmomc.com/)

I did a tracert and this is what i see..

Pinging elmomc.com [199.203.54.191] with 32 bytes of data:

Tracing route to vl654.host191.netvision.net.il [199.203.54.191]

Why are you testing the domain name?
You should be testing the server name that you want to connect to.

telnet elmomc.com 80

shows you that there isn't even an HTTP server listening there
so if that is what you have been entering it would explain your "problem"


BTW did you try any of the suggestions I gave you in your *previous*
thread?

<
http://www.microsoft.com/windows/ie...19a1&catlist=&dglist=&ptlist=&exp=&sloc=en-US >

Oh. I see where perhaps you may be getting confused.
I only suggested using nslookup with the domain name
as a means of getting your DNS to get in contact with the
server's primary name server. If your nslookup is finding
the correct address for the HTTP server you wouldn't want
to bother with the address associated with the domain name.

In order to eliminate all concern about DNS lookup
why not add an entry to your HOSTS file and see if
it works any better?

199.203.1.129 www.elmomc.com


BTW it would be much better if you had continued in your original
thread. I only spotted this one by accident.


Good luck

Robert Aldwinckle
---

 

[sc]

Hi, thanks for the respond. how can there not be a HTTP Server listening
when others get to that URL from different location?

I did tried your previous suggestions before and I'm still stuck at this
problem.

When I do a tracert, and it gets to "route to vl654.host191.netvision.net.il
[199.203.54.191]" does this tell me it's getting out of my computer/Comcast
network and then failing over in il ?

If it was an DSN issue, wouldn't I also have been able to get to the site
via the IP address? I can't get to it either by name or IP!

Would appreciate more feedback/suggestions...

thanks in advance!

...

I've been trying for weeks to access a web site (http://www.elmomc.com/)

I did a tracert and this is what i see..

Pinging elmomc.com [199.203.54.191] with 32 bytes of data:

Tracing route to vl654.host191.netvision.net.il [199.203.54.191]

Why are you testing the domain name?
You should be testing the server name that you want to connect to.

telnet elmomc.com 80

shows you that there isn't even an HTTP server listening there
so if that is what you have been entering it would explain your "problem"


BTW did you try any of the suggestions I gave you in your *previous*
thread?

<
http://www.microsoft.com/windows/ie...19a1&catlist=&dglist=&ptlist=&exp=&sloc=en-US >

Oh. I see where perhaps you may be getting confused.
I only suggested using nslookup with the domain name
as a means of getting your DNS to get in contact with the
server's primary name server. If your nslookup is finding
the correct address for the HTTP server you wouldn't want
to bother with the address associated with the domain name.

In order to eliminate all concern about DNS lookup
why not add an entry to your HOSTS file and see if
it works any better?

199.203.1.129 www.elmomc.com


BTW it would be much better if you had continued in your original
thread. I only spotted this one by accident.


Good luck

Robert Aldwinckle

 

[Robert Aldwinckle]

Hi, thanks for the respond. how can there not be a HTTP Server listening
when others get to that URL from different location?

My point is that you are testing the address for the domain name
not the address for the HTTP server (the www. name).
In fact, you don't even prove that you normally have a correct address
for the server, which I have already given you twice.

There seems to be no HTTP server at the address given by
the domain name. elmomc.com

Therefore that is not a name that you should be trying to use
to fetch HTML pages from.

There does seem to be an HTTP server at the adresss given
by the server name: www.elmomc.com

To see this enter in a command window:

telnet www.elmomc.com 80

If the screen clears the site has a server listening on port 80.


Therefore that is the name that you could try to use to fetch HTML
pages from.

Since there are different addresses for each name I don't think
it makes much sense to bother testing with the name that you don't
intend to use. Instead you should test with the name that you do
intend to use.

You should not expect either ping or tracert to prove that you have
connectivity to the HTTP server. Both commands use the ICMP
protocol which many hosts disable in order to try avoid "Denial of
Service" attacks. As I tried to explain the only reason I mentioned
either command is to use them as a means of doing a DNS lookup.

In fact, in NT5* both commands lookup via the dnscache which is seeded
by the HOSTS file; so really the best way to do a DNS lookup is
to use nslookup. However, I showed you that I initially got timeouts
for that lookup with my nslookup. Sometimes retrying the lookup is
enough to make it work and sometimes not. Provided there is no override
(e.g. in the dnscache) the lookup that tracert does *seems* to be more
reliable. (Perhaps it has a different timeout tolerance than the other
command.) In the other thread I also hinted at other more advanced
options which could help assist a DNS lookup which was failing.
But in order to avoid all that complexity I suggested you add an entry
into your HOSTS file.

I did tried your previous suggestions before and I'm still stuck at this
problem.

Does this mean that you added an entry to your HOSTS file
as I suggested last? If so, you may have to flush the dnscache
(or reboot) to ensure that the new override is being used.

FYI to flush the dnscache, enter in a command window:

ipconfig /flushdns


Good luck

Robert
---

When I do a tracert, and it gets to "route to vl654.host191.netvision.net.il
[199.203.54.191]" does this tell me it's getting out of my computer/Comcast
network and then failing over in il ?

If it was an DSN issue, wouldn't I also have been able to get to the site
via the IP address? I can't get to it either by name or IP!

Would appreciate more feedback/suggestions...

thanks in advance!

...

I've been trying for weeks to access a web site (http://www.elmomc.com/)

I did a tracert and this is what i see..

Pinging elmomc.com [199.203.54.191] with 32 bytes of data:

Tracing route to vl654.host191.netvision.net.il [199.203.54.191]

Why are you testing the domain name?
You should be testing the server name that you want to connect to.

telnet elmomc.com 80

shows you that there isn't even an HTTP server listening there
so if that is what you have been entering it would explain your "problem"


BTW did you try any of the suggestions I gave you in your *previous*
thread?

<
http://www.microsoft.com/windows/ie...19a1&catlist=&dglist=&ptlist=&exp=&sloc=en-US >

Oh. I see where perhaps you may be getting confused.
I only suggested using nslookup with the domain name
as a means of getting your DNS to get in contact with the
server's primary name server. If your nslookup is finding
the correct address for the HTTP server you wouldn't want
to bother with the address associated with the domain name.

In order to eliminate all concern about DNS lookup
why not add an entry to your HOSTS file and see if
it works any better?

199.203.1.129 www.elmomc.com


BTW it would be much better if you had continued in your original
thread. I only spotted this one by accident.


Good luck

Robert Aldwinckle