I'm testing the DHCP settings on the server before I start using the feature company wide. I configured my PC for DHCP. When I shut down and restart my computer, the address assigned to my PC will not release. I have to run IPCONFIG /renew to get the IP assigned again, or delete my listing from the address pool under DHCP on the server. (I only have one subnet.) I did notice that all DHCP listings in the registry show an IP address for DHCP as 169.254.241.181. The server is a 192.168.xx.xx address and so is the address pool. Is there something wrong with the DHCP configuration that it doesn't recognize a release for 192.168.x.x addresses? (This address also lists under DNS for the local computer, but I don't know what's generating it. If I run ipconfig, the correct IP address displays for the server NIC.)
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
2000 server DHCP will not release IP address
- Thread starter alexs0628
- Start date
So when you reboot, your computer doesn't get assigned an address at all until you run ipconfig /renew?
And is the server's IP address static or are you trying to get it with DHCP as well?
That 169.254.241.181 address is an APIPA address. One that Windows gives itself if it's configured to get an address via DHCP but can't find the DHCP server.
And is the server's IP address static or are you trying to get it with DHCP as well?
That 169.254.241.181 address is an APIPA address. One that Windows gives itself if it's configured to get an address via DHCP but can't find the DHCP server.
- Thread starter
- #3
That's right. If I re-boot, I don't get assigned an IP address. I run ipconfig /renew, then I get one. Or, if I delete my IP listing from DHCP on the server. DHCP doesn't release the last address my PC was assigned, nor does it assign my PC a new one.
The ip address you are receiving is a private IP address and cannot be released. This is a feature Microsoft started in Windows 98 and it has been used in Windows ME, 2000, XP, etc. This is caused by any of the following:
> Faulty NIC
> Bad network cable
> Network connection is not connected somewhere
> Bad or wrong NIC drivers
Try resinstalling your NIC. swapping cables, etc.. For some reason your NIC is not able to obtain a IP address from the DHCP server or router.
> Faulty NIC
> Bad network cable
> Network connection is not connected somewhere
> Bad or wrong NIC drivers
Try resinstalling your NIC. swapping cables, etc.. For some reason your NIC is not able to obtain a IP address from the DHCP server or router.
zoeythecat
Technical User
I would recheck your settings on your DHCP server and make sure everything looks correct. What options do you have defined?
Common options are:
003 Router (if you have a router in your environment)
006 DNS Servers
015 Domain Name
044 WINS/NBNS Servers
046 WINS/NBT Node Type
Options 044 and 046 are if you use WINS. 003, 006 + 015 are critical options you need. Also make sure your IP Address scope is setup correctly and has the correct subnet mask. Check the Address Leases under the scope. Do you see anyone getting an IP Address from here?
Common options are:
003 Router (if you have a router in your environment)
006 DNS Servers
015 Domain Name
044 WINS/NBNS Servers
046 WINS/NBT Node Type
Options 044 and 046 are if you use WINS. 003, 006 + 015 are critical options you need. Also make sure your IP Address scope is setup correctly and has the correct subnet mask. Check the Address Leases under the scope. Do you see anyone getting an IP Address from here?
zoeythecat
Technical User
Also make sure your scope is "Authorized" and active. (I'm sure it is, just throwing that to the checklist of things to check)
ShackDaddy
MIS
Your problem is essentially getting an address from the server, so it's about connectivity and server-side configuration.
Manually configure the client with a static address and then ping the server to make sure you are on the same wire. Then make sure that the scope has been activated and was configured with the proper subnet mask. Blow away the scope and create it again if you have to.
ShackDaddy
Manually configure the client with a static address and then ping the server to make sure you are on the same wire. Then make sure that the scope has been activated and was configured with the proper subnet mask. Blow away the scope and create it again if you have to.
ShackDaddy
- Thread starter
- #9
These messages displays in my Event Viewer:
The system failed to update and remove registration for the network adapter with settings:...(network settings listed correctly.)
...The reason for this failure is because the DNS server it sent the update request to timed out. The most likely cause of this failure is that the DNS server authoritative for the zone where the registration was originally made is either not running or unreachable through the network at this time.
And --
No Windows NT or Windows 2000 Domain Controller is available for domain (company name). The following error occurred:
There are currently no logon servers available to service the logon request.
And --
Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 00065B8065C8. The following error occured:
The semaphore timeout period has expired. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.
Then I run ipconfig /renew and I get the IP address back.
I think I'm having time out problems. I am also logging onto a Novell 3.12 server that we are still using. We use the Novell client (4.83 sp2) for login to both servers, but it takes a minute or two for my PC to communicate with the Novell server. I always have to click on Server and find the Novell server before it lets me log on to that one. When I was testing W2k server in my test station setup, I was using the W2k client logon and DHCP wasn't a problem. Maybe that's part of the problem?
The system failed to update and remove registration for the network adapter with settings:...(network settings listed correctly.)
...The reason for this failure is because the DNS server it sent the update request to timed out. The most likely cause of this failure is that the DNS server authoritative for the zone where the registration was originally made is either not running or unreachable through the network at this time.
And --
No Windows NT or Windows 2000 Domain Controller is available for domain (company name). The following error occurred:
There are currently no logon servers available to service the logon request.
And --
Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 00065B8065C8. The following error occured:
The semaphore timeout period has expired. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.
Then I run ipconfig /renew and I get the IP address back.
I think I'm having time out problems. I am also logging onto a Novell 3.12 server that we are still using. We use the Novell client (4.83 sp2) for login to both servers, but it takes a minute or two for my PC to communicate with the Novell server. I always have to click on Server and find the Novell server before it lets me log on to that one. When I was testing W2k server in my test station setup, I was using the W2k client logon and DHCP wasn't a problem. Maybe that's part of the problem?
- Status
Similar threads
- Locked
- Question
- Locked
- Question