Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


DHCP alocator has disabled itself

  • Please log in to reply
1 reply to this topic

#1 KCav


  • Members
  • 98 posts
  • Gender:Male
  • Local time:06:25 PM

Posted 09 July 2018 - 07:45 AM

I am told address 10.0.0,37 is outside the scope I should change the scope.  Why should I have to manually change the scope?  How is the scope for IP addresses determined?  Ref. Event 30013, SharedAccess NAT


BC AdBot (Login to Remove)


#2 muroga


  • Members
  • 34 posts
  • Gender:Male
  • Local time:12:25 AM

Posted 09 July 2018 - 09:21 AM

Indeed a 10.0.0.xxx address is not in the scope of 192.168.137.x address assignment. Basically what you need to change if is your desired address is in place of You have to change it this way because a subnet mask of only allows you to change the last segment of the address, the first three numbers are part of the prefix which has to match, thats a simple less technical way to think of it. As to why you have to change this manually its because of the way the operating system has setup the internet connection sharing feature, apparently Windows 7 only allows the use of 192.168.137.x subnet.


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users