automatic private ip address vs. dhcp assigned

[erick]

I recently replaced my linksys router with a dell 2300
wireless. I am still using a wired connection until I
get a wireless adapter. After changing to the new router
one of my computers will not connect to the internet.
Instead of being assigned an IP address by DHCP it uses
an automatic private IP address (I think my modem
address). I tried to switch back to the other router and
it still does this. I tried to manually configure the IP
address, but still can't connect to the internet. I
could see the computer on the network, could ping IP
addresses but not domains.

 

[Kent W. England [MVP]]

You can see it because you are likely using NetBEUI as well as TCP/IP,
but your node is not able to communicate with the DHCP server or there
is some incompatibility between your computer and the DHCP server.

If the linksys is still present, disable its DHCP server to allow the
dell wireless to do the job alone.

 

[Sitapati das]

Hi Erick,

If you can ping IP address outside your private network; then you might find
that you get this situation because DHCP usually takes care of the DNS
servers as well. This will happen if you manually assign the IP address, but
don't manually assign DNS servers. To solve it you can manually assign the
DNS servers as well. Use "ipconfig /all" at a command prompt on a machine
that is working to extract the information about the DNS servers.
This won't solve the original problem, but it could be a workable fix.

regards,
Sitapati