Event 1053 Dhcpserver shutdown

Discuss Windows Event Log events. What they mean, what they tell you about your machine's security ... and whatever questions else you have.

Moderator: alorbach

Event 1053 Dhcpserver shutdown

Postby AlanCates » Thu Apr 15, 2004 5:12 pm

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.1, belonging to the domain: .


On a new SBS 2003 after a couple of days I started getting this event and the dhcp server is shutting down.

I have verifued there is no other computer at 192.168.0.1 and that there are no dhcp servers on the LAN or WAN. nmap scans via tcp and udp confirm that. The dhcp is bound only to the 192.168.0.1 nic. I have uninstalled and reinstalled dhcp service. On the reinstall I lost the domain name in the server name portion of the dhcp server as shown in the console.

Also, I have to disable the 192...1 nic to get the dhcp server started to edit its settings.

I have seen this reported elsewhere but all solutions are to remove the 'other' dhcp server. I cannot find another. Anyone have an idea?
AlanCates
 

Exactly the same problem

Postby Frelon » Wed Dec 08, 2004 10:11 am

Hi

I have exactly trhe same problem...

Could tou help us ?
Frelon
 

Postby AlanCates » Wed Dec 08, 2004 8:23 pm

Yes. If I can remember all the details.

There are two DHCP servers in SBS '03. This problem happens because both are attempting to run. The setup menus in '03 sort of walks one into it. So, normally you only see this at setup or when one adds remote access for home or off site users.

There is the DHCP server proper that is accessed via the Admin Tools. This is normally the one you want running for the internal network.

There is also a DHCP server in the RRAS setup (remote access and routing in '03). This is the one that fooled me. If you tell RRAS to hand out IP's to remote connections it starts a second DHCP. It does not use the already running DHCP as I thought it would. Its idea of remote is everything other than its self. Thus the conflict. If you have a DHCP on the network then it should automatically provide IP's for remote connections too and there is no need for the RRAS DHCP.

On one of the other forums there is a dicussion of the problem and the step by step resolution. I do not recall the menu path and a quick look at one of my 03 servers proves I have forgotten where it is. I do know that depending on which tool you use it can be hard to find.

But I did find the resolution here: LINK

Also, EventID has information too.

Good Luck. Alan Cates - Cates-Associates.net
AlanCates
 

Google Ads



Return to Windows Events

Who is online

Users browsing this forum: No registered users and 0 guests

cron