| T O P I C R E V I E W |
| alanc |
Posted - 04/17/2004 : 8:25:24 PM
I have not yet been able to get around this problem.
quote:
Event 1053 Source Dhcpserver
The DHCP/BINL service on this computer running Windows Server 2003 for Small Business Server has encountered another server on this network with IP Address, 192.168.0.2, belonging to the domain: .
While setting up a SBS 2003 server I started getting this error and the Dhcp server begin shutting down. This started after the server crashed from a bad DVD driver. Driver was replaced and it now works. But, then the 1053’s and shut downs started.
Everything I can read says there is another Dhcp server causing the shut down. But…
This small system has 10 client computers all of which are on Dhcp and the server has 2 static ip’s (66… and 192.168…). There is an Alcatel DSL modem set to use static ip’s. Dhcp on the Alcatel is disabled. Also the DSL connection is isolated, coming from the modem to its own NIC in the server. A second NIC serves the LAN.
I have scanned the network for another Dhcp server. I cannot find one, LAN or WAN. There was one on the LAN for a time while this unit was being setup but either this SBS’s Dhcp was stopped or the other one was stopped. Now the other (old P2P Wingate) server is off the network.
I originally had the server at 192.168.0.1 and ran all of these tests. Then I moved it to 192.168.0.2 and tried again. Same problem came back.
I have shut down the server and pinged for another 192…1 and or 2 machine. None found.
I’ve checked the Dhcp bindings and it is only bound to 192…2
I’ve scanned the network with Nmap looking for another Dhcp server, none found.
I have uninstalled Dhcp and deleted the \system32\Dhcp folders and then reinstalled. I then ran Change IP using the original/same 192… ip and then ‘Connect to Internet.’ The problem reoccurs and the Dhcp server now posts the domain name mshome.net in the Dhcp management consoles. The work stations show the mshome.net suffix in spite of our domain name being entered as parameter 015 Domain Name for the scope and server.
Often on a reboot the Dhcp will come up correctly and run for 1 to 2 hours before shutting down. When I restart I get a start event then a shut down and events 1503/1504. I can disable the 192...2 NIC and restart Dhcp then enable 192…2. The Dhcp will continue to run, apparently indefinitely, but with the mshome.net suffix/domain and any restarts and some scope setting changes will cause it to shut down again.
I’m lost. I can’t find another Dhcp server that could be causing the shut down. I’ve even turned off the DLS modem and tried, no joy. 
Does anyone have any suggestions?
|
| 24 L A T E S T R E P L I E S (Newest First) |
| Emmanuel442 |
Posted - 01/02/2006 : 08:21:12 AM
quote:
Originally posted by NMDANGE
Sorry if I wasn't clear, I tend to use the standalone MMC applets.
Saying "standalone" is a piece of cake when no one is around to kick your butt..
|
| nickw |
Posted - 12/01/2005 : 3:33:22 PM
Good stuff :) |
| biggskofford |
Posted - 11/30/2005 : 6:12:42 PM
Thanks Nick...
After searching through the posts, I saw your response about internet connection sharing. I was having this problem on one of my workstations...the user turned on ICS and several other workstations began to obtain their DNS and DHCP info from the rogue workstation.
I "unshared" the internet connection and all is well now.
...keith |
| MarieMc |
Posted - 04/23/2004 : 10:59:41 AM
Hey there Nick!
 |
| nickw |
Posted - 04/23/2004 : 10:54:37 AM
Hi Marie  |
| MarieMc |
Posted - 04/23/2004 : 10:15:22 AM
Please disable RRAS, and stop the DHCP ALLOCATOR services and then configure it using the TO DO LIST wizard.
|
| nickw |
Posted - 04/22/2004 : 12:58:19 PM
http://www.sbslinks.com/mshome.htm
|
| NMDANGE |
Posted - 04/22/2004 : 10:04:17 AM
If you are using Computer Management instead of the stand-alone RRAS MMC, you can right-click where it says "Routing and Remote Access" in the Services & Applications tree, and get to the properties of the server from there. Sorry if I wasn't clear, I tend to use the standalone MMC applets. |
| alanc |
Posted - 04/21/2004 : 10:40:32 PM
quote:
Did you get that from Les?
Yes. I have been following the MSHome.net thread at MS's SBS forum.
quote:
Does VPN still work?
Actually I do not know. We are not presently using VPN.
|
| nickw |
Posted - 04/21/2004 : 7:36:44 PM
Alan,
Does your VPN still work when you do what you did?
|
| nickw |
Posted - 04/21/2004 : 6:42:00 PM
Hi Alan,
Did you get that from Les?
I just got an email saying:
"Looks like the DHCP Allocator in RRAS, under the properties of NAT/Basic Firewall has been enabled."
|
| alanc |
Posted - 04/20/2004 : 10:21:05 PM
MSHome.net Problem persists. THe clients are showing their domain suffix as mydomain.com, as they should. But, the Dhcp console still shows the service on mshome.net.
I renamed the hosts.ics file and restarted the server. The exact same hosts.ics was created. I had hoped it would reset itself.
Does anyone know how to clear and reset the Dhcp? I suppose I could uninstall and reinstall Dhcp again...
--------Edit----------4/21
In RRAS one can turn off name resolution and then the Dhcp console shows the correct domain name. Hurray. On my next restart I will see if it changes the hosts.ics file info. |
| alanc |
Posted - 04/20/2004 : 11:04:23 AM
quote:
Just open up the RRAS MMC, right-click the machine, select properties then go to the IP tab.
Where it says "IP Address assignment" select DHCP, and choose your LAN adapter in the drop-down on the bottom. This should tell RRAS to use the DHCP server to get IPs for vpn clients.
 This statment confused me because...
In my SBS machine there is no 'machine' in the RRAS section of the tree. The tree runs as:
Server Management Console
Advanced Management
Computer Management (local)
Services and Applciations
Routing and Remote Access
IP Routing
NAT/Basic Firewall
In NAT/Basic Firewall there are four right pane entries, my two NIC's, as I named them, loopback and internal. I setup NAT on the external NIC. Within the NIC properties are most of the firewall controls and port setups.
In the NAT/Basic Firewall properties (left pane) there is a properties page that has a tab labeled 'Address Assignment.' This page has one checkbox labeled 'Automatically assign IP addresses by using the Dhcp allocator.' There is no drop down for NIC selection. There are fields for the IP range and an 'Exclude...' button. There is no NIC selection.
Activating the allocator with internal addresses leads to the Dhcp problems I experiened. Yesterday I shut down this allocator and the Dhcp service has been up for 12+ hours. With the allocator running the Dhcp service shuts down in 2 to 3 hours or sooner.
BUT... There is a machine listed if I go in through the RRAS console. The Server Mgmt. Console and the RRAS consoles are not the same on my SBS 2003. Using the RRAS console I find the settings the quote refers to and I can see how to setup the RRAS addressing for VPN and dialup.
Actually, using the Server Mgmt console I cannot find a path to the properties available through the RRAS console. I suspect this may be the reason so many of us are running into the Dhcp 1053 shutdown problem. |
| NMDANGE |
Posted - 04/20/2004 : 10:05:38 AM
You don't need the DHCP Allocator on RRAS if you have a DHCP server.
Just open up the RRAS MMC, right-click the machine, select properties then go to the IP tab.
Where it says "IP Address assignment" select DHCP, and choose your LAN adapter in the drop-down on the bottom. This should tell RRAS to use the DHCP server to get IPs for vpn clients. |
| nickw |
Posted - 04/20/2004 : 07:39:26 AM
Hi Alan,
Keep us informed... I have never seen this issue, but it seems others have :) I would like to know the outcome.
Thanks,
|
| alanc |
Posted - 04/19/2004 : 9:02:56 PM
quote:
Originally posted by alanc
Thank you for your responses and help.
The system is somewhat in use today. This evening I will try your suggestions and post back.
I read through the information provided. It seems the RRAS has a Dhcp Allocator and that it is seen by SBS's Dhcp as a second Dhcp server. Shuting down RRAS has allowed those discussing the problem in some of the threads to keep their Dhcp servers running and has enbled the ability to restart them. This seems to be the case for me.
The information shows that the Allocator is supposed to provide IP's for dialup and VPN clients. So this should be, I think, connected to the external NIC, which mine is. In Minasi's Server 2003 the RRAS setup covers setting up the NAT to simulate ICS. On page 279 it shows setting the IP range to the internal address range and using it as an internal Dhcp service. He calls it a 'mini-Dhcp server in NAT.'
Later along about page 306 Minasi goes into setting up Dhcp. I went through those steps and, while I may have missed it or the concept, there is no warning about the possible conflict with NAT's allocator. But, from what I am reading this is the problem.
Even with the Dhcp Allocator bound to the external NIC I got this problem. I suspect that is because it did not occur to me that RRAS was for external use and its scope was set to overlap the internal Dhcp service. Since I do not need RRAS for external connections I shut down the allocator.
I still have the problem that mshome.net is the name appearing in the Dhcp console. As yet I have not been able to get it to change to my domain name. But it appears the Dhcp service will run without shut down. I can now restart the service without a problem and it remains running. It will be several more hours before I am sure the shutdown problem is corrected. Previously it has taken 2 or 3 hours for a shut down to occur. I'll check it later tonight and see what happens.
Again, thanks for the help. I think the threads provided will help with the name problem too. I'll go through them again. |
| alanc |
Posted - 04/19/2004 : 2:30:29 PM
Thank you for your responses and help.
The system is somewhat in use today. This evening I will try your suggestions and post back.
|
| nickw |
Posted - 04/19/2004 : 1:26:46 PM
Another one from Les..
http://groups.google.ca/groups?hl=en&lr=&ie=UTF-8&threadm=BC489189.5DC%25lisan%40brennekeschool.com&rnum=1&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DISO-8859-1%26q%3Ddhcp%2Bstopped%2Bmshome.net%26btnG%3DSearch%26meta%3D |
| nickw |
Posted - 04/19/2004 : 12:51:02 PM
Thanks Andy... hope this helps...
Also, these ideas from the other SBS Rocks team
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&c2coff=1&threadm=ul03HopHEHA.828%40TK2MSFTNGP12.phx.gbl&rnum=2&prev=/groups%3Fq%3Dmshome.net%26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26c2coff%3D1%26selm%3Dul03HopHEHA.828%2540TK2MSFTNGP12.phx.gbl%26rnum%3D2
|
| HandyAndy |
Posted - 04/19/2004 : 12:40:56 PM
Hi Alan,
Here is what I would try, even though you think you uninstalled and reistalled DHCP, it is sticky and so are it's settings. Try following this kb http://support.microsoft.com/?kbid=169229 and do everything except saving the scope. You want to wipe it clean and create a new scope.
It does look to me to be coming from the SBS box itself.
If this KB does not do the trick, post back here and Nick will let us know to dig deeper for you.
HandyAndy [SBS-MVP] a.k.a. Andy Goodman
www.SBS-Rocks.com |
| nickw |
Posted - 04/19/2004 : 12:03:19 PM
I have asked some others to look at this post and give some ideas...
|
| alanc |
Posted - 04/19/2004 : 10:41:20 AM
I have looked through the machines. I actually visited each one. There are no AOL installs and few of the computers have more than one NIC or even a modem. Those machines do not have ICS installed or turned on. Some do have 1394 bridging which I am unframilar with but seems to have been part of the default setup from our computer vendor. But, nothing in the bridging properties leads me to think they might create an ICS share or Dhcp service.
Also, if ICS was on, wouldn't it show in a port scan from Nmap?
Also, if this were an ICS problem, wouldn't it go away when all the workstations are turned off? Whether the workstations are on or off I get this second Dhcp error.
Also in the Dhcp console I get both a mshome and mydomain Dhcp servers. I have tried to get ride of the mshome by unauth. it. I also see the mshome.net dhcp listed as being on 192.168.0.2... which leads me to think the phantom Dhcp server is in the SBS server. |
| nickw |
Posted - 04/18/2004 : 07:04:45 AM
An update:
I just confirmed that Windows XP Internet Connection Sharing (ICS) has an inbuilt DHCP Server of sorts. This is your phantom machine.
|
| nickw |
Posted - 04/18/2004 : 07:00:16 AM
Hi Alan,
The "mshome.net" domain is normally associated with a machine that has had ICS installed on it. Check all of your XP machines to ensure that none of them are running ICS. Do that for a start, I am looking into other possible causes.
http://support.microsoft.com/?kbid=309642
|
