|
Problem description: We have a small office with 8 computers on the same domain, and a server with Active Directory. Everything was working fine, until... I reset my password via Active Directory, but when I log into the domain on my computer, I can only get on with my old password. However, once I'm in, if I try to access a shared folder on that same server, it only accepts the new password. Only my computer is having this issue, so far. Attempted fixes: Reset the password again, reset the account. Recent changes: I think someone might've accidentally removed some programs that come with Windows Server 2003, I don't know what though. I also can't find a list of what programs come with Server 2003. -- Operating system: My computer is Windows 7 SP1, Server is Windows Server 2003 x64 SP2 System specs: My computer can actually sing because it is Adele; a Dell Optiplex 320 to be specific. Server also sings as a Dell Poweredge 1950 Location: USA I have Googled and read the FAQ: Yes
|
#
?
Jun 26, 2015 18:26
|
|
|
|
| # ? Apr 25, 2024 18:30 |
|
|
Three initial things to try: -Reboot the server if it hasn't been done lately. -Disjoin the domain (from your computer) and then rejoin it. -If that doesn't change anything try deleting the computer from within active directory and then rebooting your local computer.
|
|
#
?
Jun 28, 2015 04:43
|
|
|
Zogo posted:Three initial things to try: When I disjoined the domain, and tried to rejoin it, it gave me the error: could not find Active Directory Domain Controller for the domain 'future' Other computers that have always been connected to it have no problems, but apparently I can't add a new computer to the domain. I tried "FUTURE" and 'future.lcl' for the domains, and they are DEFINITELY the only two that would work and not misspelled. Also, I can ping the server and the server can ping me.
|
|
#
?
Jul 6, 2015 21:12
|
|
|
jryan42988 posted:...apparently I can't add a new computer to the domain. Is there someone around who has an admin account? Only certain users may be able to join it. Also, did you remove the computer account (not the user account but the computer name) from within AD itself?
|
|
#
?
Jul 7, 2015 00:42
|
|
|
Zogo posted:Is there someone around who has an admin account? Only certain users may be able to join it. I don't even get to the point where it asks me for an admin username/password, it says it can't find the AD DC at all. I believe I removed the computer account from AD, but will double check and update tomorrow.
|
|
#
?
Jul 7, 2015 22:06
|
|
|
I deleted the computer from the AD, tried again, but to no avail. The full error message is... quote:"An Active Directory Domain Controller (AD DC) for the domain "FUTURE" could not be contacted. When I click details... quote:"Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\Windows\debug\dcdiag.txt.
|
|
#
?
Jul 8, 2015 14:22
|
|
|
Try this: http://geekswithblogs.net/technetbytes/archive/2011/10/09/147233.aspx
|
|
#
?
Jul 9, 2015 04:52
|
|
|
Okay, so at first this didn't help, but after working on it for a while and restarting the server again, it now prompts me for admin credentials, but then I get the error... "The following error occurred attempting to join the domain "FUTURE": An attempt to resolve the DNS name of a domain controller in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain. For information about network troubleshooting, see Windows Help." Also... when I try to add a new computer on AD, I get an error "the directory service was unable to allocate a relative identifier" DJcyclopz fucked around with this message at 19:44 on Jul 9, 2015 |
|
#
?
Jul 9, 2015 16:19
|
|
|
It's been years since I had to deal with Active Directory, but could you static-set the IP address of the client machine and set the DNS to the server? Also, isn't one of those DNS servers Google? Is that intended?
|
|
#
?
Jul 10, 2015 01:56
|
|
|
Tried all of those things I'm pretty sure this problem is centered around the other error I was getting: "the directory service was unable to allocate a relative identifier" I get that error when I try to manually add a new computer to active directory. Aghhh any idea what I should do from here? google has not helped much
|
|
#
?
Jul 20, 2015 15:49
|
|
|
jryan42988 posted:I get that error when I try to manually add a new computer to active directory. Was the server configured so that a computer would have to be manually added like that? Because that's not the normal requirement. Have any other computers/laptops that aren't joined to the domain? If so, try to join on one of those. Broadly that would at least tell us if it was a computer issue or a server issue.
|
|
#
?
Jul 21, 2015 03:58
|
|
|
Zogo posted:Was the server configured so that a computer would have to be manually added like that? Because that's not the normal requirement. Tried with another computer, same error. I had a feeling that would be the case since it asks me for credentials before giving me that error. Also, I just learned that 8.8.8.8 is the only DNS server that is working correctly. So now I know it's definitely a DNS server issue, but still don't know how to troubleshoot from here.
|
|
#
?
Jul 21, 2015 21:22
|
|
|
|
| # ? Apr 25, 2024 18:30 |
|
|
jryan42988 posted:Tried with another computer, same error. I had a feeling that would be the case since it asks me for credentials before giving me that error. Also, I just learned that 8.8.8.8 is the only DNS server that is working correctly. So now I know it's definitely a DNS server issue, but still don't know how to troubleshoot from here. Were the 10.200.221.136, 10.200.221.133 IP addresses given to you from the ISP? I wonder if there's been a change with them recently. It would help to know the network topology. Are there other routers or servers on the network or just the domain controller?
|
|
#
?
Jul 22, 2015 00:12
|
|