Just error codes isn't gonna help. "Enough, enough bowing down to disillusion! Hats off & applause to rogues & evolution! The ripple effect is too good not to mention. If you’re not affected, you’re not paying attention!"

0

Domain Controller Diagnosis Preforming initial setup: Done gathering initial info. Doing initial required tests Testing server: Default-First-Site_Name\SERVER Starting Test: Connectivity ......................... SERVER passed Connectivity Doing Primary Tests Testing server: Default-First-Site-Name\SERVER Starting test: Replications ......................... SERVER passed Replications Starting test: MCSecDesc .........................SERVER passed MCSecDesc Starting test: NetLogons [SERVER] An net use or LsaPolicy operation failed with error 1231, The network location could not be reached. For more information about network troubleshooting, see windows help.. .........................SERVER failed test NetLogons Starting test: Advertising .........................SERVER passed test Advertising Starting test: KnowsOfRoleHolders .........................SERVER passed test KnowsOfRoleHolders Starting test: RidManager .........................SERVER passed test RidManager Starting test: MachineAccount Could not open pope with [SERVER]:failed with 1231. The network location cannot be reached. For information about network troubleshooting, see Winsows Help. Could not get NetBiosDomainName Failed can not test for HOST SPN Failed can not test fir HOST SPN * Missing SPN :<null> * Missing SPN :<null> .........................SERVER failed test MachineAccount Starting test: Services Could not open Remote ipc to [SERVER]:failed with 1231: The network location cannot be reached. For information about network troubleshooting, see Winsows Help. .........................SERVER failed test Services Starting test: ObjectsReplaced .........................SERVER passed test ObjectsReplaced Starting text: frssysvol [SERVER] An net use or LsaPolicy operation failed with error 1231, The network location cannot be reached. For information about network troubleshooting, see Windows Help. .........................SERVER failed test frssysvol Starting test: frsvent .........................SERVER passed test frsvent Starting test: kccevent Failed to enumerate log records, error The network location cannot be reached. For information about network troubleshooting, see Windows Help. .........................SERVER failed test kccevent Starting test: systemlog Failed to enumerate log records, error The network location cannot be reached. For information about network troubleshooting, see Windows Help. .........................SERVER failed test systemlog Starting test: VerifyReferences .........................SERVER passed test VerifyReferences Running parition tests on : ForestDnsZones Starting test: CrossRefValidation .........................ForestDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom .........................ForestDnsZones passed test CheckSDRefDom Running partition tests on : DomainDnsZones Starting test: CrossRefValidaion .........................DomainDnsZones passed test CrossRefValidation Starting test: CheckSDRefDom .........................DomainDnsZones passed test CheckSDDefDom Running patition tests on : Schema Starting test CrossRefValidation .........................Schema passed test CrossRefValidation Starting test: CheckSDRefDom .........................Schema passed test CheckSDRefDom Running partition tests on : Configuration Starting test: CrossRefValidation .........................Configuration passed test CrossRefValication Starting test: CheckSDRefDom .........................Configuation passed test CheckSDRefDom Running parition tests on : scouts Starting test: CrossRefValidation .........................scouts passed test CrossRefValidation Starting test: CheckSDRefDom .........................scouts passed test CheckSDRefDom Running tests on : scouts.local Starting test: Intersite .........................scouts.local passed test Intersite Starting test: PsmoCheck .........................scouts.local passed test PsmoCheck You better like that- I did it all by hand :\

0

LOL... you know it can generate a log for you... "Enough, enough bowing down to disillusion! Hats off & applause to rogues & evolution! The ripple effect is too good not to mention. If you’re not affected, you’re not paying attention!"

0

Every one of the errors you indicated keeps coming back to this KB article... http://support.microsoft.com/kb/257623 But this doesn't sound applicable to you. Two questions... A. Is NetBIOS over TCP/IP turned on the DC? B. Did you ever change the domain controller's IP after you promoted it to a DC? "Enough, enough bowing down to disillusion! Hats off & applause to rogues & evolution! The ripple effect is too good not to mention. If you’re not affected, you’re not paying attention!"

0

A) How would one check if NetBIOS is over TCP/IP on the DC? B)No, I hav e not changed the IP of the DC- its always been static, as far as I can tell.

0

"How would one check if NetBIOS is over TCP/IP on the DC?" Under WINS tab under advanced settings for TCP/IP of your NIC. "Enough, enough bowing down to disillusion! Hats off & applause to rogues & evolution! The ripple effect is too good not to mention. If you’re not affected, you’re not paying attention!"

0

Under the WINS Tab, it lists "192.168.0.1" as the WINS address. That is the address of the server.

0

What does that have to do with checking if NetBIOS over TCP/IP is enabled? "Enough, enough bowing down to disillusion! Hats off & applause to rogues & evolution! The ripple effect is too good not to mention. If you’re not affected, you’re not paying attention!"

0

Its on the Default setting: Use NetBIOS setting from the DHCP server. If Static IP address is used or the DHCP server does not provide NetBIOS setting, enable NetBIOS over TCP/IP

0

Is the Windows Firewall enabled on the DC? "Enough, enough bowing down to disillusion! Hats off & applause to rogues & evolution! The ripple effect is too good not to mention. If you’re not affected, you’re not paying attention!"

0

No, the firewall has been disabled.

0

Hi heropsycho2177, You are asking to many useless question, if you're intending to help the guy, then do so otherwise do not lead him up the garden path! You didn't even ask what os is he using in the client computers, to justify the use of WINS. And what about the Suffix, is the AD installed and configured correctly and the updates turned on. Networking is not dificult but then again simple mistakes are common and the system will not work. First of all, why are you using WINS if you're using the WIN 2000 on all your clients? You only use WINS on pre 2000 OS.

0

Instead of pointing out mistakes of someone else's, could we try to fix mine first? :P I'd like to get this solved before Monday.

0

Hmm, I think you are fighting a losing battle! Too many errors! I would start again preferably with a new image, step one would be to assign IP addresses and make sure they all have the same Subnet Mask! All client machines as a "prefered DNS" will be pointing to the DC machine! Second step they are all in the same Workgroup, they all have their own unique name (eg. "Server1, Server2, Client1, Client2 or similar! at the same time I would add the Suffix "MyCompanyName.com" or something similar! Step three, since you're using Switch make sure all computers are plugged into the switch and you're using the right cables (straight). You should be able to ping all computers, if you can't don't worry about DNS, you should be able to ping before you even start thinking about starting with the DNS. OK, you can ping! To configure DNS you can either do it while configuring dcpromo or do it separately by opening up DNS Admistrative Tools (if DNS is not installed, either ways you'll have to install the DNS first and this is done by going to - Control Panel, Add/Revive Programs and then Add/Remove Windows Components. Then find and install the DNS) but it may ask you for the OS CD! If you chose to configure the DNS first you'll have to run and configure the DCPROMO (AD) after, however you may choose that the DCPROMO do that for you Automatically. Note: I always install DNS first and do my own configurations! After you configure the DNS and run DCPRono (while configuring the DCPromo I would select the "Native Mode" it's easier since you're using Win 2003, Win 2000 or XP and you don't have Pre 2000 OS like Win 95 Win 98 ) make sure the DNS is Active Directory Integrated and allow Dynamic updates. Check the Forward and the Reverse Lookup zones and their pointers and that the DNS is started and that all the folders are there and visible! If I'm not missing anything at this point you should be able to add all the Client machines to your Domain. R/click on my Computer then click on Properties you should see the fully qualified name on you DC (eg. DC1.MyCompany.com), if that's the case then half of the job is done! As you can see there is no WINS, there's no need for WINS! WINS is Dinosaur, I feel sorry for people who still stuff around with WINS! OK everything looks good so far! And heropsycho2177 you or someone else take over from here!

0

TbG, you can disregard this post, I gotta bring out the sledgehammer on this guy. My advice to you is next. "You didn't even ask what os is he using in the client computers, to justify the use of WINS." When did I say anything about WINS?! "You didn't even ask what os is he using in the client computers" That's because unlike you, I can read... "7 Dell Optiplex GX110 (Clients) -128mb RAM -667mhZ p3 -6gig HDDs -Windows 2000 Professional SP4" "And what about the Suffix, is the AD installed and configured correctly" Do you even know what DCDiag does? It checks to see the health of AD. Should there be problems with AD, DCDiag would be the most likely to find it, which it did. It identified problems with NetBIOS, and the ability to make RPC connections to the DC. "You only use WINS on pre 2000 OS." Experienced network engineers know that's not true, although that has nothing to do with this situation. Please, go actually support and admin for example a remotely large Exchange 2000/2003 environment, even with all Windows 2000 and XP clients, and let me know how it goes without using WINS. As for the relation to NetBIOS over TCP/IP, had you read the output of his dcdiag test, you'd have seen this... "Could not get NetBiosDomainName" Please actually read before spouting out nonsensical BS about how I ask too many questions your brain deems useless. Just because you've studied or may have even passed a few MCP exams, it doesn't mean you are an AD god. I say this because you name just about everything the textbooks say to do, but you didn't even know about dcdiag, nor the practical uses of WINS the books don't tell you. "And heropsycho2177 you or someone else take over from here!" Yes, run along. "Second step they are all in the same Workgroup" Wrong, that may actually cause an issue if anything. Don't name the domain and whatever workgroup the same thing. And whether or not all the machines are on the same workgroup before you even dcpromo is completely irrelevant and unnecessary. Also, you seem to think AD integrated DNS and dynamic updates are a good thing, yet no mention that you need a windows DHCP server for this. "Enough, enough bowing down to disillusion! Hats off & applause to rogues & evolution! The ripple effect is too good not to mention. If you’re not affected, you’re not paying attention!"

0

TbG, you have two choices... #1. Fix the current deployment. You have RPC, IPC issues, and NetBIOS issues. All research of those messages are not turning up any info that I've seen on the internet, aside from hotfixes should they happen on Windows 2000 SP4 as the DC. Since you're using Windows 2003, that's not the solution. I don't know what else to tell you to try at this point. If someone else has any ideas, you could wait for someone to post with a possible solution. Hopefully it won't be someone else who is more eager to point out other supposed mistakes in attempting to help instead of actually helping. #2. Redeploy. I would recommend the following procedure. 1. Disjoin all computers from the current troubled domain. 2. Reinstall the OS on the DC server. Install W2K3 SP1 and all critical updates. 3. Configure the server to use its actual IP as its sole DNS server. 4. If you are using a SOHO router, disable the DHCP server in it. 5. DCPromo the box. Allow DCPromo to take care of DNS for you since this is your first time deploying DNS. Configure it to allow dynamic updates. 6. In this case, choose Native mode. 7. When choosing the netbios domain name, just use the first part of your fully qualified domain name. IE, if it's test.local, use "TEST" as the NetBios domain name. 8. If you want, you could create reverse lookups. It's not necessary for what you're doing, but it would be best practice in a production environment. 9. If these computers connect to the Internet, be sure to set up Forwarding in your DNS server for your ISP's or upstream DNS server, whichever is applicable to your environment. Test DNS using NSLookup. 10. Normally, you would set up WINS in a production environment, especially if you have Exchange or clients who need to VPN from the internet and access file shares. In this case, you probably don't have to. However, your internal clients and servers should all be set to enable NetBIOS over TCP/IP. 11. Run NetDiag and DCDiag again and verify there are no errors. That's the proper way to ensure "all the folders are there" for DNS Jax5 said to do. Correct me if I'm wrong, but since those records can be pretty confusing for a novice, wouldn't you agree that you wouldn't know what to look for? DCDiag and Netdiag would be more likely to identify the problem because they eliminate human error, and they're programmed to know what records are needed. 12. Install DHCP on the DC, and set the scope options up properly. Be sure DHCP gives clients their DNS server as the DC's IP. Make sure you authorize the DHCP server in AD as well. 13. Reboot each client, and ensure they are getting the proper IP settings from your Windows DHCP server. Ensure all computers can ping the DC, and they are configured to use the DC as their sole DNS server. Test name resolution using nslookup. 14. Join the clients into AD using the NetBIOS domain name. Verify each shows up within AD Users and Computers. Reboot the client. You should then be in business! "Enough, enough bowing down to disillusion! Hats off & applause to rogues & evolution! The ripple effect is too good not to mention. If you’re not affected, you’re not paying attention!"

0

Although the last post is interesting and I do not agree with everything, but that's me, at least TBG has some procedure to follow! As for DCDiag that's one of the tools you can use but I don't, I don't have to not for a simple set up as this one. And for 1.) "When did I say anything about WINS" The moment I see the word "WINS", the first thing I would ask about the list of operating systems. Isn't that logical???? 2.) "Could not get NETBios" Well doesn't that point to either DNS or the DCPromo stuffup somewhere along the line. And yes Suffix! You don't enter the suffix It's not gonna work. That's as simple as that. That's mostlikely his problem! 3.) " Second step they are all in the same Group" OK put them all in different group and try to ping! The default is "Workgroup" and you shouldn't touch this while you're setting up! Now I have never worked in a large exchange environment (I assume we're talking about the Mail Exchange Server) but had no problems installing Exchange Server in Native Mode. Then again TBG's environment doesn't seem to be large so why would he wanna use WINS, that beats me! Now I have to "run along" because heropsycho2177 said so!

0

"The moment I see the word "WINS", the first thing I would ask about the list of operating systems. Isn't that logical????" It's absolutely logical if you've only learned from books and don't have real world experience. "Well doesn't that point to either DNS or the DCPromo stuffup somewhere along the line." No. "Now I have never worked in a large exchange environment (I assume we're talking about the Mail Exchange Server) but had no problems installing Exchange Server in Native Mode. Then again TBG's environment doesn't seem to be large so why would he wanna use WINS, that beats me!" I never said he needed WINS. I don't know where you got that idea. I said NetBIOS over TCP/IP should be enabled. READ! As soon as you saw the word WINS, you assumed I was saying setup WINS. I said that is the tab where you enable NetBIOS over TCP/IP. It would be nice if you actually read someone's post before you criticized them. "Now I have never worked in a large exchange environment (I assume we're talking about the Mail Exchange Server) but had no problems installing Exchange Server in Native Mode." You can choose not to follow best practices from Microsoft. Go ahead and have Exchange deployments that don't work right! http://support.microsoft.com/kb/837391 "As for DCDiag that's one of the tools you can use but I don't, I don't have to not for a simple set up as this one." Ok, don't follow best practices. Doesn't matter to me. I SPOT A TREND! "Enough, enough bowing down to disillusion! Hats off & applause to rogues & evolution! The ripple effect is too good not to mention. If you’re not affected, you’re not paying attention!"

0

"I said NetBIOS over TCP/IP should be enabled. READ! As soon as you saw the word WINS, you assumed I was saying setup WINS. I said that is the tab where you enable NetBIOS over TCP/IP." It is not often that you have to disable the NETBIOS and certainly not if you're trying to configure DNS or the Active Directory. As I said earlier most likely he didn't enter the Suffix. Or the DNS wasn't started! (providing everything else was 100%) You look like an expert in Win 3.1, refresher course in Win 2000 and 2003 would do you good! Between you and TbG the word WINS was mentioned 4 times and you didn't question once why WINS? Also turning on the dynamic updates and having the DNS being AD integrated is security issue and it's got little to do with the DHCP! You can give all your Clients static IP if you like in a small LAN environment. AD will be very useful with the DFS, Group Policy etc. Exchange Server can be placed in the DMZ . That's the main reason for having the Dynamic updates enabled and the DNS being AD integrated. However! Enough said!

0

"It is not often that you have to disable the NETBIOS and certainly not if you're trying to configure DNS or the Active Directory." I didn't say disable NetBIOS over TCP/IP. I said make sure it's enabled. Again, reading comprehension would do you good. "You look like an expert in Win 3.1, refresher course in Win 2000 and 2003 would do you good!" I've designed and supported Windows 2000/2003 solutions for over six years, and I'm an MCSE 2000/2003. I also supported Exchange and Active Directory for Premier Microsoft Product Support. Might want to work on how you perceive the world because the gap between reality and your perception of it is enormous. "Between you and TbG the word WINS was mentioned 4 times and you didn't question once why WINS?" WINS was only brought up in reference to how to enable NetBIOS over TCP/IP. Again, had you read the thread, you'd have known that. You are aware that you enable NetBIOS over TCP/IP on the WINS tab, right? DUUUUUUH! Show me where I told him to setup WINS in this thread. It doesn't matter how many times "WINS" appears in this thread. Had you actually not been lazy and read the thread before posting, you'd have known that. "Also turning on the dynamic updates and having the DNS being AD integrated is security issue and it's got little to do with the DHCP!" You didn't tell him to statically assign IP's to his clients. And now to address the unrelated gibberish you typed at the end... "You can give all your Clients static IP if you like in a small LAN environment. AD will be very useful with the DFS, Group Policy etc. Exchange Server can be placed in the DMZ . That's the main reason for having the Dynamic updates enabled and the DNS being AD integrated." You didn't say give all your clients a static IP until now. What Exchange has to do with this is beyond me. On top of that, it sounds like you think the Exchange Server for an organization (that would be a backend server since you have to have at least one backend) can and should be placed in a DMZ. There's no point in arguing that with you because you're completely clueless if you think a backend server should be there. That would give anyone with any Exchange experience a heart attack upon hearing it, and it goes against basic security principles, Microsoft best practices, and required knowledge to pass any Exchange MCP exam. Finally, the main reasons to have DNS to be AD integrated is for security concerning DNS records, which can help prevent DNS poisoning, and because AD integrated DNS can be more efficiently transferred using AD replication technologies. That has nothing to do with "DFS, Group Policy etc." http://www.microsoft.com/technet/pr... Do you really want to continue this? "Enough, enough bowing down to disillusion! Hats off & applause to rogues & evolution! The ripple effect is too good not to mention. If you’re not affected, you’re not paying attention!"

0

I feel sorry for people having to work with you, if I didn't know what I was talking about you'd brain washed me with that nonsense! Before you start doing any work for other people you need to know how to install the three basic services DNS, AD and DHCP! Right? Then how to apply the Group Policy, and only then you install other services for which people are hiring you for, services like the Mail Exchange, DFS, Web Server etc. Right? But you're all over the place! No logic! You need to learn the basic stuff first! TbG where did you find this psycho to help you with your Networking, make sure you don't disagree with him he might hit you with a sledge hammer!

0

I work great with other people who are peers and treat me with respect. You're not my peer, and you certainly didn't from the get go treat me with common respect. "if I didn't know what I was talking about you'd brain washed me with that nonsense!" Which one of us backed up what we said with facts and articles from Microsoft? That would be me. I also don't take crap from someone who comes into a thread and blasts me for things I didn't even say. Yeah, I did hit you with a sledgehammer! Thanks for at least recognizing you got schooled. :-) "Enough, enough bowing down to disillusion! Hats off & applause to rogues & evolution! The ripple effect is too good not to mention. If you’re not affected, you’re not paying attention!"

0

OK, you're an easy going, good and honest friendly type of guy, I can see this, you might even be good looking but that's beside the point! You'll still have to learn when to use WINS and when to use DNS, they will perform similar tasks, but one is used in some circumstances and the other in another. Didn't they teach you this in your "MCSE 2000/2003" course? Or you must have used different books, yours must have had some pornographic material, (extra work)! I hear the 2 day Networking courses are great, they supply you with all this! Therefore next time you see someone mentions WINS, before you start asking tons of useless questions and lead the other guy "up the garden path" find out why WINS, after all we're in 20th century!

0

We're in the 21st century. Your brain is evidently not Y2K compliant. As for WINS, look at the article I linked you to concerning NetBIOS and Exchange. One would think you'd have at least realized by now that your statements claiming WINS is never needed with Windows 2000/XP/2003 clients and servers is false. But alas, you don't learn, and you apparently never will. "Enough, enough bowing down to disillusion! Hats off & applause to rogues & evolution! The ripple effect is too good not to mention. If you’re not affected, you’re not paying attention!"

0

Unfortunately hero likes to argue with other posters. Tbg - Your DC should point to itself as preferred DNS server. Remove 127.0.0.1 and put in the IP address of the server. So the servers IP address and the Preferred DNS server will be the same. This is all assuming the DC is also the DNS server. The clients should also point to the DC as their Preferred DNS server. Make sure in the Properties if TCP/IP that this information is entered and correct. You do not need WINS in an Active Directory domain unless you have some old clients or applications that need it. Active Directory does not require WINS. Don't waste your time with it. So make sure all your clients have proper IP address and subnet masks as Jax suggests. Make sure they have the proper DNS settings and make sure your DC is functions properly and also has the proper IP settings and is pointing to itself for preferred DNS. Have you made any progress with this so far?

0

"Unfortunately hero likes to argue with other posters." With all do respect, I wasn't the one who started the argument, and I didn't come in to this thread insulting other people. I'm here to help. Glen also has a tendency to come in and post to correct things that don't need to be corrected, and gets an attitude when someone calls him on it. Neither here nor there... I received a PM from the original poster and am helping him via instant messaging. If the solution is found, either the original poster or I will post back. "Enough, enough bowing down to disillusion! Hats off & applause to rogues & evolution! The ripple effect is too good not to mention. If you’re not affected, you’re not paying attention!"

0

You are helping him? Are you making any progress? And whatever you do, do not use that hammer on Tbg's Computers! It won't work!

0