I hate wireless stuff.

[[BTF]adam]

<[BTF]adamo> Laptop has connected to wireless fine for years, no problem. Just got the desktop downstairs back from a family friend putting a new PSU in but now it won't even see the wireless network, it is only 2-3ft from the laptop that finds it instantly. whats the deal!

any ideas?

i haven't tried resetting the router (idk why it would or wouldnt work, but when in doubt - always restart!) or physically moving the box to where the laptop is right now (despite it only being spitting distance away) just to rule out signal issues. I know the card works and its a pretty decent one, D-Link something or other. it keeps picking up our neighbors wireless sporadically so it can definitely _see_ networks, just not ours :/

[ReCycled]

Is it Windows 7? I went thru hell trying to simply network my laptop and desk computer together. Eventually I partially succeeded. But it will still block me here and there for no reason. Never had these issues with previous OS's - even Vista was fine.
 

[QuakeDuke]

Did they muck about in the services and turn off wlan  (or similar depending on version of windoze) where it no longer looks for wireless?  Does networking work if you "hard wire it?"

[VaeVictis]

i have the same thing with a vista machine :/ moved it around, tried two dif nic's... the network shows up with full strength signal and then drops off the map randomly... laptop works at full signal 100% of the time 2 feet from the tower having problems

was hoping i could figure out a cause/solution when i go for my cwts cert, but if some one has one here it would be sooner and more convenient

[[BTF]adam]

Windows XP. I am not sure QD, as far as I know, no. I did a windows zero config check and the service is running fine. I am not sure about the wired situation, it would be difficult to test because the router is a floor above and I don't have an ethernet long enough but I am certain that at the person who put this PSU in's house, it connected to their wireless network fine.

[VaeVictis]

winxp will drop your prefered network for another one if you have ssid broadcasting disabled on your wap

[[BTF]adam]

ssid broadcasting is enabled.
 
I have tried the following since yesterday:

moved pc and router closer together - nothing
tried setting up the specifics of the network in a preferred network - nothing
made sure the nic settings match the router setting - were fine
ensured the windows zero config and event log were both running in services - both are


next on the list I guess is uninstalling and reinstalling the device drivers, and failing that reinstalling windows. (it's a new install, I didn't do it and I vaguely recall settings being configured when the d-link drivers were installed, if this guy used the wrong ones and its mucked something up internally or something, i don't know. what I do know is before this pc's powersupply died, it had a version of tinyXP on and was connecting to the wireless network completely fine, now with a new install of windows its not.

[QuakeDuke]

ssid broadcasting is enabled.
 
I have tried the following since yesterday:

moved pc and router closer together - nothing
tried setting up the specifics of the network in a preferred network - nothing
made sure the nic settings match the router setting - were fine
ensured the windows zero config and event log were both running in services - both are


next on the list I guess is uninstalling and reinstalling the device drivers, and failing that reinstalling windows. (it's a new install, I didn't do it and I vaguely recall settings being configured when the d-link drivers were installed, if this guy used the wrong ones and its mucked something up internally or something, i don't know. what I do know is before this pc's powersupply died, it had a version of tinyXP on and was connecting to the wireless network completely fine, now with a new install of windows its not.

It's possible the nic was fried when the PS died.  I would think that would really be the only option left if a driver refresh doesn't change the scenario.

[[BTF]adam]

yeah driver uninstall/reinstall did nothing.


I'm just gonna reinstall windows, it usually fixes things and there is practically nothing on this install anyways, there are all sorts of funky driver files and whatnot that shouldnt really be on so.. who knows whats up with that.

as for the fried nic, would that still be possible* despite the fact it's picking up our neighbors network fine, and I can legit connect to it, I just dont have their wpa key of course

[QuakeDuke]

as for the fried nic, would that still be possibel despite the fact it's picking up our neighbors network fine, and I can legit connect to it, I just dont have their wpa key of course

Ack! My Bad.... I missed that part.. .doh!

[VaeVictis]

its probably just some stupid windows service fucking stuff up...

[[BTF]adam]

update: turns out it wasnt a fresh install, well it was, but it was on a diff hard drive this guy put in and I neglected to check the innards (why would I?) so my old install was in there, just not connected up. connected that and wireless worked like a charm as soon as I booted up, so something definitely went wrong with the new install/configuring it for his network