I have some major problems between Active Directory and DNS. Is it better to have a full understanding of AD befor going on to DNS or doesn't it matter? I find both hard to learn.
They can be tricky. Think of it this way... AD needs DNS for naming and tracking network clients/servers. You really can't know one without the other. You can, but if something fails, then you're going to have a really hard time. Ya' really need to know them both.
What's your problems? Have you run any event ids' through technet?
You have to have DNS to install AD, but DNS is integrated with AD...chicken or egg.
I would suggest removing AD (dcpromo again), uninstall DNS completely (Add/Remove Windows Components). Then run DCPROMO, and it will error that it needs a DNS server and ask if it can install it for you (say YES!) Now you should have a working AD with integrated DNS.
Messing around with AD and DNS scares me a bit. This server has an outside line behind a firewall, and is partialy on line as an SQL server, with a specific domain setup schema per a customer spec. I feel I need to learn more about AD and DNS befor I start fooling around. I just didn't know where to start.
Running dcpromo caused other remote applications not to work anymore (the boss was not impressed)and I am trying to figure out how to get it back (i.e. remote admin console).
At this point a fresh install may be the best idea (or restore from a backup made before you started...)
There are always those leftovers when you make changes. Like when you uninstall DNS, then reinstall it and find it has all those records you had entered a month ago!
Restore the server from tape or re-install from scratch.
If you fresh install when it first boots tell it to be an AD server, let it install DNS, then get your SQL disk out and set that up. Now you can carefully document each thing that you do and track what happens.
Reminisce mode...
When I first started with Win2k (after 5 yrs of NT4) I bought a junk computer from yard sale, installed Win2k Server and setup a whole AD domain one service at a time. I used a DNS2GO name, had authorative DNS, VPN, RIS, different OU and went all out (took like 50 re-installs to get all to work like it should.) Then I went to my first Win2k customer and installed his network exactly like I had done on the junk computer, just not doing those things he didn't need/want.
Depending on your backup software you may be able to make a boot floppy and the restore the whole system from that tape. Or you will have to re-install Win2K Server from scratch then insert tape and restore all files including system state backup. In this case be sure that the backup program puts the files back in their original location and overwrites files that are already there.
What's going on with the server right now. Is it working?
Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884
"Action is the proper fruit of knowledge."
Thomas Fuller (1610-1661); English scholar, preacher
Whats in your log files? Anything showing you the failures so we can search the event id's? Good luck.
Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884
"Action is the proper fruit of knowledge."
Thomas Fuller (1610-1661); English scholar, preacher
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.