Windows Forum

Ask something
Discussion Locked

Automatic Private IP Addressing

0 helpful
2 replies

by shanghai sam

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Win2k assigns an IP in the range of 169.x.x.x if it can't find a DHCP/DNS. I have a Win2k Server and two win2k WS; one is able to get a valid IP, the other is not; they're on the same hub, within 3 feet of one another and the server. If I specify the parameters, bang, the spoiler is in like Flynne, the other I've had no issues, and I can bring in a Win2k laptop and connect. So, what can cause this one machine to be so canterous? And is there a way to specify a different default IP address range?

2 replies

by faisalmasood

ok do this:

1) Go to DHCP in Administrative Tools
2) Click you computer name
3) Click the Scope you have defined for your network
4) Click Reservations
5) Now Minimize this window & open command prompt in your client pc or type cmd in Start > Run & enter
6) In command prompt type c:\nbtstat -a pcname
(pcname = netbios name of client)
7) Note the MAC address in bottom
8) Now back to reservation in DHCP. Right Click Reservation & select New reservation
9) Give the reservation any name, IP address you want to assign to client from your Scope, MAC address you noted above. You are done. :)
10) Don't forget to mention this IP in exclusion range also.

by mattius

Have you tried ipconfig? From the command window type "ipconfig /release" enter, then "ipconfig /renew" enter, then "ipconfig /all" to see if you got an ip.

After you clear the APIPA you should get DHCP from then on.

This discussion is closed to new replies.