Vista - Cannot connect to one website

I cannot connect to one website via HTTP or HTTPS - www.discover.com. After
installing SP1, I can no longer connect to this one website. I have Zone
Alarm along with Vista's built in firewall installed, and there is a firewall
build in to the 2 wire DSL router I have. Antivirus is Symantec antivirus
10.2.0.276. Windows defender is also installed. I've diabled all firewalls
and antivirus and setup a DMZ on the router and still cannot connect. When I
try to connect in IE, it gives the error page:
res://ieframe.dll/dnserror.htm#http://www.discover.com/ which seems to
indicate either a DNS or a firewall error. Running Vista's diagnostic tests
says that port 80 or 443 is being blocked, but with all firewalls off, I
can't imagine by what. I've installed virtual pc and installed xp with sp2 on
the virtual pc and that is able to connect through vista to that website. Via
a XP SP2 laptop on the local LAN i'm also able to connect. I've tried to
uninstall and reinstall the NIC. The machine has a PCI wireless card and
using that it is also not able to connect. I've tired to use my cellular
provider for dial-up access and that also did not work. I've tired safe mode
with networking and still no luck. Of course all other sites are normal. I've
tried resetting IE settings, adding the site to the trusted sites, running
with no add-ons, all with no luck. I've messed with the security settings as
suggested in some threads and no luck. I've also tried Opera, Firefox, and
Safari and none of them can connect either. There is no proxy setup either.
I've reset the IP and Winsock ( ipconfig /flushdns, /renew, netsh int ip
reset, netsh winsock reset, etc) and nothing helps. When I try to ping the
site, it works fine:

Pinging www.discover.com [199.38.149.1] with 32 bytes of data:
Reply from 199.38.149.1: bytes=32 time=29ms TTL=116
Reply from 199.38.149.1: bytes=32 time=28ms TTL=116
Reply from 199.38.149.1: bytes=32 time=27ms TTL=116
Reply from 199.38.149.1: bytes=32 time=27ms TTL=116

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

Running a TRACERT shows:

Tracing route to www.discover.com [199.38.149.1]
over a maximum of 30 hops:

1 4 ms 3 ms 3 ms homeportal.gateway.2wire.net [172.16.0.1]
2 17 ms 16 ms 17 ms adsl-76-226-79-254.dsl.sfldmi.sbcglobal.net
[76.
226.79.254]
3 16 ms 17 ms 16 ms 76.205.15.66
4 17 ms 16 ms 17 ms bb2-g10-0.sfldmi.sbcglobal.net [151.164.43.63]
5 24 ms 22 ms 23 ms 151.164.95.166
6 23 ms 24 ms 24 ms gar8.cgcil.ip.att.net [12.122.79.85]
7 26 ms 24 ms 25 ms tbr2.cgcil.ip.att.net [12.122.99.66]
8 24 ms 24 ms 25 ms gar4.cgcil.ip.att.net [12.123.6.14]
9 25 ms 24 ms 27 ms 12.116.239.22
10 27 ms 26 ms 26 ms 199.38.154.242
11 27 ms 32 ms 26 ms 10.6.2.1
12 26 ms 28 ms 26 ms 10.6.10.4
13 26 ms 27 ms 27 ms 199.38.149.1

Trace complete.

IPCONFIG /ALL shows:

Windows IP Configuration

Host Name . . . . . . . . . . . . : 615WD41
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : gateway.2wire.net

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : gateway.2wire.net
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
Physical Address. . . . . . . . . : 00-0C-F1-A6-7D-B1
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 172.16.1.35(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Lease Obtained. . . . . . . . . . : Friday, April 25, 2008 1:52:17 AM
Lease Expires . . . . . . . . . . : Friday, April 25, 2008 3:52:17 AM
Default Gateway . . . . . . . . . : 172.16.0.1
DHCP Server . . . . . . . . . . . : 172.16.0.1
DNS Servers . . . . . . . . . . . : 172.16.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

I've run spyware / antivirus scans along with hijackthis and nothing has
turned up. Short of uninstalling SP1, I have done everything that I can think
of. Since this is the only website I cannot connect to, there must be
something burried in Vista that is blocking it, but I do not know what that
could be. I don't know if I stated it earler, but I have not problem
connecting to other websites on port 80 or 443, just discover.com. Trying to
connect from search engine results also does not work, for what it's worth. I
also have attempted to change the DNS servers to OpenDNS servers, but that
did not help. I have Cisco VPN on the machine and am able to connect to my
work, but even then I cannot navigate to discover.com. I was able to go to
discover.com prior to SP1 and it was working normally.

I'm not exactly new to computers, but this one has me stumped. Any ideas?

Same exact problem here. over an hour with microsoft tech support
hailing from India and they couldn't figure it out. This needs to go
to the top programmers at microsoft but does anyone know a way to get
it to them?

On Fri, 25 Apr 2008 00:39:00 -0700, ddale900
<ddale900@xxxxxx> wrote:
Check the MTU setting. That one did not get replaced by AutoTuning.
<http://networking.nitecruzr.net/2007/06/determining-mtu-to-single-server.html>
http://networking.nitecruzr.net/2007...le-server.html

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://networking.nitecruzr.net/

I finally fixed it!!
Thanks for the help Chuck, it turns ouot that it wasn't specifically the MTU
setting you were talking about, but at least that got me pointed in the right
direction. I tried pinging discover and changing the MTU from 1500 default
down to 1464 before it finally stuck with the -f setting. So I changed the
MTU and nothing and now I had to lower the MTU for the -f ping to 1430???
Odd, seems whatever I changed the MTU to, the discover website needed a lower
setting. So I started to search around for this and found this website:
http://www.mydigitallife.info/2007/0...lems-in-vista/
Here the website describes using the "netsh interface tcp show global"
command at the command prompt in order to view the global tcp settings. I did
that and mine showed:

C:\>netsh interface tcp show global
Querying active state...

TCP Global Parameters
----------------------------------------------
Receive-Side Scaling State : enabled
Chimney Offload State : disabled
Receive Window Auto-Tuning Level : normal
Add-On Congestion Control Provider : ctcp
ECN Capability : enabled
RFC 1323 Timestamps : disabled

the website says the default parameters the appear would be
———————————————-
Receive-Side Scaling State : enabled
Chimney Offload State : enabled
Receive Window Auto-Tuning Level : normal
Add-On Congestion Control Provider : none
ECN Capability : disabled
RFC 1323 Timestamps : disabled

So now I knew my setup was not what the norm was supposed to be. I tried the
fix described on the site and disabled auto-tuning level and no luck. So I
decided to figure out how to change the rest of the settings to what were
displayed on that website using the following commands:

C:\>netsh interface tcp set global chimney=enabled
Ok.

C:\>netsh interface tcp set global congestionprovider=none
Ok.

C:\>netsh interface tcp set global ecncapability=disabled
Ok.

C:\>netsh interface tcp set global timestamps=disabled
Ok.

And Viola! click the link to discover.com and it worked! I may play arouond
with this again some more someday and figure out exactly which setting it was
that was keeping me out of discover's website and what exactly each setting
does, but any way you slice i've finally got the website back up and running
after a month and a half without it. Thanks for pointing me in the right
direction and hopefully this helps MarkimusPrime as well. Now if only I can
figure out how to get all the time back that i've spent trying to figure this
out...

Thanks.


"Chuck [MVP]" wrote:

God you're my savior. Your trick worked. I typed in those 4 commands
in te command prompt and I can finally use discover's website.. I LOVE
YOU

"ddale900" <ddale900@xxxxxx> wrote in message
news:01D07103-4FA4-4233-B81C-6A906B2C9313@xxxxxx
I see you solved your problem. I was playing around with the setting and it
looks to me that the culprit is the ECN setting. I enable that and can't
connect to discover.com but if I disable it then it comes right up. The
other settings didn't seem to have any affect.

NetBiznessMan

On Sun, 27 Apr 2008 19:22:00 -0700, ddale900
<ddale900@xxxxxx> wrote:
Thank you for the follow up. RWin AutoTuning is indeed a good thing to check
also.
<http://networking.nitecruzr.net/2007/06/autotuning-in-vista-maybe-not-ready-for.html>
http://networking.nitecruzr.net/2007...ready-for.html

--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://networking.nitecruzr.net/

You only need to change the ECN settings back to "disabled."

Type CMD in the "Start Search" field after clicking Vista's START button,
right click the cmd.exe file that pops up and "run as adminstrator," then
type:

netsh interface tcp set global ecncapability=disabled

Press enter to get the "ok" message. Try logging into www.discover.com (or
any variant).

I hope that this helps.

"ddale900" wrote:

This is the only trick that worked for me as well! Bloody brilliant


--
Sliceco
------------------------------------------------------------------------
Sliceco's Profile: http://forums.techarena.in/members/119862.htm
View this thread: http://forums.techarena.in/windows-v...ork/956570.htm

http://forums.techarena.in