Windows 7 on wired computer prevents wireless connections to router

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Status
Not open for further replies.

r@minder

Distinguished
Mar 29, 2008
1
0
18,510
Hello.

I own three computers. One has a wired connection to my wireless router (Linksys WRT54G v. 6 with latest firmware), the other two use wireless adapters and are running Windows XP Professional 32-Bit. If I run Windows 7 Ultimate 64-Bit on the computer with the wired connection, the other two computers cannot connect to the router (access point). Here's what's troubling.

If I leave the other two "wireless" computers turned off, and run Windows 7 on the "wired" computer, then turn off the "wired" computer, and turn on one or both of the "wireless" computers, they still cannot connect.

In order to establish a wireless connection, once again, I must reset the router , then reset the security, and finally, enter the new network key on each of the "wireless" computers. It doesn't matter whether the "wireless" computers are on or off when I either install or run Windows 7 on the "wired" computer. The problem occurs even when I turn off the "wired" computer before turning on the "wireless" computers.

At this point, I can only "assume" (either from lack of knowledge or imagination) Windows 7 actually makes changes to the router's settings. I cannot access the router's web-based utility from Windows 7 or from Windows Vista. I must access it from Windows XP (I quad boot XP, Vista, Windows 7, and Ubuntu). My problem with wireless networking only occurs with Windows 7 Ultimate 64-Bit. I don't experience this problem with Vista Ultimate 64-Bit. Also, I have no networking issues with Windows 7 running on the "wired" computer.

Perhaps there is a simple solution. However, it's disconcerting that Windows 7 can prevent other computers from connecting to my router. Windows 7 should only be concerned with connections made to the computer it is running on, and not take over the responsibility of the router. If this is the case, then I find that to be completely unacceptable. I'm not using the wired computer as a gateway for the other computers. The Linksys router is the default gateway. Furthermore, I'm absolutely not interested in sharing music or files through Home Group, since this feature of Windows 7 is only compatible with other computers running Windows 7, and I'm not about to replace XP on the "wireless" computers with a beta version of Windows 7. I suspect Home Group might be the culprit here, or the reach of Windows Firewall is now out of bounds.

If you know or have an idea of what might be the problem, please let me know. I'll have to leave Windows 7 alone until I find a solution, as I'm not going to go through the hassle of reseting the router and network keys every time I run Windows 7. Unplugging the computer from the router is an option, but to do so would cripple the OS and the fun of using it. Besides, the beta needs access to the Internet for updates and to report problems.
 


The network key is essentially a password you create when you set up the wireless network. It is saved (encrypted) in your router / hub whatever thingy so when you try to connect any new computer to the same wireless network, you have to enter that "key" into that computer so it can connect. It basically stops your neighbours from using your download limit for free.
 
I have 1 wired win 7 x32 pc, 1 vista laptop (wireless) and 1 win 7 x32 (wireless) pc on witch i have linksys usb adapter (wusb54gc v2).
Problem is with 3rd pc (using usb adapter). Laptop and wired pc are connected to the internet with no probs, but 3rd one cannot. I see my network but key doesnt seem to work. Which only makes me belive that 4 hours of searching for right drivers for that usb adapter pay up and i got right one.
"Windows was not able to connect to network name".
I tryed to remove homegroup - didnt help.
Windows firewall isnt running.

bah...dont know what to do anymore. Laptop and wired pc dont seem to "fight" over network and they work just fine.
:cry: :cry:
 
I was having the same issue with wifi dropping on my Vista and Win7 computers (not XP though). I didn't think it was a firmware issue since the Linksys site listed their patches and none for my router called out specifics for the two troubled OS.

After several months, I landed on a Vista forum where it read that Vista had issues with TCP/IPv6 (and also Win7) which so far has kept my two machines connecting for the last week without me having to reset the wifi..

HISTORY
Both my eMachine (Win7) and my Toshiba (Vista) kept knocking out the wifi connection or I had to restart the router half the time I turned them on. All machines running XP (desktop and netbook) connected fine without issue.

The Linksys router is fine (I didn't update to the latest and greatest firmware, but reading the update it didn't have anything substatial...I don't like update firmware unless it's crucial since I've read to many reports where the firmware updates turn hardware into bricks when they were running fine before).

After several months of research online I narrowed the issue with Vista/Win7 and not the router or Broadcom/Atheros cards. Seems Vista and Win 7 had issues with the TCP/IPv6 that interrupts connections.

I unchecked the TCP/IPv6 on the eMachines and have not had a dropped wifi connection or needed router rebooting. So far so good, so try to go to your "Change adapter settings" and uncheck the IPv6 box to see if that helps.
 
My ZyXEL NBG334W router has been rock solid for months. I hooked up a new win7-64 machine and noticed every time I awoke it after a sleep my router rebooted. Tonight I noticed the same thing is happening when I boot the win7-64 machine anew.

After reading this thread I removed the win7-64 machine from HomeGroup and have so far been able to go through a sleep/wake session without the router rebooting. My network is only made up of two xp-32 machines, the win7-64 machine, the router, a few devices and a switch - so the win7-64 machine is the only one capable of using HomeGroup anyway.

I dunno if HomeGroup causes the problem or, as posted before, it may be that the underlying issue is the router's incompatibility with ipv6, which HomeGroup uses. But though I might be jumping for a joy a little early, after a single test, I just wanted to note my success story and post a thank you for those who have posted in this thread.
 
It is sooooo dumn frustrating!!!


I'm using a desktop running Win 7 x64
When I stream to the linksys DMA-2200, it drops out every 10-15 mins! I know its not the router, extender or how far they're apart! When it happens I always have to disable, enable the NIC then it works.

I have disabled power management of all sorts, unchecked TCP/IPv6, updated drivers of the NIC and my NVIDIA Graphics card, that's all I could think of and have read from people having the same issue.

If you could suggest other ideas or or have recommendations I'd very much appreciate it! Please HELP!
 


It's THE HOMEGROUP, turn off the home group that was automatically setup when you ran Windows 7 for time Start, Contol Panel, Network and Sharing, Homegoup... Windows 7 has a redundant file sharing function. The first is the one we are all used to MSHOME, WORKGROUP, etc... and THEN there's Homegroup a networking for dummies feature for all family Windows 7 users to share media. Turn it off, reboot and that ?"Should"? do it for you. I've found that there are two programs "PlayOn" and a free one called vcm playit. Yopu get two weeks free of Playon but you'll immediately see it's worth within 2 days. And then, on this page:

http://windowsmediacenter.blogspot.com/search?updated-min=2010-01-01T00%3A00%3A00-08%3A00&updated-max=2011-01-01T00%3A00%3A00-08%3A00&max-results=7


scrolling way down, past the issue of the box of the day they are working on, you'll find all the downloads, it's a Microsoft Blog.

Hope this helps
 



Have you verified that your router is compatible with Windows 7? Have you attempted to swap the router out as an attempt to troubleshoot?

Jessica
Microsoft Windows Client Team
 
Hi folks -- Had a similar problem and was able to fix the issue. Here are the quick details:

Run a home network which consistes of 3 XP laptops (one wired and two wireless), wireless printer, and wireless TiVo connection. Introduced a fourth laptop Windows 7. For some reason, it brought down the whole network (Linksys WRT54G router). When I removed the Windows 7 machine, it worked again.

Updated the firmware on the router which did the trick.
I have an Hp laptop and am runnning of the same router as you and we have reset several times and I can't connect to the internet wirelessly. The 2 other computer are wired and are running on xp and are working fine. I just don't know what to do to get my wireless connection.
 


ok I finally found the damn cause!
Someone in another forum told me to turn OFF the TASK OFFLEAD option in the Network card's settings...

Control Panel\Network and Internet\Network Connections

right click Local area connection, click properties.
Click Configure.
Go to Advanced tab
turn OFF Task Offload.

Like I said that how worked wonderfully for me and my NIC isn't disconnecting every 10-20 mins from the extender...
Good luck guys
 
OK, so I've spent a ridiculous amount of the past couple of days trying to accomplish the seemingly simple task of adding two new wireless laptops with Win7 to a perfectly happy and functioning network of 3 wired pc's running xp. About a month ago, a wireless router was added to the XP system and has been working just fine.

I've tried a variety of things, and they won't see each other. Then, to my surprise, suddenly I was having all kinds of problems with the existing network. I would fix them, reboot, blah blah--they're fine. Go back to other tasks, and next thing I know, "there is a problem with the mshome network..." Arghh. When I left, one of the 3 could no longer connect to the internet. I thought I was losing my mind.

I googled and found this thread. THANK YOU ALL. This was huge! I now have a much better idea what to look for, and what others have found happen. I will return there at zero dark thirty with little sleep but at least armed with a slough of ideas. I'll let you know how it all turns out. I'm starting with turning off homegroup. Thanks again,

Paula
 
k i've done alot of research on this and its cause some routers arn't able to handle win 7 correctly yet and there still isn't an update for the problem yet to this day... i check everyday cause i have a problem with this to we have 4 wired pcs 1 with win 7 2 wit xp and 1 wit vista and actually 2 ps3s a wii and we do have a laptop wit xp on it... now we didnt have any problem with our router til we put the new compute wit win 7 on it after that videos wont load and other computers get disconnected much like ur problem, which i managed to fix by making all the routes static, it might be the bandwidth but i doubt it cause the new computer just replaced an old one. so dat problem is unsolved still lol oh yeah and if you have wireless on two of em and one lan then you might need to set an ip for the wireless computers cause there might just be an ip problem cause wen a wireless disconnects it loses there ip and gets a new one which might be a problem...
 
I have a machine with Win7 which I simply call "SERVER" although it is not. It serves the storage center purpose, plus 2 printers are shared from it--hence the name. The 2 printers are an Epson Stylus R200 Photo Printer (my favorite), and a Lexmark all-in-one X7170 a few years old but treated well. Since replacing the "server" and all the "clients" with Win7, I can not get either printer to behave properly. I have searched (and searched) for updated downloads, tried installing them to no avail. I truly think that Windoze has another MAJOR blunder on their hands. Win7 is great! LET'S GET SOME UPDATED DRIVERS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 
FireWalls .... Norton /mcafee anything with a firewall other than Windows Get rid of it period. windows has its own since XP, norton is a bitch you have to configure File sharing with in norton software... if you want to use it by all means spend a few hours learning your software that you bought. and keep it otherwise stop bitching and get rid of it... its no good to home users... business i will adapt but many problems have occurred with norton since 2004 IS.. also Workgroups, make sure everything is on the same workgroup. it is very unlikely that a Win OS will bring down the network..come on a apple computer can talk on the same network that runs windows... you think windows 7 caused your problems amongst other windows OS's. get real... the first step to your problem would be to power cycle and understand Dynamic ip address, if you are not on a static network, Dynamic ip address assign a number to each computer (first come first serve)meaning the first computer you turn on to your home network the router will assign that computer a ip address or number and so with the 2nd and 3rd 4th a priter and so on and so forth. File and print sharing will have to follow as there are many issues with FnP sharing with xp and vista alone you have to turn on Public discovery i would refer to microsoft.com for most answers and Google. is your best friend...otherwise you need someone from the IT computer certified world that knows computers to solve your problem. good luck

I have to disagree with you so VERY strongly!! I have a Linksys router which is exhibiting these exact same problems. I'm using fixed IP addresses, gateway and DNS, so it's not a dynamic assignment problem. It has only happened since it was connected to a Win 7 m/c. This m/c has certainly has never even sniffed Norton, relies on the router for a firewall (Windows internal one disabled), and has Ipv6 disabled, so only Ipv4 is available, and it STILL causes the router to crash, usually in under 1/2 hour . Turn off the PC, and reset the router and it works on XP machines indefinitely. This is the full release version of Win 7 Pro 64 bit, not a beta, so they still haven't fixed it. BTW my router's already on the latest firmware, so that solution's out.

Thanks for the tips from other users on the thread.

 
Status
Not open for further replies.