Windows Server 2012 R2 DHCP Server will not Start Event #1053 & 1054

Toggle sidebar Toggle sidebar
R

rezada28

Feb 22, 2018
3
0
20
Errors began when attempting to configure a SonicWall to our network as noted in Even Viewer. We have 1 Server and 11 Desktops. The SonicWall was previously connected without error however I was not provided with the Admin Password to the SonicWall, only to the mysonicwall.com site. Firmware needed upgrading so I was forced to do a factory reset of the SonicWall and in safemode. Success. The configuration of the SonicWall was unknown so I contacted the ISP for assistance. Turns our we have a static IP. I got the internet up and working on the network again however I can't seem to get the DHCP service running. I learned of the DHCP server because: Two of our machines had domain trust issues so I tried disconnecting them from the domain and reconnecting them (no luck). I had disabled the IPv6 and attempted to point the boxes through IPv4 statically to the server and no luck. The machines noted an "An Active Directory Domain Controller (AD DC) for the domain, "xxx.local" could not be contacted" error. I can ping the DNS from these endpoints. I flushed the DNS and /regiterdns commands with no luck. I am wondering if there is some sort of configuration issue with the SonicWall? Has to be right? But what is it? The Ipconfig of the server reports back that the Ethernet adapter NIC 1 & 2 are set to a Default Gateway 192.168.3.1 which is the same as the DHCP server address on a network endpoint. Is this where it is messed up? This is the same IP address for the LAN on the SonicWall but if I change this on the SonicWall the internet connection is lost. What should I do.
 
Solution
R
The SonicWall Firewall DHCP service is turned on by default. Turning off the DHCP service on the SonicWall Firewall allowed the DHCP service on the server to restart. Now the clients can be added back to the domain. Issue fixed.
Sort by date Sort by votes
R

rezada28

Feb 22, 2018
3
0
20
The SonicWall Firewall DHCP service is turned on by default. Turning off the DHCP service on the SonicWall Firewall allowed the DHCP service on the server to restart. Now the clients can be added back to the domain. Issue fixed.
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom