Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 465
  • Last Modified:

DHCP handing zero address

I just ran into a client that was having issues connecting to our mail server and other sites. When I ran IPconfig to find out what IP address it was assigned I noticed that it had a .0 address, basically it had the network name as an IP address.  i.e. 192.168.60.0.
I'm wondering why DHCP would hand out this address as it is not a valid IP address.

Any thoughts?
0
GW_Techno
Asked:
GW_Techno
  • 3
  • 2
  • 2
2 Solutions
 
ipajonesCommented:
Have you checked the allowed range of addresses configured in the DHCP scope ?
0
 
Chris DentPowerShell DeveloperCommented:

Depending on the accompanying subnet mask, 192.168.60.0 is potentially a valid address. What is the subnet mask here?

Chris
0
 
GW_TechnoAuthor Commented:
Yes, basically my range is 192.168.44.1 - 192.168.47.254 *not the actual numbers but last two octets are correct.    So we actually have 1,024 available IPs in that range.  Microsoft DHCP server doesn't allow me to set exclusions to block the 192.168.45.0,x.x.46.0 and  x.x.47.0 from being handed out..

I didn't think it was possible to assign a dot zero address.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
GW_TechnoAuthor Commented:
we're using the subnet mask 255.255.252.0
0
 
Chris DentPowerShell DeveloperCommented:

That's a valid address then, or it should be. A range is whatever total, -2, one broadcast, and one subnet (1024 - 2 = 1022 useable). All addresses between, 0 and 255 included, are valid addresses.

Does whatever you're using refuse to talk to a host on that address?

Chris
0
 
ipajonesCommented:

Just following on from Chris-Dent's last comment:

If you're using the range 192.168.44.1 - 192.168.47.254 with a /22 mask (255.255.252.0) then both 192.168.45.0 and 192.168.46.0 will be classed as valid addresses.  If you want to exclude them you may have to setup separate scopes.
0
 
GW_TechnoAuthor Commented:
It wasn't until you mentioned the subnet mask that I realized that it was a good address.   I guess I never noticed .0 addresses being used.

Actually discovered that it was a corrupt image, or Office installation that was causing the problem.

Thanks for your help
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

  • 3
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now