I promoted my server which was on a workgroup to a domain, which couldn't see the workstations, although I set up accounts, and the next day the server DNS and DHCP and all Active Directory functions had deconfigured themselves, which I had configured the previous evening. The workstations couldn't join the domain. I depromoted it to a stand-alone server and put back the workgroup. Now DNS is still behaving like it's on Active Directory, and DHCP can't initialize the server (itself). If I change the IP address from the address used on the domain, will that help? I believe the DHCP problem is related to DNS. whythisagainwhythisagainwhythisagain
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Workgroup to domain to workgroup; no DHCP
- Thread starter whythis
- Start date
In dhcp what options did you have running under the server options ? if buy chance you dont have 015 listed , the dhcp clients will not be able to join the domain , i am wondering about the authorize the dns server as well as dhcp , but why did it deconfigure it self , hmmm , if i was you i would re create a dhcp scope and re do dns services and try it from there ! Anthony Cabanas
Long Island Networking Technologies Inc acabanas@linettech.com
Long Island Networking Technologies Inc acabanas@linettech.com
- Thread starter
- #3
Hi, LinetTech: Thanks for the response. If you reread my question, I mentioned I demoted the domain to a workgroup again, and now DHCP can't initialize the server. I can't check the options if the server can't be configured. Can't create a DHCP scope now. I had it configured, as well as
Active Directory, the night before, and the next day it had deconfigured itself and would not allow me to reconfigure, so I demoted the server back to a stand-alone server, and now DNS doesn't configure correctly (thinks it's still on Active Directory) and DHCP can't configure the server. However, on the bright side of things, the workstations still have internet access (I'm here!). We'll see what happens in a few days, when the leases are up. Could well be I'll be reinstalling the server. whythisagainwhythisagainwhythisagain
Active Directory, the night before, and the next day it had deconfigured itself and would not allow me to reconfigure, so I demoted the server back to a stand-alone server, and now DNS doesn't configure correctly (thinks it's still on Active Directory) and DHCP can't configure the server. However, on the bright side of things, the workstations still have internet access (I'm here!). We'll see what happens in a few days, when the leases are up. Could well be I'll be reinstalling the server. whythisagainwhythisagainwhythisagain
Instead of waiting for the leases to expire, why not release them? Would be much quicker. When you set up a Domain, you don't create workstation accounts before you join them to the Domain. When they join, they will be automagically created. When you set up the Domain, did you remember to Authorize the DHCP server in AD? If not, that is why everything stopped working.... Thanks,
Matt Wray
Matt Wray
- Thread starter
- #5
Yes, I authorized the DHCP in AD. I installed all AD functions. Got up the next morning and all had absconded. Tried to reinstitute everything, and it couldn't accept the server. Got rid of the domain, went back to a workgroup, and now DNS and DHCP won't take the workstation/server info. I get messages that AD isn't responding. Considering AD isn't THERE any more....more Micros_ _t. whythisagainwhythisagainwhythisagain
Sounds like maybe it is time to restore your latest backup... Thanks,
Matt Wray
Matt Wray
- Thread starter
- #7
Matt: considering I'm sick of reconfiguring for this week, at least, I'm going to wait until the IP leases run out on the workstations. It's an experiment...wait and see if the leases run out and if so, how long it takes. I would rather eat dirt than have to set up the server again at this moment. Had a Trojan nothing could catch last week, redid the whole server, then got the bright idea to change from workgroup (which at least worked!) to domain. The rest is history....Like I tell my teenage son, whenever he's having a fit about the system, "What do you EXPECT? It's
MICROS_ _T!" Have a good one, whythisagain.... whythisagainwhythisagainwhythisagain
MICROS_ _T!" Have a good one, whythisagain.... whythisagainwhythisagainwhythisagain
Ahhh! A good old AD problem... If you are having DNS and DHCP problems after dcpromo was done, it's because the problem was there all along. Do you have anything on the server that might stop these things from functioning, like a gateway software, firewall software, or antivirus?
Well, if you look to see if you have any software that blocks ports DNS(53), DHCP(???I forgot I think it's 115), Telnet(23), ftp, etc.. Try uninstalling such software.
The other problem could be that AD didn't uninstall properly, try reinstalling. -- this is weak of me, but??
-- Some tips: Finding the source of the problem.
If your workstations are getting their leases renewed every time you boot up, then DHCP is working - or a DHCP on the network is working. To find out more on where workstations are getting their IP leased from type IPCONFIG /ALL at command prompt (win 2k and XP) or RUN winipcfg in WIN98 and click on Show More >>
If you are not sure it's the Server or something else you can use the NET command to stop DNS and DHCP on the server from the command prompt. Type NET stop DHCP at a command prompt to stop DHCP. Restart or renew the IP at a workstation and see if it renews. If it does then you have another machine on the network causing the problem.
To restart DHCP type NET start DHCP ... and same with DNS.
I need to know more about your Network setup to give you better advice.
Such as number of machines, is there a router, number of servers, how they are networked ... etc. Don't give anyone or me info that can compromise your network such as IP addresses, but a general description.
Hope this helps.
Well, if you look to see if you have any software that blocks ports DNS(53), DHCP(???I forgot I think it's 115), Telnet(23), ftp, etc.. Try uninstalling such software.
The other problem could be that AD didn't uninstall properly, try reinstalling. -- this is weak of me, but??
-- Some tips: Finding the source of the problem.
If your workstations are getting their leases renewed every time you boot up, then DHCP is working - or a DHCP on the network is working. To find out more on where workstations are getting their IP leased from type IPCONFIG /ALL at command prompt (win 2k and XP) or RUN winipcfg in WIN98 and click on Show More >>
If you are not sure it's the Server or something else you can use the NET command to stop DNS and DHCP on the server from the command prompt. Type NET stop DHCP at a command prompt to stop DHCP. Restart or renew the IP at a workstation and see if it renews. If it does then you have another machine on the network causing the problem.
To restart DHCP type NET start DHCP ... and same with DNS.
I need to know more about your Network setup to give you better advice.
Such as number of machines, is there a router, number of servers, how they are networked ... etc. Don't give anyone or me info that can compromise your network such as IP addresses, but a general description.
Hope this helps.
- Thread starter
- #9
ciababy: Yeah, I use IP config regularly. Apparently, demoting the server from a domain controller back to a stand-alone server running a Workgroup was not seen by the
OS fully. However, this is interesting: the workstations are still getting DHCP service, although neither the DNS or DHCP services in the 2K Server are authorizing the server or showing proper configurations for the network workstations, etc. It's amusing. For instance, DHCP shows the server, but cannot configure scopes. Workstations are getting IP's and internet access. Velly Intellesting....I appreciate your advice on not to give out your network Id's. You're okay. I've got the network on a router, with the server set for DHCP. Funny, when the router was handling DHCP, it used to "hiccup" and put us down a LOT. When I set up the server to handle DHCP, the router has been stable ever since (more than 8 months). I'm just going to watch what happens for the next week, and if no "untoward" things occur (like losing internet connections on the workstations), I'm just going to leave "weird enough alone". Thanks for your consideration and assistance. You have a good attitude, something we need more of on the forums. whythisagainwhythisagainwhythisagain
OS fully. However, this is interesting: the workstations are still getting DHCP service, although neither the DNS or DHCP services in the 2K Server are authorizing the server or showing proper configurations for the network workstations, etc. It's amusing. For instance, DHCP shows the server, but cannot configure scopes. Workstations are getting IP's and internet access. Velly Intellesting....I appreciate your advice on not to give out your network Id's. You're okay. I've got the network on a router, with the server set for DHCP. Funny, when the router was handling DHCP, it used to "hiccup" and put us down a LOT. When I set up the server to handle DHCP, the router has been stable ever since (more than 8 months). I'm just going to watch what happens for the next week, and if no "untoward" things occur (like losing internet connections on the workstations), I'm just going to leave "weird enough alone". Thanks for your consideration and assistance. You have a good attitude, something we need more of on the forums. whythisagainwhythisagainwhythisagain
If you were using one of the SOHO routers, the hiccup probably came from when the leases were up. Have you verified that DHCP is no longer running on the router? "What do you EXPECT? It's
MICROS_ _T!" Have a good one, whythisagain....
Have you thought about Linux? I find it much more stable for servers than Windows... Thanks,
Matt Wray
MICROS_ _T!" Have a good one, whythisagain....
Have you thought about Linux? I find it much more stable for servers than Windows... Thanks,
Matt Wray
Of course the DHCP service is functioning. "Authorize" is no longer required because you no longer have AD. Read your help that comes with the server on the subject stopping rogue DHCP servers for the purpose of authorize (it requires AD). Without AD, no authorize is needed. As for DNS, check the settings on what type of zone it is. Without AD, you can only have a primary or secondary zone. Change it to a primary zone and make sure you have dynamic updates checked to YES so all your 2k pro's can register themselves in DNS. If you have 98's, NT's, etc, use the setting in DHCP to update DNS for those machines that do not support updating themselves.
- Thread starter
- #12
Before I promoted the server to a DC and then demoted it to a standalone server, DHCP could be configured to add scopes which stipulated functions and showed the workstations and server IP leases. Now it says it can't find the server, if I try to configure it, although the server is still featured therein. Well, as long as we're all still getting internet access, I see no reason to take down the whole server over this. DNS is configured properly. Thanks for your responses.
Mattwray: I've thought a LOT about Linux, but I can't afford to buy all the new programs and possibly hardware I'd need to install it on the entire network (as well as programs because our programs wouldn't work with it, either). I don't have DHCP enabled as a router function. I switched to using the server to provide DHCP, and haven't had a single problem with the router ever since.
Have a good day, kids. whythisagainwhythisagainwhythisagain
Mattwray: I've thought a LOT about Linux, but I can't afford to buy all the new programs and possibly hardware I'd need to install it on the entire network (as well as programs because our programs wouldn't work with it, either). I don't have DHCP enabled as a router function. I switched to using the server to provide DHCP, and haven't had a single problem with the router ever since.
Have a good day, kids. whythisagainwhythisagainwhythisagain
You could install Linux on your server and run Samba for windows clients. And if the command line is still difficult, as it is for me since I am still new to Linux, you can download Webmin from This is a graphical admin tool that can be run from a web browser amywhere on the network... Thanks,
Matt Wray
Matt Wray
- Status
Similar threads
