//flex table opened by JP
PDA

Click to See Complete Forum and Search --> : W2K AD Admin tools problem...

mcseguy9
02-22-2002, 03:29 PM
We just upgraded all of our users to W2K Pro and have upgraded our PDC to W2K Server and have implemented AD. 3 of us have installed the W2K support tools to include the AD Users and Computers icon in the Administrative Tools folder in the Programs menu. Only 1 of us can click the icon and connect to the new AD server and view the users and computers. Here's the error message I'm receiving:

***Naming information cannot be located because:
The server is not operational
Contact your system admin to verify that your domain is properly configured and is currently online.***

The 2 of us who cannot connect are getting that error message. We don't know what's causing it. Once we click the OK button the AD Users and Computers window opens up but we aren't connected to anything. When we try to connect to the AD server we get teh same error message.

I'm totally new to AD and have no clue what's wrong. Any help would be great. Thanks.
BipolarBill
02-22-2002, 05:43 PM
I assume that all three of you are Administrators. Are you logged on locally or on the domain?
mcseguy9
02-25-2002, 09:42 AM
Sorry it took so long for me to reply. Let's see, one of us is an admin on teh network and the other two are domain admins. The admin himself can't get connected, but one of the domain admins can and the other can't. Interesting, eh? We are all logged onto domain and, not that it matters, I'm sure, we are all in teh admin groups on our PC's. Thx for the help.
BipolarBill
02-25-2002, 10:46 AM
Make sure that the ones who cannot connect are added to the respective PCs and Servers as Local Admins.
mcseguy9
02-25-2002, 11:19 AM
I added myself to the built in (local) admin group and tried it again. It didn't work. Was there more to it than that? Thx.
BipolarBill
02-25-2002, 11:59 AM
I'm officially stumped. This has me thinking:

***Naming information cannot be located

that it's a DNS problem.
mcseguy9
02-25-2002, 02:19 PM
out of the 3 of us, the one who can get in doesn't have proxy client (WSP) installed. the other 2 of us do. it appears that adding the ip address of either the DC or the DNS server (i don't know which since the DC and DNS server are the same machine on our network) to a file called msplat.txt fixes the problem.
mcseguy9
02-25-2002, 02:27 PM
out of the 3 of us, the one who can get in doesn't have proxy client (WSP) installed. the other 2 of us do. it appears that adding the ip address of either the DC or the DNS server (i don't know which since the DC and DNS server are the same machine on our network) to a file called msplat.txt fixes the problem.
BipolarBill
02-25-2002, 03:23 PM
If so, congrats! Man...Win2K AD can be pretty damned obtuse, can't it?