Can't find domain?

[jwilder]

I have setup 2K Server and we have 2K Pro workstations. I've setup a domain controll, DNS and DHCP, and WINS account. But when I logon to to a workstation as 'rover' domain admin account and try to add a domain user to the local administrator group, it says it can't find/locate the domain specified?

Any ideas on what I need to look at or what I'm missing?

Thanks. Jason Wilder
IT/CAD Manager
"When I go, I want to go in my sleep like Grandpa. Not screaming in terror like his passengers."

 

[tlcscousin]

You did join the domain with the two workstations?
Are you logging into the domain or into the local PC?
When you do the ctrl+alt+del at first logon click on the options button and make sure it is the domain you are logging into not the local PC.

 

[jwilder]

Yes, I'm logging in under a Domain Administrator account, as Domain Admins are in ALL local computer Administrator groups. Jason Wilder
IT/CAD Manager
"When I go, I want to go in my sleep like Grandpa. Not screaming in terror like his passengers."

 

[Guest_imported]

I have a similar problem. I cannot access the userlist in an NT 4 domaim from a new DC. I can map drives and browse the PDC. I can access the userlist from other DC's on my site so I know the trust is OK. I can browse access lists for every other domain as well. The problem is only at this server. It will not allow me to log onto the domain directly either.

Must I reboot the PDC on NT 4 to resolve this ? (It would need to be scheduled)

 

[SteveTheGeek]

JWilder,
I've had the same problem for months. NT4 and/or Win2kPro workstations, I can't manipulate any group membership involving domain accounts (such as adding my regular domain user account to the local Admin group), it can't find the domain specified. Logins and resource access works fine.
My suspicion, which I haven't bothered to nail down yet, is DNS settings - not finding the AD domain controller service somehow for things other than logons. Are the workstations pointing to a DNS server that has the Win2k domain's AD services records loaded?
-Steve

 

[Guest_imported]

Months is unacceptable - I need to assign permissions now, today ! This machine is a DC running WINS and GC. All machines in chicago logon to it, and are naturally, not able to browse. One can verify WINS lookups thru the console by name searching the registrations. Nothing unusual here, the 1B (master browser) entry is correct, so I don't think WINS is the issue. If I specify the FSO as the primary WINS server, (which CAN access the domain) it does not make any difference. Same error

 

[SteveTheGeek]

Nomad,
If it's that much of a crisis you might want to call Microsoft Tech Support. That being said, it doesn't sound like a WINS issue to me, either. If you're running a Win2k network in native mode, WINS ought to be entirely superfluous. The DNS situation is what ought to be looked at. Do your Chicago machines use a DNS server that has the DC's records?
-Steve

 

[Guest_imported]

Actually, I have called teck support and it remains an open ticket at the moment. This is not a native mode enviroment. There is only 1 DNS server on the network that all DC's point to. If it did not have the appropriate entry, no other DC would be able to access that domain either. Such is not the case.

I am not able to log onto this domain as admin or verify trust relationships since the domain is "unavailable" despite being able to browse it's contents thru explorer.

 

[SteveTheGeek]

<slapping forehead> Rereading the thread, I just saw the &quot;NT4 domain&quot; noted in your first post. Sorry, my answers have been assuming you too are in a Windows2000 server/ActiveDirectory domain environment, I apologize for any confusion I may have caused.
-Steve

 

[Guest_imported]

Eureka, (where's my violin ?)

OK here's the solution.


There should be three entries in WINS for each DOMAIN.
The most important one is a (1ch) Domain controller entry.
It is probably missingwhich is the problem.


Go to the WINS table, registrations, browse all. Add the following static mapping:
Type = Domain Name (from drop down list)
Enter the name of the DOMAIN you cannot browse
Enter the IP Address of the PDC in that domain.
Refresh toi confirm the entry now exists.

 

[markstuart]

Hi, I'm having problems integrating a W2K machine onto an WinNT4 server network.
The W2K machine seems to be sending packets out onto the network but cannot see the Domain.
I've tried registering the name of the WS onto the server as an NT4 workstation, but I'm having no luck!!
Any ideas please?

Mark

 

[wesleychang]

Hi, I am under a similar circumstances that you guys have
just discussed of--only that the situation is reverse.

I am having problems to logon to Win2000 DCs from NT servers. The migration of NT to 2000 of the DC has been
passed for months. However, yesterday, when the users from NT servers tried to logon to the 2000 DC as usual, it just
wont do it! We've tested all necessary procedures--ping
test, net use, snifering the ports, blah blah, and they all
work out except letting users to logon. If anyone of you
have any idea of resolving this problem, please please help
me out here. Deep thousand thanks!

Sincerely,

Wesley Chang

 

[SteveTheGeek]

Are you both getting &quot;Unable to locate domain controller&quot; errors? The exact text/point that you're getting the error would help.
-Steve

 

[GlenJohnson]

I don't know if this will help, but I had users unable to connect to our domain after I put in a new W2k server. Since we're mixed mode, (2000 and Novell), the users would cancel the domain login and get into Novell. They didn't inform me of the problem for several weeks, (Don't ask me why) so at first I didn't correlate the new server to their problem. I decided after about a week to reboot all 3 2000 servers and when I rebooted the new server, we could log on. (By this time I'd set up a test workstation that couldn't log on also.) Whenever I took the new server off the network, I could log on, when I put the server on the network I couldn't. Started monitoring the network card, and found out it was sending out tons of bad packets. Replaced the card and haven't had this problem since.