Cant connect to networks after tethering !!!

[BD20]

Hi guys, I have an unusual problem. I have a Toshiba A305D running windows 7 enterprise, and I tethered my phone last night and was able to connect to the net via my phone. However now I am unable to connect to either of my previous 2 networks. For some reason I can now only connect to my phone tethering. The networks show up as usual but when I try to connect it says unable to connect. When I try and diagnose the problem it does not show a problem, or cant find a solution.

Strange thing is my wife has a Compaq Presario with the same os and it does the same on hers now also. Neither computers are able to connect to connect to either of our old networks, only to the phone via tethering.

I have searched high and low for solutions but cant find any. Any help would be greatly appreciated...

Thanks in advance..

 

[chev65]

Resetting your router comes to mind...and use DHCP because it makes it easier to connect.

 

[BD20]

Resetting your router comes to mind...and use DHCP because it makes it easier to connect.

Resetting the Router did not work. How do I use DHCP??

 

[kegobeer]

Unless you configured your computers with a static IP, you are already using DHCP. Don't worry about that - nothing in your previous post leads me to believe you've made any changes like that.

Can you post a screenshot or two of the networks that appear and the error you get when you try to connect?

 

[chev65]

Interesting analogy, although if he was using DHCP then why didn't those machines reconnect after resetting the router in the first place? I would also make sure that DHCP hasn't been changed on the network connection properites of both machines. I doubt if you changed them but something messed up the automatic connection and that would point to a DHCP problem.

And to that end why would connecting a phone to a router destroy the connection?

 

[stpbby]

go to the start menu type cmd , hit enter.
type ipconfig/release
ipconfig/renew

take a screen shot and post it.

also you can try this:

disable your wireless connection then re-enable it.

control panel -> Network and sharing Center -> change adapter settings -> right click and disable, the right click and enable.

 

[BD20]

go to the start menu type cmd , hit enter.
type ipconfig/release
ipconfig/renew

take a screen shot and post it.

also you can try this:

disable your wireless connection then re-enable it.

control panel -> Network and sharing Center -> change adapter settings -> right click and disable, the right click and enable.

Thanks for everyones input.

I tried both of these and still no luck connecting to my old networks. I can still connect to my phone when its tethering a wifi signal, but no netoworks.

Basically it just says unable to connect

How do I check these DHCP settings??

 

[BD20]

And to that end why would connecting a phone to a router destroy the connection?

My thoughts to. You know I got so frustrated I formated my laptop and re-installed Win 7 thinking in theory this should reset everything but I still cant connect to anything other then my phone tethering a wifi signal, or tethering via usb.

 

[chev65]

In which case resetting the modem and router should fix this problem. Back to square one with this but at least you narrowed the problem down to the router or modem.

 

[redrage19]

I have the same problem

I just moved house and chose to switch broadband provider, so have been left with no internet for a couple of weeks. I opted to tether my phone to get online as well as going back to my parents and using the old network in the meantime. However since tethering the phone, I cannot connect wirelessly to the old network.

troubleshooting brings up an error reading...

Problem with wireless adapter or access point.


I have tried switching off the router for ten mins, but that didn't work.

I tried a system restore to before I tethered the phone, that hasn't worked.

I reinstalled the driver for my Atheros AR9285, that hasn't helped either.


Can anyone suggest something else to try? I am concerned the same issue will come up when I try to connect to the new network when I eventually get it installed at the new property.