Working on this computer remotely in my company, it has more than one problem but right now we are focusing on trying to re-join it to the domain. We removed it first off to see if it would fix the trust relationship issues it was having along side not being able to browse the network files of any computers or servers.
When attempting to join the domain this is what we get in the dcdiag. If this is the case, verify that the domain name is properly registered with WINS. They are updated by the AD DC at set intervals. I've been working on this computer for about 2 days, and while the user is able to work remotely through a terminal server, they are going to need to get access to the server eventually.
This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Report abuse. Details required :. Cancel Submit. Shenan Stanley.
You can create the computer account in AD before adding the computer to the domain, with the computer name you want it to have. Create the computer account in the appropriate OU then reset the account.
When you add the computer to the domain from the computer's end, it will prompt for your domain credentials, make sure that the account you use has domain admin or account operator privileges.
Carlson's right, make sure the time isn't bunged up. Yup - if the time is out Kerberos authentication will fail. I always forget the time one, usually I'll double check the clock and adjust it without thinking about it that's how used to it I am. Are you connecting to your network via wireless or cable?
As wireless can cause problems with domains and logging in. I uninstalled all the patches installed yesterday, though there were 4 that I couldn't remove. They were related to MS office and Visio. I also uninstalled the antivirus program from the machine. I set it to automatic and then tried to start it. It says it started then stopped, so I rebooted. It was still not "started" after the reboot. Looking in the event viewer, it says that it was stopped because the machine is in a workgroup and this service is not required in that configuration.
I also tried the reboot, change computer name, reboot and attempt to add to domain with no luck. CarlsonER - Yes. I am logged on the local with the local admin and trying to use domain adim to join to the domain. I don't know what it was The computer Gods were mad at me for something and now all is right with the world. Thanks to everyone again for the suggestions. One of them worked, but I can't say which one directly!!! Best answers chosen based on the last three things I did : That's the best I can do.
I wanted to add that "Mapping a network drive" actually fixed the issue for me. I was able to join the domain after that.
Pacific Innovations is an IT service provider. Make sure you can ping the domain, e. Try manually creating the computer account in Active Directory first, and wait a few minutes for replication to take place. To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. I'll also remember to turn on system restore before I do anything : Looking for anything that might get me out of doing this all over again.
Best Answer. View this "Best Answer" in the replies below ». Popular Topics in General Networking. Spiceworks Help Desk. The help desk software for IT. Track users' IT needs, easily, and with only the features you need. Learn More ». Magnus Aug 29, at UTC. Jason Aug 29, at UTC. Ripper Aug 29, at UTC.
Hope this helps, sorry to hear of your troubles! Rockn This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. Have you removed the computer object from AD prior to attempting to join the domain again?
Thai Pepper. CarolB This person is a verified professional. Lots of ideas so far. That was quick : Magnus - I already tried uninstalling the patches, but I am unable to get into the system using the previous account. Thanks for the suggestion!
Fanatik Aug 29, at UTC. This may not be your problem but does sound like it. Magnus Aug 30, at UTC. Magnus wrote: geez- I can't believe I forgot that one. I always forget the time one, usually I'll double check the clock and adjust it without thinking about it that's how used to it I am edit: had to fix an auto-correct that snuck in. Hi Carol Are you connecting to your network via wireless or cable? I was able to map a network drive.
And the time is the same as my other machine. Brevity - I tried both wired and wireless Check if the computer account already exists in the AD - if so delete it. This is especially true if it's a multi-site AD deployment.
