|
|
|
|
|
|
Posted: Sat Dec 29, 2012 1:42 pm
I'm back at home but we have no wireless! I need to hook up to the router by cat5 to get on, and that means I need to stay in the living room and can't hide in my bedroom.
|
 |
 |
|
|
|
|
|
|
|
|
Posted: Sat Dec 29, 2012 2:48 pm
Why isn't your router broadcasting? Can you get into its settings?
Fixing things like this is what I did over the phone for a couple years.
|
 |
 |
|
|
|
|
|
|
|
|
|
|
Posted: Sat Dec 29, 2012 2:55 pm
IceBlake Why isn't your router broadcasting? Can you get into its settings?
Fixing things like this is what I did over the phone for a couple years. It's broadcasting but my computer tells me it can't connect. My uncle said there was a firmware issue for OSs prior to win 7 iirc but he's the computer whiz in this situation, not me.
|
 |
 |
|
|
|
|
|
|
|
|
Posted: Sat Dec 29, 2012 3:31 pm
Firmware issue? Hmm. Settings are more likely than firmware to prevent you from connecting.
If it were a firmware issue, you'd just need to correct that on your computer, which would be relatively simple with your CAT5 connection; just google your wifi connector's manufacturer and product number and check your version of firmware vs the most current on the net.
I think it's more likely he has the router issuing IPv6 addresses, with which older OSs can have problems. A firmware upgrade could fix this, but so could changing the router to broadcast in IPv4.
|
 |
 |
|
|
|
|
|
|
|
|
|
|
Posted: Sun Dec 30, 2012 12:14 pm
IceBlake Firmware issue? Hmm. Settings are more likely than firmware to prevent you from connecting.
If it were a firmware issue, you'd just need to correct that on your computer, which would be relatively simple with your CAT5 connection; just google your wifi connector's manufacturer and product number and check your version of firmware vs the most current on the net.
I think it's more likely he has the router issuing IPv6 addresses, with which older OSs can have problems. A firmware upgrade could fix this, but so could changing the router to broadcast in IPv4. You're probably right. I'm only stuck with this situation for a week so I'm not going to fiddle with it, but if it were my network I'd be poking around.
|
 |
 |
|
|
|
|
|
|
 |
|
|
|
|
|