Windows 7 wireless problems

[dlpmdr]

I have spent the last week setting up 12 new computers for my clients all running windows 7 pro 64 bit. each machine is different... different wireless hardware.. specs, etc. each machine however, cannot stay connected to the 2wire gateway for more than 10 minutes. it will drop the connection saying no internet access (everything is still working fine however, as other machines still have access. the exact same machine running windows xp has no issues). simply resetting windows wireless (disconnecting, reconnecting) puts it right back online. 

i just got back from another clients place who also has uverse... and its the exact same issue. something is happening in windows 7 that is running into problems with this 2wire. anyone have any ideas? 

[dlpmdr]

ok... back from another clients. this is a global issue... im seeing this across the board. just tested with windows 7 32 bit ultimate... same issue. when connecting to the 2wire... it will last around 10-15 minutes, then state "no internet connection" on the win 7 machine. (again... the connection is fine. other machines are still up and running). 

took a few troublshooting steps.... tried hard coding an ip as opposed to pulling dhcp from the router... tried turning off ipv6... neither seemed to have any effect. 

however... if i take the exact same setup, turn off wireless on the 2wire, and add in a third party wireless router.... the issue goes away. so it is definitely something with the 2wire.  

addition: ANOTHER uverse customer i deal with just called... same thing. they upgraded to win 7 on release day, and have been having the issue since then (its the first ive heard of it).  how am i the first person to have this issue? 

[randyl]

Maybe just start over clean ????  dunno  worth  a shot i guess
Close all active applications
Click Start -> Control Panel -> Network Connections
Right click Wireless Network Connection, select Properties, Wireless Connection Properties window appears
Wireless Connection Properties should contain at least three tabs (General, Wireless Network, Advanced)
If Wireless Network is not present do steps below
Close Wireless Connection Properties window
Click Start -> Run, Type: services.msc, click ok
Services window should appear
Scroll all the way down and locate Wireless Zero Configuration
Right click Wireless Zero Configuration, select Properties
Make sure that the start-up type is set to Automatic, change if not
If Wireless Zero Configuration service is started or stopped, re-start or start service
Close Services windows (Wireless Network tab should now be activated)
If Wireless Network tab is present continue below
Click on Wireless Network tab
Make sure that there's a check mark on the "Use Windows to configure my wireless connection automatically"
In the Preferred Networks list, make sure that the box is empty, if not delete all access points found
Just below the Preferred Networks list box, click on the Advanced button, a small window will appear
Select the first option - Automatically connect to preferred networks
Put a check mark on the last line that says - Connect to non-preferred networks
Click close
Click Ok on the Wireless Network Properties
Go back to Control Panel -> click System -> System Properties window will come up
Click on Hardware tab -> click on Device Manager button, Device Manager windows come up
In Device Manager, click on the "+" beside Network Adapters to expand contents
Right click and select un-install the Wireless Network device and confirm removal on the warning window
Close all active windows
Restart laptop/pc
Upon startup, found new hardware will appear
If no, found new hardware appears, the driver has already been installed automatically and should continue with the next steps
Windows should automatically re-install the Wireless Network Device drivers
Upon completion of installation, a pop-up window will appear stating "One or more wireless networks detected, click here for more options"
Click on the balloon to bring up the "Available Wireless Networks Windows"
You should now be able to see all available Wireless Networks in range
Select desired Access Point to connect to then once connected, you should be able to browse the internet with no problems
Also make sure that there are no power settings turned on to put the card to sleep etc

[MyDogHasFleas]

I'm running Windows 7 32-bit on one laptop and 64-bit on another laptop.  Both are working fine on wireless.  I use the 32-bit one on wireless in my home all the time, and have never seen a drop.  So there's no pervasive "Windows 7 doesn't work with U-verse Wireless" issue.

I suspect you have a different problem.  Either wireless interference, or issues with your wireless hardware or drivers in your PC, or maybe possibly a bad RG (but the coincidence of this happening exactly when you switched to Windows 7 would be too high).

You can eliminate interference by running a test with the laptop in the same room as the RG, and see if you still get drops.  If not, you probably have interference.

If I were you, I'd focus on the wireless drivers as the culprit.  Make double certain sure you have the official latest Windows 7 supporting drivers.  Try deleting the device and re-installing it.  Be aware the drivers on Windows Update may be different from the drivers on the manufacturer's website.   

[dlpmdr]

randyl:

thanks for the long list. unfortunately, nothing there made any difference. ive tried everything i can think of here... including formatting and reinstalling a few of the machines.

mydoghasfleas:

i wouldnt think it would be a universal issue... but the evidence to point to that is just too great. i now have a total of 18 windows 7 machines... on 5 different uverse accounts in austin and houston.... ALL of them are having the issue.. and ALL of them had no issue prior to the move to windows 7. as stated before... these are all different machines.. different hardware. if i couldnt take each of these machines, and put them on some other wireless network without problems... i would say you are correct. but, i can. the moment i take the machines that have these issues, and put them on a different wireless router... the problems disappear. 

i called yesterday and talked with level 2 tech support... we are starting to think that it is the 2wire gateway. windows 7 has  increased the number of tcp connections. those increased connections appear to be overwhelming the 2wire which drops that wireless connection. they have tested this a little, and stated that there is nothing that can be done with the 2wire at this moment... and are offering me a third party (dlink) wireless router to use. obviously, i dont want to run around setting up yet another wireless router to for each on of my clients... 

[randyl]

http://gateway.2wire.net/xslt?PAGE=J14&THISPAGE=J15&NEXTPAGE=J14

NAT Sessions

current secs since boot: 618383
session table 908/1024 available, 0/512 used in inbound sessions:
sess[51254]: bkt 13, flags: 0x000001a1, proto: 6, cnt: 7

win 7 opens 10 ???

[dlpmdr]

week #3.... and the body count is still stacking up. i have only seen ONE windows 7 system on a uverse connection now that did not have any issues. the only difference between all the others: this system was all by itself on the network. there had never been any other systems connected to the 2wire. 

ive kept count: 73 total windows 7 machines (both 32 and 64 bit... varying versions, home premium and pro, and a few ultimates)  on uverse connections, none are able to stay connected. att needs to get this fixed asap.

Message Edited by dlpmdr on 12-03-2009 11:42 AM

[mikhmln]

---

MyDogHasFleas wrote:

I'm running Windows 7 32-bit on one laptop and 64-bit on another laptop.  Both are working fine on wireless.  I use the 32-bit one on wireless in my home all the time, and have never seen a drop.  So there's no pervasive "Windows 7 doesn't work with U-verse Wireless" issue.

I suspect you have a different problem.  Either wireless interference, or issues with your wireless hardware or drivers in your PC, or maybe possibly a bad RG (but the coincidence of this happening exactly when you switched to Windows 7 would be too high).

You can eliminate interference by running a test with the laptop in the same room as the RG, and see if you still get drops.  If not, you probably have interference.

If I were you, I'd focus on the wireless drivers as the culprit.  Make double certain sure you have the official latest Windows 7 supporting drivers.  Try deleting the device and re-installing it.  Be aware the drivers on Windows Update may be different from the drivers on the manufacturer's website.   

---

2 64 bit win 7 laptops, and 1 32 bit win 7 laptop, no problems.  Had a desktop 32 bit win 7 on wireless with no issues at one point, now have it hard wired.

[SomeJoe7777 ACE - Geek]

---

dlpmdr wrote:

week #3.... and the body count is still stacking up. i have only seen ONE windows 7 system on a uverse connection now that did not have any issues. the only difference between all the others: this system was all by itself on the network. there had never been any other systems connected to the 2wire. 

ive kept count: 73 total windows 7 machines (both 32 and 64 bit... varying versions, home premium and pro, and a few ultimates)  on uverse connections, none are able to stay connected. att needs to get this fixed asap.

---

Sorry, but I have to disagree.

I currently have one Win 7 32-bit system at home, and a second Win 7 x64 system at home on the same network, along with 3 Windows XP systems, and one Windows Server 2003 R2 (32-bit).  All are working perfectly.

Two of the Windows XP systems are wireless (through a 3rd-party wireless access point, the RG's wireless is turned off), the rest of the systems are on wired Ethernet.

[bsdsmb]

Not sure if any progress is being made on this thread.  I've not had trouble with my win7, but I'm not really using the RG wireless much either. 

But ... this sounds much like a security key timeout / reset issue.  Double check that the WPA / WEP security settings are all correct between the RG and the various clients. 

[jrinjax]

My new HP touchsmart 300-1020 will not connect to the RG by wired connection, the adapter can not see the RG and says the cable is disconnected. HP and AT&T have not been able to solve the problem. The wired LAN will connect to any other network OK, just not to AT&T.

[jrprice]

Same problem here.

Have one XP box and one Win7 box. The XP box has no issues (beyond the usual wireless hiccups that occur) but the Win7 box is unable to maintain a stable connection for any period of time.  I can usually get it restored with a lot of fiddling, but it will invariably fail again.

I'm running Win7 Ultimate 64 bit with an Atheros 5005GS (yes, latest drivers) adapter.  I believe the issue is with the 2WIRE box since the XP machine does connect and hold, and I can connect to another 'available' wireless router plucked out of the air that is NOT 2WIRE (and not secured) using 802.11N (the 2WIRE box is using G).

All this points to the 2WIRE POS.  Checked it and it tells me that it is 'up to date'.

Also, once I DO get connected the 'fail' is always preceded by a 'DNS Client Event' 1014:  

Name resolution for the name xx.xxx.xxx timed out after none of the configured DNS servers responded.

The xx.xxx.xxx varies from error occurence to error occurence.

Any thoughts?

I've tried just about everything, including uninstalling/reinstalling the adapter, starting 'fresh', using OpenDNS, turning off IP6, using every gyration of ipconfig I can think of, and standing on my head while patting my stomach.  Nothing works as an 'a-ha!'. 

[jrinjax]

I still have intermittant problems with the 7-64 bit machine dropping the connection [due to DNS issues] whether wired or wireless. I had to repull the cable [to a 6E] and buy a LAN diagnostic checker since the XP machines would work and the 7-64 would have connect issues. I am hoping that AT&T and MS will work this out.

[jrprice]

Same 'symptoms' I'm seeing.  Got an XP box (wireless) working just fine.  It's the Win7 64-bit box that drops the connection due to 1014 DNS 'issues'.

So how do we bring the appropriate 'focus' to AT&T and Microsoft to figure out what is going on?  Is it really MS issue or is it 2WIRE?  Would seem that AT&T should have sufficient clout with 2WIRE to work that angle, but are they doing ANYTHING?

[iain]

I'm seeing several threads on other forums that say that Windows 7 doesn't play well with WPA2. IIRC, the RG defaults to WPA2 / TKIP.

There are actually sickeningly few devices that do work with WPA2 and/or AES - a Linksys router and brand new Linksys access point, both with the latest firmware, both with WPA2 support, refuse to communicate using anything other than WPA/TKIP, not WPA/AES or WPA2/anything.

Try backing off to WPA/TKIP and see if that's the issue. If so, wait for the inevitable Windows 7 update to fix this, which may happen sometime after WPA2 has been hacked.

[jimmyone]

---

jrprice wrote:

Same 'symptoms' I'm seeing.  Got an XP box (wireless) working just fine.  It's the Win7 64-bit box that drops the connection due to 1014 DNS 'issues'.

So how do we bring the appropriate 'focus' to AT&T and Microsoft to figure out what is going on?  Is it really MS issue or is it 2WIRE?  Would seem that AT&T should have sufficient clout with 2WIRE to work that angle, but are they doing ANYTHING?

---

 We have 2 HP computers one laptop, one desktop both are running Windows7 64 bit. One laptop running Vista 32 and one laptop running Vista 64. The OP stated the problem was with Windows7 64 bit wireless systems. If correct that removes my desktop and everything except the new laptop because the desktop is hard wired. I have not seen the problem.  I'll check with my wife when she gets home the new laptop runng win7 64 is her's and see if I can duplicate the problem. I seriously doubt she is having the issue as she often works from the laptop for hours nightly then spends a great deal of time online with friends. It would be interesting to see what the systems involved have in common?

[MyDogHasFleas]

I'm running the RG with WPA2/AES.  I just got a new laptop on Win 7 64-bit and gave the old one to my daughter in another town.  Zero problems connecting and staying connected over wireless.  So that's 3 separate laptops now on Windows 7 that I have had zero problems with.  Two on 64-bit, one on 32-bit.  

My daughter also has U-verse up in Dallas and the Windows 7 laptop I gave her connects flawlessly up there too.  (She's on WEP/40-bit and refuses to let me upgrade her security.... that's another story.  I have no idea where she got this stubborn streak from.   )

I think if there were some "pervasive" problem with Windows 7 wireless connections to U-verse, you'd be seeing all h**l breaking loose on the InterWebs.  Since we don't, I can only assume that these issues people are having in this thread are very isolated cases.  

[jrprice]

Interesting...

Opened up a free basic account with OpenDNS (www.opendns.com) and am using their DNS servers (manual DNS config set on IP properties).  No issues so far (the dreaded 1014s) and it has been several hours since the switch with no errors, no drops.  So, if that's the case, I'm wondering about the DNS boxes being used by ATT since most of the reported errors I'd get were along the lines of 'Name resolution for the name xxx.xxx.xxxx timed out after none of the configured DNS servers responded.'

I'll keep an eye on it...

[jrprice]

---

MyDogHasFleas wrote:

I think if there were some "pervasive" problem with Windows 7 wireless connections to U-verse, you'd be seeing all h**l breaking loose on the InterWebs.  Since we don't, I can only assume that these issues people are having in this thread are very isolated cases.  

---

You spent any time on the Microsoft tech forums?  There are more discussion/threads there about Win7 connectivity issues/problems than you can count.  Is it 'all hell breaking loose'?  Maybe not, but it ain't isolated, homey.

[jrprice]

---

jrprice wrote:

Interesting...

Opened up a free basic account with OpenDNS (www.opendns.com) and am using their DNS servers (manual DNS config set on IP properties).  No issues so far (the dreaded 1014s) and it has been several hours since the switch with no errors, no drops.  So, if that's the case, I'm wondering about the DNS boxes being used by ATT since most of the reported errors I'd get were along the lines of 'Name resolution for the name xxx.xxx.xxxx timed out after none of the configured DNS servers responded.'

I'll keep an eye on it...

---

Well, still seeing the 1014s from time to time, and the occasional drop, but nothing on the scale as before.  Weird.

[MyDogHasFleas]

---

jrprice wrote:

---

MyDogHasFleas wrote:

I think if there were some "pervasive" problem with Windows 7 wireless connections to U-verse, you'd be seeing all h**l breaking loose on the InterWebs.  Since we don't, I can only assume that these issues people are having in this thread are very isolated cases.  

---

You spent any time on the Microsoft tech forums?  There are more discussion/threads there about Win7 connectivity issues/problems than you can count.  Is it 'all hell breaking loose'?  Maybe not, but it ain't isolated, homey.

---

I maintain there is no "pervasive issue".  I looked at the Windows 7 forums, I found this issue which has to do with power save mode:

http://support.microsoft.com/kb/928152

Enabling connections to a network can be tricky especially since people have all kinds of network environments, adapters, drivers, etc.  It's not surprising that people have problems.  But to say that "Windows 7 wireless networking is broken" is just wrong.  

[click_clack]

I have an HP laptop 64bit running on Windows 7 purchased last October.  I'm running it wirelessly to my 2Wire RG and have not had one connectivity problem (other than my wife hitting a button which disables the wirelss card.)

She can even print on my HP wireless network printer running through th RG (had to wait until end of January for HP to come out with the driver but once it was available (win 7 compatible driver) no problems there, either.)

Should I knock on wood?

[oufanindallas]

---

click_clack wrote:

I have an HP laptop 64bit running on Windows 7 purchased last October.  I'm running it wirelessly to my 2Wire RG and have not had one connectivity problem (other than my wife hitting a button which disables the wirelss card.)

She can even print on my HP wireless network printer running through th RG (had to wait until end of January for HP to come out with the driver but once it was available (win 7 compatible driver) no problems there, either.)

Should I knock on wood?

---

I have a wireless HP printer that works great on my Windows 7, no problems whatso ever. 

[jimmyone]

---

jrinjax wrote:

My new HP touchsmart 300-1020 will not connect to the RG by wired connection, the adapter can not see the RG and says the cable is disconnected. HP and AT&T have not been able to solve the problem. The wired LAN will connect to any other network OK, just not to AT&T.

---

I agree with MDHF there is no prevasive issue the problem if there is a problem dates back to the Touchsmart running Vista 64 and then being upgraded to Windows 7 64 Bit. There have been MB and HDD issues glore that can be found on the HP forum that are Touchsmart spefic. None, not one of the issues can be or I should say have been traced back to Uverse. I'm all for addressing a problem but we need to ID the problem before suggesting a solution. IMO a lot of the problems are due to The HP Windows 7 64 bit upgrade where users fall to follow instruction. They then run over to the Windows 7 forum where they are instructed to do a clean install instead of following the instructions you receive with the upgrade kit. Remember half of the people making suggestions did not have the upgrade kit and most of the others did not have HP Systems. That was in November when I pointed this out.  I was also shocked to find some of the issues were the result of people using the Windows 7 beta trying to install the 120 day trail over it. Bottomline if you actually have a HP system that is not working properly with Windows 7 64 bit you are not going to find a solution anywhere but at the HP Forum or from a HP REP.

[jrinjax]

Your theory has a slight hole in it on my case. My Touchsmart came with Windows 7 64 on it from the factory. HP and AT&T each spent a half day of trying to trouble shoot it. Both finally gave up and did not call back. I ended up pulling a new CAT6E cable to replace the one that still worked fine on XP to get the wired connection working so I would not have all of the wireless issues that I don't have on my XP notebooks.

I have no idea of what everyone else's problems are but am sure of what I experienced....

[jimmyone]

---

jrinjax wrote:

Your theory has a slight hole in it on my case. My Touchsmart came with Windows 7 64 on it from the factory. HP and AT&T each spent a half day of trying to trouble shoot it. Both finally gave up and did not call back. I ended up pulling a new CAT6E cable to replace the one that still worked fine on XP to get the wired connection working so I would not have all of the wireless issues that I don't have on my XP notebooks.

I have no idea of what everyone else's problems are but am sure of what I experienced....

---

 You may be be correct seeing as I am capable of being wrong from time to time. However it is also possible the topic that's being addressed here is addressed on the HP forum In this thread and others  Far be it from me to suggest this is not a Uverse issue rather a Windows 7 issue if it is an issue. Again there is no imperial data as in no data on the Windows 7 Forum or the HP Forum that indicates in any small way what you are stating has a close relationship to the truth as it relates to the Uverse RG. There is a simple solution HP is well known for, continue to call and force a buy back. In short they have to give you a system that works or return your money. You would not be the first Touchsmart owner with multiple issues.

[jrinjax]

Thanks for the advice, but it is my Wife's "personal e-mail getter" so after I repulled the cable, I have kind of ignored the other issues with it. She did mention she did not like it as much as her office XP desktop. As long as she continues to use it I am not going to bother with it since I have yearly boat and jet ski issues to solve before our vacations.

[jushowi]

If you have a Dell computer try changing the driver for the wireless card to the Microsoft one instead of the Dell one.  

Start -> Control Panel -> Network and Internet -> Network Connections

Right click the wireless card then click properties

Click the configure button

Click the Driver tab

Click the Update Driver button

Click Browse my computer...

Click Let me pick...

Click the wireless driver that reads (Microsoft) at the end

Click Next

Click Close when it's done

Try to connect to your 2wire.  This worked for me.

[rdiaz]

Jushowi,

Thank you so much for your tip!  I could see my 2wire network but could not connect with Win7 until I did what you suggested.

THANKS!

[oz_1 ACE - Wizard]

My HP G42 running Win7 seems to connect fine with WPA2 since thats the only encryption I use for several years now but i do use an Airport Extreme and not the wireless in the RG. The one thing I never use is auto channel since they never work well

especially in heavy traffic so try 1,6 or 11.