Monday, March 11, 2013 1:27 PM
Okay first off all, I run a HP pavillion M6-1012tx laptop.
And the problem is:
I can connect to my wireless network and get it to work, but after some time, it shows me this
Uploaded with [URL=http://imageshack.us]ImageShack.us[/URL]
Naturally, I tried disconnecting and reconnecting but when i try to reconnect, it says windows was unable to connect to the network, and when i click the option to try and solve the problem, my laptop crashes and i have to power off the laptop by force. When I turn the laptop back on, it works again, but the same problem happens, with the network suddenly going into no network access after every 20 minutes or so . I have no idea whats happening, it's not the router or the modem's fault because it works just fine with my smartphone. This problem has been there since 5 months ago, but I didn't care because I didn't have a router or wireless connection yet.
>I tried scanning my laptop with an anti-malware program and antivirus, but there were no malware or viruses
>I tried disabling and re enabling my wireless adaptor to no avail
>Updating my wireless adaptor driver crashes my laptop for some unknown reason
BTW I run a Windows 7 Home Premium SP1 (64 bit)
I hope someone can help me find a solution to this problem
Thanks in advance :D
Monday, March 11, 2013 3:53 PM
When the problem occurs have you looked at the event viewer to see if you have any Application or system events pertaining to the wireless?
Have you checked HP's support website for the latest wireless network card drivers?
Monday, March 11, 2013 11:05 PMThe IP address lease 192.168.1.2 for the Network Card with network address 0xAC162D4B8EE2 has been denied by the DHCP server 192.168.1.1 (The DHCP Server sent a DHCPNACK message). I think this is what caused the problem. Its the only error i can find connected to networks in the event viewer, as i said, I did try to update my wireless network card driver but when it was around halfway through installing, my laptop crashes and I have to power off my laptop by force
Wednesday, March 13, 2013 2:46 AM
It sounds to me like an issue with the DHCP settings on your router as your computer tried to renew its network configuration and the DHCP server (in this case your router) refused it. I know you said you are not experiencing the issue on your smart phone, but that doesn't necessarily exclude the router as the culprit.
1. I would suggest updating the cisco firmware on your router.
2. You could attempt an ipconfig /release followed by an ipconfig /renew at the command prompt. This basically forces the computer to renew its ip configuration.
3. Lastly you could try setting a static ip address, which doesn't fix the problem with the DHCP server (router) but will bypass the issue. To do this right click on your wireless connection> open network and sharing center> Change adapter settings (on the left)> right click on your wireless card and go to properties> select internet protocol version 4 (TCP/IPv4) from the list and click properties. At this point you'll want to click the buttons to specify the IP configuration and enter an IP address on the network that isn't already in use. This may be very easy if you have few devices on the network. Try for example ip address: 192.168.1.50 subnet mask: 255.255.255.0 Default gateway: 192.168.1.1 and you can make the primary DNS server 192.168.1.1 and ignore the secondary. once you hit apply and okay.
This should bypass the issue by ensuring that you PC always gets that ip address (192.168.1.50) from the router. From what you said your computer is assigning its own automatic private IP address because it fails to get one from the router. With that said, even though the issue is bypassed, the router still may have an issue with the DHCP settings and another option is to perform a factory reset on the router. KEEP IN MIND before doing this some DSL providers require log on info to be inputed into the router before the modem wil pass on it's public IP address that gets you online. If it's cable internet or something similar, this shouldn't be an issue