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?
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/06/determining-mtu-to-single-server.html
--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://networking.nitecruzr.net/
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.
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
>I finally fixed it!!
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/06/autotuning-in-vista-maybe-not-ready-for.html
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.
--
Sliceco
------------------------------------------------------------------------
Sliceco's Profile: http://forums.techarena.in/members/119862.htm
View this thread: http://forums.techarena.in/windows-vista-network/956570.htm