Active Directory issues with new W2K3 server
Just installed a new W2K3 server. Have 2 XP Pro workstations that joined the domain fine. Setup DNS, DHCP, WINS on the server. XP Pros are pulling all settings from server verifying the information in the scope is correct & that the W2K3 server is listed as the first DNS server. No modifications to GPO.
Upon joining the domain tried to do the following:
1. Add Domain Users to the Local Administrators folder. Unable due to the domain not being present in the locations list. Only the local accounts / computer showed up in locations.
(WORKAROUND: Used AD on server to "manage" the workstations and add the account this way.)
2. Add Network Printer which was installed and shared (check that it be included in the AD) but from the workstations can not see anything listed in the AD. If try Option 2 in installing the printer, printer shows up under the server.
Question: Are these two issues interrelated with AD on the server or is it a DNS issue? What is the fix to correct this? Don't want to blow away the DNS or AD if we don't have to.
Thoughts?
Rpierce1373
Upon joining the domain tried to do the following:
1. Add Domain Users to the Local Administrators folder. Unable due to the domain not being present in the locations list. Only the local accounts / computer showed up in locations.
(WORKAROUND: Used AD on server to "manage" the workstations and add the account this way.)
2. Add Network Printer which was installed and shared (check that it be included in the AD) but from the workstations can not see anything listed in the AD. If try Option 2 in installing the printer, printer shows up under the server.
Question: Are these two issues interrelated with AD on the server or is it a DNS issue? What is the fix to correct this? Don't want to blow away the DNS or AD if we don't have to.
Thoughts?
Rpierce1373
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Here is my second choice:
https://www.experts-exchange.com/questions/23356031/There-are-currently-no-logon-servers-available-to-service-the-logon-request.html
MANY things can cause this issue, mostly all related to DNS. So, any event log errors or DCdiag errors are helpful. Expect a possible long troubleshoot with a quick fix.