Upgrading to Win2k from NT 4.0

This is a discussion about Upgrading to Win2k from NT 4.0 in the Windows Networking category; After upgrading our PDC (Primary domain controller) running Windows NT 4. 0 Server to Windows 2000 Server I've got a little problem with client machines running Windows 2000 Professional: they could log on , they see the hole network but when trying to browse any machine in that network the following error message ...

Windows Networking 2246 This topic was started by Alexiz, 2001-11-19 18:53

Discussion 8

Alexiz

24 Posts
Location -
Joined 2001-11-19

#69416

2001-11-19 19:53

After upgrading our PDC (Primary domain controller) running Windows NT 4.0 Server to Windows 2000 Server I've got a "little" problem with client machines running Windows 2000 Professional: they could log on , they see the hole network but when trying to browse any machine in that network the following error message appears: "No logon servers are currently available for netlogon services". Our network contains both NT 4 workstations and Windows 2000 Pro. There are also 2 more servers running Win2k Server - they even COULDN'T log on into the domain 8) . Please, help.

KT266a chipset shootout

Windows XP Question, please help

Participate in our website and join the conversation

You already have an account on our website? To log in, use the link provided below.

Create a new user account. Registration is free and takes only a few seconds.

This subject has been archived. New comments and votes cannot be submitted.

Nov 19

Created

Dec 19

Last Response

0

Likes

2 minutes

Read Time

Users

Responses to this topic

clutch

3857 Posts
Location -
Joined 2000-03-29

#69417

2001-11-19 20:10

So, your new W2K server is now running AD (in compatiblity mode for NT more than likely), but you can't browse? What is your current name resolution method? How many other DCs do you have running? I would imagine that you have at least one DNS box running, but do you have WINS still up? That error is normally typical of a blocked or failed name resolution attempt (listed here) where the workstation can't figure out who to talk to for credential validation.