Hi, I have a clean installation of Windows Vista RC1 on my laptop along side Windows XP Pro SP2. When I start Vista, I can connect to the internet with out any problemsl, after like 5 minutes, if I close IE, then open it, I can't browse anything. It gives me an error message and when I choose to diagnose the problem, it says that it is a DNS issue, and the host name it unknown. The weird thing, is that my IM Clients (Live Messenger, Gtalk, Skype) all keep on working when IE stops, this is because they have activity going on (same if I stream radio). But if I sign out, I can't sign back in. The only way that I have found to restore network connectivity is to restart my machine. I have installed the Marvel Yokun Adapter, I have disabled the TCP Check Sum Offload as some posts suggested. I have also tried the following command "netsh interface tcp set global autotuninglevel=disabled", but to no avail. P.S. I connect to the internet through a residential gateway at my apartment building, and internet connectivity is not working at all on XP!!! Thanks

Windows Vista has amazing new generation TCP/IP stack, it allows automatic tuning for your connection relying on available bandwidth and other factors/parameters of your network connection. There is also many other options regarding internet like saving webpages or important connectionpackets for next usage. And that's clearly shown in your issue, you can easily login your IM software as smart windows TCP/IP stack recognized the static IP of IM servers for quick smart and dircet connection without needing to determine the hostname then convert it to it's IP via your ISP DNS server which might have sevre issues with. I can also add the problem is related "Offline Files" found in Control Panel, you can adjust it by increasing limit of offline files in Disk Usage tab and then you can enable it working by checking "On slow connections, automatically work offline" and apply it. If you already using this and the problem still exist, try to uncheck it. If the problem still exist, let me in the know so that we find out another solution.

I am also having a similar issue. Please help. I installed Vista RC1 yesterday. Most all programs can access the internet ie. Online Poker Software, but internet explorer is unable to access any website. Any ideas. I sometimes even get a invalid web address message. I can however ping these same web site with good response through command prompt. Please help.

I think that I've shown good solution, try it Aleopold. Good luck

Hello Aleopold Did you read the following post? http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=757462&SiteID=17

Hi, Thanks for your response. I still haven't been able to verify the fix you gave me. The network is down at home, and I connected to my work network and every thing seems to be working perfectly there.

Maybe some issue with your home network topology! Read these information: The following are the new features of the Next Generation TCP/IP stack in Windows Vista: Dual IP layer architecture for IPv6 The implementation of IPv6 in Windows XP and Windows Server 2003 is a dual stack architecture. For IPv6 support, you have to install a separate protocol through the Network Connections folder. The separate IPv6 protocol stack had its own Transport layer that included Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) and its own Framing layer. Changes to protocols in either the Transport or Framing layers had to be done to two Windows drivers; Tcpip.sys for the IPv4 protocol stack and Tcpip6.sys for the IPv6 protocol stack. The Next Generation TCP/IP stack supports the dual IP layer architecture in which the IPv4 and IPv6 implementations share common Transport and Framing layers. The Next Generation TCP/IP stack has both IPv4 and IPv6 enabled by default. There is no need to install a separate component to obtain IPv6 support. Easier kernel mode network programming The Next Generation TCP/IP stack supports Winsock Kernel (WSK). WSK is a new transport-independent kernel mode Network Programming Interface (NPI) for Transport Driver Interface (TDI) clients. Using WSK, kernel-mode software modules can perform network communication using socket-like programming semantics similar to those supported in the user-mode Windows Sockets 2 API. While TDI is supported in Windows Vista for backward compatibility, TDI clients should be updated to use WSK to achieve the best performance. Support for a strong host model When a unicast packet arrives at a host, IP must determine whether the packet is locally destined (its destination matches an address that is assigned to an interface of the host). IP implementations that follow a weak host model accept any locally destined packet, regardless of the interface on which the packet was received. IP implementations that follow the strong host model only accept locally destined packets if the destination address in the packet matches an address assigned to the interface on which the packet was received. The current IPv4 implementation in Windows XP and Windows Server 2003 uses the weak host model. The Next Generation TCP/IP stack supports the strong host model for both IPv4 and IPv6 and is configured to use it by default. You can configure the Next Generation TCP/IP stack to use a weak host model. The weak host model provides better network connectivity. However, it also makes hosts susceptible to multihome-based network attacks. New security and packet filtering APIs The interfaces in the current TCP/IP stack for TCP/IP security (filtering for local host traffic), the firewall hook, the filter hook, and the storage of packet filter information has been replaced with a new framework known as the Windows Filtering Platform (WFP). WFP provides filtering capability at all layers of the TCP/IP protocol stack. WFP is more secure, integrated in the stack, and much easier for independent software vendors (ISVs) to build drivers, services, and applications that must filter, analyze, or modify TCP/IP traffic. New mechanisms for protocol stack offload The Next Generation TCP/IP stack can offload the processing of TCP and other types of traffic to Network Driver Interface Specification (NDIS) miniport drivers and network interface adapters. Offloading TCP and other protocol processing can improve performance for high-bandwidth networks or high-volume servers. New support for scaling on multi-processor computers The architecture of NDIS 5.1 and earlier versions limits receive protocol processing to a single processor. This limitation can inhibit scaling to large volumes of network traffic on a multi-processor computer. Receive-side Scaling resolves this issue by allowing the network load from a network adapter to be balanced across multiple processors. New extensibility The Next-Generation TCP/IP stack has an infrastructure to enable more modular components that can be dynamically inserted and removed. Reconfiguration without having to restart the computer The Next-Generation TCP/IP stack uses a new method to store configuration settings that enables more dynamic control and does not require a computer restart after settings are changed. Automatic configuration of stack settings based on different network environments The Next-Generation TCP/IP stack automatically senses the network environment and adjusts key performance settings, such as the TCP receive window. Improved stack auto-tuning and configuration reduces the need for manual configuration of TCP/IP settings. Supportability enhancements There is extensive support for run-time diagnostics, including support for TCP Management Information Base (MIB)-II and better system event logging and tracing. The following features are improvements in the Next Generation TCP/IP stack: Better support for computers that roam between networks. Better support for developers of multicast-enabled applications and networks. TCP performance enhancements for high-speed networks, asymmetric satellite links, and wireless and other high loss networks. Improved portability of the Next Generation TCP/IP stack to other Microsoft operating systems such as Windows CE, Xbox, and Windows Embedded. Improved resistance against all known TCP/IP-based denial of service and other types of network attacks.