![]() |
|
Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
|||||||
| Performance and Maintainance of Windows Vista A forum for performance and maintenance tasks in Windows Vista. (microsoft.public.windows.vista.performance_maintainance) |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Evidentily a lot of people are experiencing interent problems with Vista
RC1, including me. When trying to go to sites, the magority of them time out by URL or IP. All of my settings are correct or (dumbed down) in Vista. IPv4 has static entries. Firewall off. Security set to low. Blockers, virus prgms etc disabled. IPv6 disabled on NIC. MTU set to 1452. TCP Recieve Window set to 32767. All of my other connected XP and W2K computers get to the internet with no problems, thereby elimintating router, dsl issues. I know it also has nothing to do with switch port. Things I've tried besides the obvious type stuff listed above. 1. Since Vista automatically tunes interface settings, I disabled that function by running the command: netsh int tcp set global autotuninglevel=disabled. Then I manually set the MTU and TCP Recieve Window in the registry since DrTCP and Vista are incompatible. What I've learned. The latest available Vista build has a bug where it tanks when coming across SPI (stateful packet inspection) in some routers. Which is why this problem is only affecting some people. Disabling SPI in my Cisco 837 leaves too much of a vunerability, so that's not an option. Leaving me with having to uninstall Vista and go back to XP. I haven't heard anyone say if RC2 corrects this problem. Now that MS has pulled RC2, maybe they would consider making it available again if it does indeed fix the internet problem. My questions are, is there currently a known fix, workaround or some kind of voodo that will make the internet go? Because frankly, a problem of this magnitude should not be showing up in a RC. |
|
|||
|
Sorry I laugh at lines like ... "Disabling SPI in my Cisco 837 leaves too
much of a vunerability, so that's not an option" .. You have the nations secrets on your PC? Or are you so paranoid that the thought of you disable or bypassing your router for a few minutes would be too costly? Come on! "Flatch U. Lance" wrote: Evidentily a lot of people are experiencing interent problems with Vista RC1, including me. When trying to go to sites, the magority of them time out by URL or IP. All of my settings are correct or (dumbed down) in Vista. IPv4 has static entries. Firewall off. Security set to low. Blockers, virus prgms etc disabled. IPv6 disabled on NIC. MTU set to 1452. TCP Recieve Window set to 32767. All of my other connected XP and W2K computers get to the internet with no problems, thereby elimintating router, dsl issues. I know it also has nothing to do with switch port. Things I've tried besides the obvious type stuff listed above. 1. Since Vista automatically tunes interface settings, I disabled that function by running the command: netsh int tcp set global autotuninglevel=disabled. Then I manually set the MTU and TCP Recieve Window in the registry since DrTCP and Vista are incompatible. What I've learned. The latest available Vista build has a bug where it tanks when coming across SPI (stateful packet inspection) in some routers. Which is why this problem is only affecting some people. Disabling SPI in my Cisco 837 leaves too much of a vunerability, so that's not an option. Leaving me with having to uninstall Vista and go back to XP. I haven't heard anyone say if RC2 corrects this problem. Now that MS has pulled RC2, maybe they would consider making it available again if it does indeed fix the internet problem. My questions are, is there currently a known fix, workaround or some kind of voodo that will make the internet go? Because frankly, a problem of this magnitude should not be showing up in a RC. |