Click to See Complete Forum and Search --> : No connectivity using DHCP


maho
10-31-2005, 10:09 AM
I have a Laptop (Dell Inspiron 4150) with a wireless B/G minipci card (Intel Pro 2200BG).

When running DCHP on my home wireless network I always get "Limited or no connectivity" and no connection. If I set it up to static IP I have a good 54mbps connection immidiatly.

I have another laptop which have no problem getting a IP adress over DHCP, so my router, firewall, switch setup should be ok.

I have installed the Microsoft Fix KB884020.
I have run the winsockxpfic
I have checked for spyway, TSR programs using AdAware
I have tried the ipconfig /release; ipconfig /renew

Still no connection using DHCP. I just get a 169.244.XXX.XXX adress, which I guess windows defaults to if no DHCP is availible.

Please help me !!!
THX

JackMDS
10-31-2005, 05:39 PM
Check the Router's DHCP and client table.

May be it has only on IP in the DHCP, or and the IPs has to be associated with MAC numbers and it does not have the second computer's MAC in the MAC table.

:cool:

maho
10-31-2005, 07:16 PM
The way I have set up the router I have a dhcp pool of 8 adresses, so there should be plenty to choose from.

Router: 10.0.0.1
DHCP IP pool 10.0.0.2 - 10.0.0.9
Static IP's 10.0.0.10 - 10.0.0.255
Netmask 255.255.255.0

Only one other DHCP adress is used (The other working laptop)
All other computers on the network are on static IP.

maho
11-01-2005, 05:37 PM
So today I tried the following:

Removed a lot of networking software from the PC (Zonealarm, Hamachi, etc)
Ran the software patches and fixes again: No connection
Turned off the Windows XP firewall: No connection
Reloaded the Router Firmware: No connection
netsh int ip reset [log_file_name] : No connection
Disabled WPA encryption: DHCP CONNECTION !!! :cool:
Enabled WPA encryption again with another key: DHCP CONNECTION !!! :confused:
Enabled MAC Adress Filterring: DHCP CONNECTION !!! :D

So now everything seams to be working. I have transfered more than 6 GB over the connection and it is still going strong.

I belive it was a mix of things causing this problem, but now I don't really care ;)