Re: Failure with single web site (detailed)
- From: "Kevin Underriner" <k.underriner@xxxxxxxxxxx>
- Date: Mon, 9 Apr 2007 13:16:55 -0500
Yes, I've tried IP addresses as well as hostnames. Nothing in hosts, no
problem with DNS.
Recent test is interesting:
- telnet 69.25.56.150 80 fails
- telnet 69.25.56.151 80 succeeds
The above isn't so surprising as this duplicates the test using IP
addresses as a URL in browser.
- telnet 69.25.56.150 25 succeeds
Port 25 is SMTP. So it seems that I can successfully communicate with
69.25.56.150 with anything except port 80.
Another test:
I use sygate firewall, and yes, I've run tests with and without it running,
same result. I did a packet check with sygate: everything appears normal
when using http://www.linkedin.com as a URL in ie7 - meaning, that the
sygate firewall is receiving the information from the browser, so the
problem occurs after sygate.
Next test: power cycle router, hub, etc and force system to get a different
IP address.
"Poprivet" <poprivet@xxxxxxxxxxxxxxxxxxx> wrote in message
news:Onp$igseHHA.2376@xxxxxxxxxxxxxxxxxxxxxxx
Longshot, but; have you tried using http://69.25.56.150/ to access the
site?
Internap Network Services PNAP-12-2002 (NET-69-25-0-0-1)
69.25.0.0 - 69.25.255.255
LinkedIN INAP-SJE-LINKEDIN-1404 (NET-69-25-56-128-1)
69.25.56.128 - 69.25.56.255
# ARIN WHOIS database, last updated 2007-04-08 19:10
# Enter ? for additional hints on searching ARIN's WHOIS database.
Any chance it got added to your HOSTS file somehow? Just ramble-thinking;
probably njothing helpful there, but ... Pop`
Kevin Underriner wrote:
Problem: unable to connect to a single web site (www.linkedin.com;
69.25.56.150).
Summary: I have no idea if this is at all possible ... it seems as
if there is something preventing HTTP traffic to and from IP address
69.25.56.150 on only the afflicted machine.
Details:
System is Windows XP with all current service packs and updates.
Browser failure is with both ie7 and firefox (both updated with all
current packs/patches).
Problem has started very recently - web site was actively used up to
three days ago.
No changes were (consciously) made to the machine.
DNS resolution is fine. nslookup www.linkedin.com responds with
69.25.56.150.
ping works fine (ping www.linkedin.com or ping 69.25.56.150).
Site is accessible from another machine on the same network (this
eliminates any weird route caching on the network hardware).
Hosts file has nothing of interest.
Other linkedin ip addresses work (http://69.25.56.151), but any
redirection to a link with www.linkedin.com in the address fail as
this of course goes back to 69.25.56.150.
No proxies exist - direct network connection.
Problem is unaffected by the use of firewall (sygate), or any of the
Norton security stuff.
Spyware - clean. Adware - clean. Hijackthis - clean.
ipconfig /release, /renew, /fushdns, /registerdns - no affect.
Of course there were many (many) reboots during the diagnostics and
testing issued above.
.
- References:
- Failure with single web site (detailed)
- From: Kevin Underriner
- Re: Failure with single web site (detailed)
- From: Poprivet
- Failure with single web site (detailed)
- Prev by Date: Re: XP SP2 cannot contact DHCP after a restart
- Next by Date: Re: Failure with single web site (detailed) - SOLVED
- Previous by thread: Re: Failure with single web site (detailed)
- Next by thread: Re: Failure with single web site (detailed) - SOLVED
- Index(es):
Relevant Pages
|
