Help...

Executioner · Post by **Executioner** » Tue May 01, 2012 8:10 pm

I worked on a PC laptop and got it all cleaned up. It had some Trojans etc. Did not have an issue connecting to my wireless router or Ethernet connection at home. Give the laptop back to the gal and she has no issues at home connecting. She brings it to her place of work and it won't connect to the internet, even though it finds the wireless router and connects.

I've spent over an hour on all the settings etc, and it simply won't connect. It has that red X in the center of the connection. Hard to trouble shoot if you can't connect to the internet. Forgot to mention that I tried the Repair option with no luck.

Post by **FlyingPenguin** » Tue May 01, 2012 8:57 pm

Could be something as simple as having to reboot the Wifi router at work. I see this all the time.

There's not likely to be anything wrong with the laptop if it connects to other Wifi access points.

Something else they can try is to delete the work Wifi network from the list of memorized networks and then reconnect to the work network as if for the first time, entering the passphrase and memorizing it.

Executioner · Post by **Executioner** » Tue May 01, 2012 10:59 pm

FlyingPenguin wrote:Could be something as simple as having to reboot the Wifi router at work. I see this all the time.

There's not likely to be anything wrong with the laptop if it connects to other Wifi access points.

Something else they can try is to delete the work Wifi network from the list of memorized networks and then reconnect to the work network as if for the first time, entering the passphrase and memorizing it.

Yeah I did that and the same results. Googling some results, some suggested resetting the winsock with the following command: netsh winsock reset.

Post by **FlyingPenguin** » Wed May 02, 2012 5:23 am

Try these:
netsh winsock reset catalog (reset winsock entries)
netsh int ip reset reset.log hit (reset TCP/IP stack)

eGoCeNTRoNiX · Post by **eGoCeNTRoNiX** » Wed May 02, 2012 8:32 am

I thought that WEP keys were 28 characters long? I'm sure it's just windows shortening it, but something that caught my eye.. Also, make sure to identify the network, that can sometimes cause issues. If it remains un-identified, windows sometimes won't allow it to get on the web.

eGo

Post by **FlyingPenguin** » Wed May 02, 2012 8:54 am

Win7 hides the length of the passphrase.

Another thing to try is configure the IP as static instead of DHCP just to see if it works. If it does, then it's likely a DHCP issue. If it doesn't, there's something deeper going on.

Executioner · Post by **Executioner** » Wed May 02, 2012 9:07 am

OK thanks fellas - I'll give those a shot this afternoon. Googling this issue, lots of users are complaining about this issue, as its more prevalent with Vista.

Executioner · Post by **Executioner** » Thu May 03, 2012 10:46 pm

Well, I tried for an hour to get it to connect and it simply would not - even with a winsock reset. So my only recommendation is a wipe and reinstall of the OS from the recovery partition.
On a side note, she gave me her husband's pc to fix, and I could not believe it. Paint dries on the wall faster than this rig. Its also running Vista, but only 1 gig of ram. It also has some kind of Trojan since I can't adjust the Internet Options - Lan settings. They are greyed out with both boxes checked. So now I'm running MS Defender with a USB drive to see what it finds.