Home > Archive > 70-217 > June 2001 > Connecting a computer to a domain





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Connecting a computer to a domain
trebor

2001-06-10, 2:06 pm

Hi,

I promoted my server to be a DC in a new domain (dogbowl.com), the first one in the "forest" because it was a Workgroup before. Then I used AD Users and computers to make a computer account (newhope)and and a user account (Liam) (which I gave Domain Admin rights). But when I log on to the computer to change the membership from Workgroup to a Domain. It tells me the user name is not correct or that the parameters are not correct for logon.

I have tried logging on with every variant of the name (i.e. Liam, Liam@dogbowl.com, dogbowl/Liam, etc.) I haven't found anything on Technet or Windows Help Files that has helped.

Any friendly words of advice?

Trebor
dentonb2000

2001-06-11, 10:44 am

Can the client machine resolve dogbowl.com to the correct IP? If not, this would be a problem.
trebor

2001-06-11, 2:10 pm

Bless your heart Denton for answering my question.

Thje client can ping the server by the name and by the IP address. The DNS server seems in order.
dentonb2000

2001-06-11, 2:53 pm

As far as I know, you cannot log into the computer using a domain account unless the machine is a member of a domain within the same forest. Try logging in as Administrator and trying to change the domain. Provide the user name that you created when prompted.
trebor

2001-06-12, 1:21 pm

I have tried everything. These computers can see each other and there is no name resolution problem. I have tried using the Administrator account and also the "Liam" account which has Domain Admin rights.

I just keep getting error messages about "domain doesn't exist" or "you have no account in the Gooddog domain". I have run out of ideas. I think tomorrow I will start all over from the beginning.

Trebor
trebor

2001-06-13, 3:59 am

OK this morning I started over from, scratch. I demoted the server to a member server, I got rid of my DNS zones and DHCP scopes. I then ran DCPROMO made the new DNS zone and new IP scopes. Everything was fine until I tried to change the host to a domain member. I got the same error message.

I don't know if this is a clue or not maybe someone can interpret this warning in the Event Log.

"The redirector was unable to initialize security context or query context attributes." The times of these warnings seem to coincide with my failed logon attempts.

Trebor
Gigas

2001-06-13, 7:13 pm

Hi Trebor, I have not come across your specific problem before however I will give you a rundown on the procedure I use in the classroom every week. We have our students build a multi domain multi forrest envioronment at the end of their 2152 course and this method has not failed us yet. Famous last words

Step 1 MUST have ping connectivity.

Step 2 MUST MUST MUST have DNS working. All machines must be able to do both forward and reverse lookups for all other machines. Be aware of the difference between a DNS domain and an active directory domain which is what dcpromo allows you to create.
DNS domain is set on
(right click) My Computer->Properties->Network ID tab->Properties->more.
This is where you specify dogbowl.com on each machine and then setup DNS on your member server. Remember to set the option to allow dynamic updates to "yes".

Step 3 run Dcpromo and follow the bouncing ball.

If any of the steps is not working properly DO NOT PROCEED to the next step until it is.



Hope that helps.
trebor

2001-06-14, 12:15 am

Hi Gigas,

I am glad that you are on the case.

I found the problem addressed in an MS Knowledge Base article but there the problem was DNS too. I can ping the server using the IP address and by using the server name. I can even "see" the shares on the server using NET VIEW. The iterative query works too so I don't think DNS is the problem.

trebor
Gigas

2001-06-15, 7:27 am

Trebor just a thought, is your Liam account a member of the enterprise admins group?

I am not 100% sure but something tells me you need to be an enterprise admin to create a new domain, which if I read your post correctly is what you are doing.

This is something I should know off the top of my head (being a trainer) but there is so much to learn that sometimes info gets pushed aside to make way for fresh knowledge.

Just trying to help
trebor

2001-06-16, 8:03 am

Good question. I already thought of that and I made Liam a member of the domain users, domain admin, and enterprise admin groups.

trebor
Gigas

2001-06-16, 8:41 am

DOH !!!

Oh well it was worth a try.

You say you can ping by name, can you do an nslookup for the server? and for the client?

DNS is critically important in win2k, everything is found via srv records on the DNS server. I have had many twighlight zone type of problems turn out to be DNS related.

A classic example was once when trying to map a drive I got an error "your credentials clash with an existing set of credentials on the network". I even tried creating a new user with full admin priveleges and got the same message. It turned out to be an incorrect entry for the DNS server in the ip properties of the client.

Keep on persevering mate, what does not kill you can only make you stronger.

trebor

2001-06-16, 12:17 pm

I tried reinstalling Win 2K and setting up everything from scratch on my "client" machine. And ran into another problem which I posted on Freak's site. Here it is.
---
"Has anyone had this problem? I have used a Beta Version of W2K Pro for about 6 months. I have installed it and re-installed it many times. Today I de-installed W2k tried to re-install but it stops with the error
"The (FloppyFiles.2) of the Setup.inf file is missing or corrupt. Setup cannot continue.""
---

Anyway I re-formated the HDD and now the installation is working. I will get back to you when the machine tries to connect to the domain.
trebor

2001-06-16, 3:26 pm

It worked. Unfortunately, I don't know why it worked. I supplied the exact same information during the installation that I supplied when trying to change the workgroup to a domain client.

Thanks for all the input Denton and Gigas.

trebor

PS: could it have anything to do with that corrupt setup information file?
Sponsored Links





Free Braindumps | MCSE braindumps software forum

Copyright 2003 - 2008 examnotes.net