So yea i tried uninstalling the drivers and what not, it still gets stuck... ethernet works.
*** it gets stuck at "Acquiring Network Address" my bad...
FIXED:
I reset some thing through cmd (just followed google) in initially it diddn;t work, but now it did xD
-
The IP stack? Anyways, glad.
-
i have to reset winnstock... this happened again though...
so that is a short term ffix... i need a longterm one.
any ideas? -
ok, im thinking that NOD 32 and my wireless decided that they don't like eachother today...
that appears to be the problem i think....
NVM, its not the problem...
EDIT: ok.. it appears to work, but nod32's firewall refuses to work now... odd... (tried reinstalling multiple times) -
Just wondering, how many packets are being sent and how many are being received and how many are being dropped?
-
-
Oh it's fine
. In your network and router settings there should be a panel in there showing a diagram of a network with a key showing information about the packets. That's how it is on my Linksys router anyways.
-
i know my router showed my laptop as connected though, but the laptop didnot/wouldn't -
It could be your ISP is down for a while for maintance.
-
-
If the system's not able to acquire an IP address from the router, check to make sure that both laptop and router are set to use DHCP (i.e., the router is set to act as a DHCP server, and the laptop to acquire IP address automatically through DHCP), and that the info the router is providing through DHCP is correct - including, for example, making sure that the router has a large enough range of IP addresses that it is permitted to assign via DHCP; for example, if the router is only permitted to assign IP addresses from the range 192.168.1.1 to 192.168.1.3, and there are already three other systems with assigned IP addresses, the router will be unable to assign an IP address to a fourth system that comes asking for one.
-
Lappy stuck at "Obtaining IP address"
Discussion in 'Networking and Wireless' started by aan310, Dec 20, 2008.