Anyone having network issues in 5474.5?


Recommended Posts

Event log's not much good:

Level Date and Time Source Event ID Task Category

Warning 7/22/2006 9:28:27 AM Microsoft-Windows-Dhcp-Client 1006 None Your computer was unable to automatically configure the IP parameters for the Network Card with the network address 00138F7C0A44. The following error occurred during configuration: The operation completed successfully..

:rolleyes: :rofl:

With the exception of a wireless pc card in my laptop, all my networking came up flawlessly OOTB.

Hate to suggest what I'm sure you already tried, but you checked your cable? Hub/switch/router?

Remove the onboard nic in device manager and let it reinstall itself after a reboot.

If you have a spare nic laying around, I'd drop that in and see if that picks up correctly.

They rewrote the network...so it's not gonna work with some routers/cable modems. Nothing wrong is with the setup...You might try update your router or cable modem firmware.

I have the testing machine with the same board...and network doesn't work. It worked with Beta 2 build after i updated d-link 4100 router firmware to the latest version 1.6. Now with 5472 build doesn't work again. This is beta 2 stage, and i hope after they're done all the routers will be supported etc...

I have a feeling that Vista might be expensive upgrade...which is not worth because OS itself is not worth of anything. Too bad Microsoft won't port DX10 to Windows XP platform, which i think is a bull****... Add support for SM4.0 is not a big deal having the fact that Windows XP doesn't require any LDDM model or any additional crap to handle OS gui.

I have this strange problem with my wireless card called asus wl-138 on this vista build. Well it didnt work at all on beta 2 but on this build it connects to the network but not with the internet, it says that my card does not support those needed requirements that my AP needs. It worked fine on pre beta 2 and on xp. I use xp driver. Perhaps i need to wait for a newer vista build or for asus guys to update drivers.

Edited by Nieware
  • 2 weeks later...

I can't get any network access with this build. I'm using the built in NIC on my ASRock 939Dual which has worked fine in previous builds. The drivers appear to install fine but I can't get access with DHCP or manual address assignment. :no:

did you try manualy installing the 2.20 Uli drivers? my onboard Ethernet didnt work till i updated the Uli drivers

Another Asus939Dual user here, and no luck with Vista's network. OCWForums had a similiar discussion, and no one could find a solution. I suppose we'll just have to wait until a new build and see if that fixes anything.

  • 4 weeks later...

I'm having trouble with my 3com nic in RC1 too. It was working flawlessly in the previous builds but now it's acting flaky, Windows Update doesn't work at all, it says there are some DNS errors now and then, sometimes it says the router is not found, and other times it sees everything.

But while all that is going on I can still connect to sites like Google. It's odd. I can't figure out what's going. I know it's not my ISP since the other computesr on my network can connect to stuff a-okay.

Same problem here. 939Dual and RC1. The NIC becomes "deaf" after a warm restart. It takes a full power-off at the power-supply to reset the NIC.

I've downgraded to two different XP-level drivers from ULi and the problem did not go away with either of them. So I don't think it's a driver issue.

  • 2 weeks later...

just chiming in with a 'me too'. I have a 939dual and have been having the same problem. seems to happen randomly...sometimes it works on boot sometimes it doesnt. Although it seems if i leave vista alone for a few minutes after it boots that it works. havent tested that enough though to be sure.

MS has confirmed this is a bug in the Uli drivers dealing with DHCP requests.

So one thing i am going to try doing on my next boot into vista is assigning a static IP to the machine. Perhaps if you avoid having any DHCP requests it'll work. I've set my router to always assign the same ip to this machine so DHCP at this point is redundant anyhow.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • These features described above are good, but far from what developers like me was eager to get. And that main feature that developers will love it`s the ability to connect to LOCAL AI models running on Ollama. So if you have a beefy spec machine you can now use your own model 100% local inside Visual Studio 2026 18.7.0
    • Microsoft Teams is getting a controversial location tracking feature that users may hate by Usama Jawad Image generated with Microsoft Copilot Earlier this year, Microsoft planned to roll out a controversial location tracking feature in Teams, but following customer feedback, it decided to delay its release. The bad news is that the company has decided to launch it later this year, but it's based on roughly the same design that was shared earlier, which means that many users still have good reason to worry. Basically, Microsoft Places and Teams have received workplace check-ins via Wi-Fi. The idea is that if an employee arrives at the office and connects to their enterprise network, their profile status indicator will show them as being present in the office. For example, if you arrive at work, open Teams on your PC, and connect to the "Studio B" company Wi-Fi network, your Teams profile will indicate that you are present in "Studio B", as shown below: Microsoft says that this feature is basically a replacement for physical workplace check-in peripherals, it reduces the need to manually update your status, and it also enables co-workers to know that you're at work so that they can coordinate in-person meetings with you. IT admins can enable this workplace check-in capability at a tenant level, and users have the ability to control whether they want to enable it or not. Of course, all of that sounds great on paper, but naturally, many Teams customers may still have concerns, as they did before. This is because it enables your reporting manager and other members of the organization to track if you are at the office, when you arrive at the office, and where you are right now. This could be problematic for people who work in what they consider to be flexible work environments or hybrid setups, and this kind of location tracking could be considered an invasion of privacy. Microsoft has tried to alleviate some of these concerns by letting users know that they can manually set their location easily, which essentially overrides workplace check-in if they feel uncomfortable with it. However, that doesn't really solve the problem because your organization could enforce a workplace policy that mandates that this feature remains enabled. The Redmond tech giant has also assured users that this capability does not store historical data and is only a real-time indicator of location. Finally, it only generates a signal when you connect to a corporate network, which means that if you are working from home and connect your PC to your personal Wi-Fi, it won't broadcast your location to your employer; you will simply be shown as "Remote". Microsoft has encouraged IT admins to prepare for this change and begin informing users so they know what to expect once it begins rolling out later this year.
    • Wow, Microsoft IS cooking lately... This only shows that they COULD improve, they just chose not to for whatever reasons. That obsession with AI was destroying them from the inside out.
  • Recent Achievements

    • Very Popular
      AndrewSteel earned a badge
      Very Popular
    • Veteran
      Taliseian went up a rank
      Veteran
    • One Month Later
      Clizby earned a badge
      One Month Later
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Week One Done
      Timaximus earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      511
    2. 2
      +Edouard
      162
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      80
  • Tell a friend

    Love Neowin? Tell a friend!