 |  |  |  |  |  |  |  |
DHCP Server: BAD_ADDRESS
 |
I have DHCP installed on our server, and while checking the leases I noticed a few BAD_ADDRESS entries. I delete them but they return within a few seconds. Anyone know the cause of this and how to prevent it?
Thanks!
Thanks!
It is practically impossible to teach good programming style to students that have had prior exposure to Basic; as potential programmers they are mentally mutilated beyond hope of regeneration.
-Edsger Dijkstra
-Edsger Dijkstra
Can you trace the bad adress to any workstations?
How many workstations do you have?
How many can you see in the DHCP list?
Do workstation addresses match those in the DHCP list?
Are all the workstations set to DHCP?
Do they have all the correct subnet masks?
These are all things you should check.
How many workstations do you have?
How many can you see in the DHCP list?
Do workstation addresses match those in the DHCP list?
Are all the workstations set to DHCP?
Do they have all the correct subnet masks?
These are all things you should check.
Last edited by knsljo; Jul 6th, 2006 at 2:56 pm.
•
•
•
•
Can you trace the bad adress to any workstations?
How many workstations do you have?
How many can you see in the DHCP list?
Do workstation addresses match those in the DHCP list?
Are all the workstations set to DHCP?
Do they have all the correct subnet masks?
These are all things you should check.
Can't trace the addresses
roughly 25
(random)
from what i can tell
no (we're in the process of switching over to new network architechture)
yes
It is practically impossible to teach good programming style to students that have had prior exposure to Basic; as potential programmers they are mentally mutilated beyond hope of regeneration.
-Edsger Dijkstra
-Edsger Dijkstra
You need to check this when all DHCP configured machines are running.
Take a note of all there ip addresses and cross reference it with the DHCP list.
The machines that are not configured with DHCP could have static ip addresses that conflict with addresses that are issued by DHCP. If they are on the same network and they are switched on after a workstation which has been issued with the same ip address they will conflict. You need to make sure that the DHCP server cannot issue any of the static ip addresses.
eg: set DHCP to issue 192.168.1.100-192.168.1.150 then set all static addresses outside of this range.
This is just one possibility.
Hope this helps.
Take a note of all there ip addresses and cross reference it with the DHCP list.
The machines that are not configured with DHCP could have static ip addresses that conflict with addresses that are issued by DHCP. If they are on the same network and they are switched on after a workstation which has been issued with the same ip address they will conflict. You need to make sure that the DHCP server cannot issue any of the static ip addresses.
eg: set DHCP to issue 192.168.1.100-192.168.1.150 then set all static addresses outside of this range.
This is just one possibility.
Hope this helps.
thanks for the reply.
all of our static ips are 13.240.x.x and the dhcp is set to lease 192.168.x.x
all of our static ips are 13.240.x.x and the dhcp is set to lease 192.168.x.x
It is practically impossible to teach good programming style to students that have had prior exposure to Basic; as potential programmers they are mentally mutilated beyond hope of regeneration.
-Edsger Dijkstra
-Edsger Dijkstra
Well I figure it's about time to bring this post back to life.... 
I'm still getting a bunch of BAD_ADDRESS entries in my DHCP Address Lease scope. The MAC Address is shorter than the work stations'....
I'm still getting a bunch of BAD_ADDRESS entries in my DHCP Address Lease scope. The MAC Address is shorter than the work stations'....
It is practically impossible to teach good programming style to students that have had prior exposure to Basic; as potential programmers they are mentally mutilated beyond hope of regeneration.
-Edsger Dijkstra
-Edsger Dijkstra
What do you mean with "Moved." ?
I have the same problem.
- bad_address
- shorter MAC
Duki, were you able to solve the problem ?
I have the same problem.
- bad_address
- shorter MAC
Duki, were you able to solve the problem ?
Ive had this before when 2 machines had the same mac (dont know why, i thaught they were supposed to be unique to the h/w?)
If i am helpful, please give me reputation points.
Well yes and no. We recently installed new servers, which do not give this error. I figure it was something configured wrong in DNS or DHCP on my behalf; it was my first DC.
It is practically impossible to teach good programming style to students that have had prior exposure to Basic; as potential programmers they are mentally mutilated beyond hope of regeneration.
-Edsger Dijkstra
-Edsger Dijkstra
|
Similar Threads
- Need for DNS? (Windows NT / 2000 / XP)
- FC4, DHCP server (*nix Software)
- setting up dhcp server with redhat 9 (*nix Software)
Other Threads in the Networking Hardware Configuration Forum
- Previous Thread: Gigabit network slow samba, ftp, iperf?
- Next Thread: Advice on Network Connections required
| Thread Tools | Search this Thread |
You need to join our community in order to build your list of favorite forums. You can visit the forum index for a listing of all forums.
Related Forum Features
Latest Networking Hardware Configuration Posts
802.11 802.11n bluetooth british broadband browserproblems bt connectionproblem connectivity cpu data desktop dual gigabyte hardware infrastructure internet memory network networking news program rdimm reliability riched20.dll routers server storage survey technology telecoms troubleshoot uk upgrade videoconferencing view virgin wireless wirelessnetworking
