Frustrating Windows 7 internet, will not connect

Are you using a 3rd party firewall? If you are, did you make sure the Windows firewall is, indeed, really turned off?

You said you tried different drivers... but i'm not sure which so i'll ask... did you try prior releases of Marvel Yukon Win 7 64bit drivers? (i.e. not the latest ones they list on their website but using earlier releases)

I've tried both drivers on their website currently as well as the updated drivers that windows downloads, as well as the original drivers that came with windows.

And I think I'd know if I had installed another firewall Yes, the windows firewall is definitely off.

Still can't get it to work ;(

Sounds like your stuck with a driver that doesn't work in Win 7 which leaves you with using your wireless card till a decent driver comes out OR! i just had a thought

Does your CPU support virtualization?? I just got Win 7 installed yesterday and Virtual XP installed myself today so i don't yet have any "hands-on" experience or any idea how well this might work or how doable.. But I wonder if you can run the network adapter within a virtual XP environment??

I did just find this link as an example

"Public Network" can prevent certain things from working over a network like broadcast servers such as file/printer sharing, but it won't keep you from getting an IP address. So it isn't that.

Forget about wireless at the moment and let's get your actual wired NIC working.

Connecting doesn't necessarily mean you are getting a real, DHCP IP address. You may be getting an APIPA or nothing at all with your wireless. I wasn't sure if you cleared this up or not in the thread, but I'm going to assume you can't get an IP address with your wifi card either... in Windows.

The only reason to get an APIPA assigned (automatic private IP address) is if Windows doesn't receive an answer to its DHCP request from the DHCP server on the network (your router). If it works in Ubuntu using the same router, the same NIC and the same network cable, then you have yourself a software problem (Windows, firewalls, drivers, protocols etc..)

This is unlikely to be a driver issue because 1.) I've never seen a bad driver cause an issue where you would still get an APIPA and 2.) If you can get as far as getting an auto private IP, then your NIC is almost certainly installed properly. But, I've learned not to rule the improbable out...

Given this is a fresh install of Windows 7, a software problem doesn't make much sense. But let's entertain some possibilities. Here are a few things I might try:

• Reset your winsock (TCP/IP stack) and restart. The behavior you described is a common symptom of a corrupted/incorrect winsock. I think it is worth a shot.
• Check your TCP/IP settings and make sure everything is 'automatic' on the first TCP/IP panel page.
• Uninstall all firewall and network-specific software, regardless of whether or not it is disabled. Firewalls etc.. install special drivers that allow direct access to your network subsystem and even when the program is off, a misbehaving firewall driver can cause issues like this.

And of course, there is always reinstalling. If it is a fresh install of Windows 7, you probably don't have much to lose and it might save you some headaches. If the problem persists and it continues to work in Ubuntu, then perhaps it really is a driver issue.

Hm, thanks guys, I'll give both the virtualization and the resetting the winsock a try.

Hmm, maybe you're correct about the bad drivers and the APIPA not going together. I can "connect" via the wired nic once in a while, but it seems to be sporadic, and I still don't get internet (wired). As for the wireless card, I do get a valid IP and can surf the internet as normal, but the signal is too low to actually use it reliably from my location.

I haven't installed any other software at all aside from firefox yet, and windows firewall is disabled, so it can't be a third party software issue. It's a fresh install, and ubuntu has worked fine for a while now.

I was thinking it was an addressing thing with it being 64-bit and all, but I don't know...

Hmm, still not working after resetting winsock.

Actually Asus do not support your Model (driver wise) with Windows 7
I suggest Windows update for driver updates, but not much use without network
Mind you, the drivers for your network should have come with Windows 7 anyway (as they are not listed under Vista 64Bit at Asus)

You may be best to purchase a new PCI Network card to mount internally (that is obviously compatible with Windows 7)
I have actually mounted a new network card and then got on the Internet for driver updates, then removed the new card and found everything then works (ie it may just reset something)

Like I mentioned, I don't have room for a PCI card, so that's kind of not an option.

I've tried the drivers that come with windows update, they don't work either. That's the problem..

Look, my best guess is non compatible network hardware to Windows 7
ie Please make room for another $10 PCI Network card (and note: this may be temporary)

Again, I have no room, since I'm using the two pci slots that I do have..

And I thought that if the drivers work for windows vista, they should work for 7? Same kernel for the most part. There ARE drivers for windows 7 provided by Marvell and from windows update....why wouldn't they work? Clearly they are at least supposed to support the nic.

It's not a malware or a virus. It also happens in other OS. I am not sure why though. Usually it happens when you use a router. A few times that it happened to me I did the following:
I reinstalled the drivers for the network adapter.
Than I connected everything. Modem -> router-> PC
Than I restart Plug in the modem ( when using the router I plug it in after the modem is fully on)
Than I enable the network adapter on the PC.
Usually the least I get (when using router is ability to get into the routers admin page).
If the problem is still the same I go into routers admin page and check whether it shows the real IP or the 169.*.*.*. If it shows the real IP but the network adapter shows the 169.*.*. i simply reboot the router and then refresh the ipconfig on adapter through cmd.
That usually works for me.
when it does not i just connect the PC straight into the modem and restart the modem by unplugging and waiting couple of minutes and then starting again following the ipconfig reset on the network adapter.
Hope this helps.

I do have to agree that Win7 has some very strange behavior with networking. I am on the 15MByte/s line, but on win7 I can barely get 3Mbit/s. Tried various tweaks and disabling a lot of stuff and I still get the same. And IPv6 doesn't work at all.

I just had the problem again. This time I was not using the router. I installed a firewall with anti-virus and anti-spyware and the problem showed up as soon as I restarted. I removed the program, but while i was doing that I also checked the windows network diagnose. I did that a couple of times and always noticed that among invalid IP message it also shows trhe missing protocols. I think it's a bug in the Win7 as well as anti-virus/firewall apps (guessing here) always mess with the windows network settings.
If You check in the status of connection you will see that there is no IPv6 connection, but the protocol IS installed (or so it shows). I think that might be causing a problem. Sadly I am no tech so It's all just a guess and a bit of exp here.
I tried restoring the protocols and it says that it does restore them. However a minute later the protocols are gone again.
I did as I've mentioned in the previous post and got my connection back. I am wondering for how long though. I don't think i'll be restarting my PC anytime soon. LOL

Nah, I get it regardless of whether or not I'm connected to my router, and I have never installed any virus scanner/firewall on the OS since it's a clean install.

Have u tried checking here. There are a lot of people with the same issue and a lot of help as well.
http://social.answers.microsoft.com/Forums/en-US/w7network/threads

I just turned off the IPv6 protocol completely and now everything just flies like mad

Yeah, I've tried that. Still doesn't work, even without IPv6. We have completely different problems.

still won't work

Sorry to hear that. My only suggestion would be to get a whole different adapter.Sometimes the built-in cards just aren't up to par.

Same config, same problem

Exactly same config, exactly same problem.

I tryed everything like you without success

The only workaround I found was to switch to version x32 and it works... but loosing 1GB...

And of course, my network cards work perfect with xp, vista, ubuntu... you are not crazy