Is your server's DHCP being renamed to "mshome.net" and getting Event ID: 30013 in your log files?

re: Is your server's DHCP being renamed to "mshome.net" and getting Event ID: 30013 in your log files?

Nathalie V. Hernandez — Mon, 20 Feb 2006 23:40:26 GMT

I would like to thank you, thank you! I had this problem with RRAS interfering with DHCP server in an sbs 2003 box. For two days my clients were having slower than normal access to the server. Upon inspection, I realized that the DHCP was somehow corrupted. When I accessed the DHCP server, the service was running, but it was leasing out weird IP address. Then, I realized that the authorized DHCP server was defaulting to company.mshome.net. Even worse I couldn't even reconfigure the scope because it kept telling me that the scope old scope existed though it didn't display the scope nor its associated leased addresses. It was just like bizarro world. Well, as long as the clients were able to access the network, I had a one to two day time to fix the problem. As soon as I disabled the RRAS and restarted DHCP, chose reconcile, my DHCP server was back to normal. I then went ahead and ran the wizard for RRAS and your solution was immediate relief. Thank you!

re: Is your server's DHCP being renamed to "mshome.net" and getting Event ID: 30013 in your log files?

bradley — Tue, 15 Feb 2005 07:41:00 GMT

I have had the same problem but connected to exchange. I couldn't open several exchange folders. The solution above was not working. So I fiddled around with Hosts.ics in system32/etc. After renaming server.mshome.net to server.domain.local in the file everything was running fine. Nevertheless the latest exchange patches have solved the problem. SBS is running smooth with server.mshome.net in Hosts.ics.

So I just put in my Sharepoint CALs

TrackBack — Sun, 21 Nov 2004 18:41:00 GMT

re: Is your server's DHCP being renamed to "mshome.net" and getting Event ID: 30013 in your log files?

bradley — Thu, 11 Nov 2004 03:21:00 GMT

I have the same problem, BUT its on a windows 2000 machine workstation, any ideas

Event Type: Error
Event Source: ipnathlp
Event Category: None
Event ID: 30013
Date: 9/11/2004
Time: 6:50:14 AM
User: N/A
Computer: GGA1
Description:
The DHCP allocator has disabled itself on IP address 192.168.1.102, since the IP address is outside the 192.168.0.0/255.255.255.0 scope from which addresses are being allocated to DHCP clients. To enable the DHCP allocator on this IP address, please change the scope to include the IP address, or change the IP address to fall within the scope.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Please email me back on
mark@computerland.com.au

re: Is your server's DHCP being renamed to "mshome.net" and getting Event ID: 30013 in your log files?

bradley — Thu, 06 May 2004 19:15:00 GMT

SBS2k3 is Windows Server 2003. Whatever hotfix you have received, is for us too. Do you remember the KB number?

re: Is your server's DHCP being renamed to "mshome.net" and getting Event ID: 30013 in your log files?

bradley — Wed, 28 Apr 2004 21:14:00 GMT

I had this same issue on a Server2k3 Enterprise Edition multi-homed do-all play box. To fix, I actually just unchecked the Address Assignment box and restarted the RRAS server. If I'm not mistaken I can toggle the problem on and off simply by checking/unchecking and restarting the RRAS server. Unbelievable. I thought for days it had something to do with my Microsoft Wireless Device having mistakenly registered itself in DNS or something.

Also, you might be interested to know that there is a fundamental issue on multihomed DC's which continuously registers the outside NIC in DNS even when advanced TCPIP settings are config'd not to. I rec'd an unsupported hotfix for this, but it IS Server 2k3 related moreso than SBS2k3.