Starting at Windows Vista RC1 I am unable to connect to my home router and access the internet. For some reason he keeps telling me that there is only limited connectivity. It looks like that he won't receive a IP from my router (a Sweex Annex-A ADSL modem and switch). Manually assigning an IP won't work either. It is really starting to drive me nuts. Especially because the problem still exists in RC2 wich I just installed. Using the diagnose and repair functionality helps nothing. I enabled/disabled IPv6 and every other protocol in the list. On several occasions I managed to get a connection trough the router and to the internet. But that was very rare. Only after continually resetting the adapter, setting manual and automatic IP adresses he would "detect" my router and create a connection. I have a AsROCK 939Dual-SATA2 motherboard with a onboard ULI lan. The fact that it works, even in rare occasions, would seem that there is no problem with the onboard adapter and Vista? I guess it has something to do with new technology Vista uses to connect to networks, wich is incompatible with my router? I learned about a patch but that won't work because he says that it is not ment for my system. Anyone any ideas?

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.

Thank you for the extensive message, but I don't know what to do with it? What exactly applies to my situation?

HI, I don't know how to fix it, but I have the same motherboard and the exact same problem! ULi Lan works fine when I boot to XP, but limited connectivity almost constantly when running Vista! :( I get the sneaky suspicion that the post above is a very long winded way of saying it's "a new feature". Hehe. Somebody must know how to fix this,its supposed to be a popular board!? I've downloaded the latest drivers etc, set static and manual IP, disabled IP6 on the connection... nothing. Have even tried uninstalling it in device manager, <reboot> disabling it in the bios, then rebooting againthen re-enabling it, same problem.

check out http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=755630&SiteID=17

when i trying to connect my new laptop with vista to xp network group through wireless acces point that time it saying limited coonectivity .and ipv4 and ipv6 also showing limited or no connectivty and i tried to instal ipv4 on my lap i coudnt install ipv4 protocol anye one can give how to solve this problem ?

Altough this thread received the status answered, it's absolutely not !I just received my new laptop (sadly preloaded with Vista) and I've exactly the same problem as above:- All my computers can connect wirelessly to my home network (XP & Linux based).- Vista can associate with access point but is unable to receive an ip from dhcp (and even if I manually set ip, mask, default gateway and dns, I can't ping any computer or connect to the internet).- I tried as most to disable ipv6, other useless protocol, firewall... still nothing !- Vista keep setting my home network as "unidentified network", "public network" (this latest can be manually changed to private but it doesn't help either)Is there any solution out there (except going back to XP or some real OS) ?[EDIT] tried a few more things stil without success...Is there anyway to disable this tcp / udp checksum offload for an Intel WiFi Link 4965AGN wirelless ?(registry or ... because there's absolutely no such option in advanced tab)NB. connecting to a Linksys WAP54G AP which is connected to my network (where stands router, dhcp, DNS)

Well there are some updates for you guys. First thing to do if you haven't done it yet is to unplug your router for at least60 seconds, most of manufacturers will tell you 10 seconds but with my case it took much longer than that and this is when I first got the "limited connectivity" message.Then reboot your PC; as daft as it may sounds it is often one of the first thing to do. If the problem persist, go to "Control Panel" and select the "Manager Connection" or whatever it is called (I have to apologise for my lack of knowledge regarding the terms used with Vista I'm still using XP)once you're there click on"Status" It should open the "Local Area Network Status" go to "Properties". On the "IPv6" go to "Properties" and make sure that it is ticked "Get connected automatically" (oranything similar to that). Once I checked that I rebooted thePC and everything was workingfine. Another alternative to consider is to install the CD driver from your home hub and installeverything you can from that. I hope that this information will be useful to you and please give me some feedback.

thanks for answer, but got bored... I reinstalled dual boot XP/Gentoo, both connecting without problem...

i got a problem to. my internet works fine but for some reason the ipv6 is on limited. the ipv4 is internet. but my internet kicks me off sometimes at random times. like i can be playing and online game and it will kick me off. can somone help me i just bought this computer

@ Avi:On most networks, IPv6 will show as 'limited connectivity', because some part of the network (router, switch, access point) doesn't properly (if at all) support IPv6.You can stop Windows from reporting that issue (and, possibly, correct your actual problem) by disabling IPv6:http://www.mydigitallife.info/2007/09/09/disable-and-turn-off-ipv6-support-in-vista/HTH,Chris[If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]

Thanks a lot!! Your answer so far seem to be working for me!! I just want to give a feed back!!