Win 2K Server shows up as NT Workstation

I assume that this is your question:
How that in server manager the W2k member server is grayed and seen as workstation?
Then, the answer is that browser service is not working properly. You will have also surprises then when you will go to NetworkNeighborhood and will try to browse it.

Conclusion is that is not a security issue. Windows NT 4 accounts will be able to access resources from W2k Srv member servers (and this just adding the w2k srv as memebr server in the NT4 domain). Also, permissions in NTFS 5 will work.
W2k should have all of them NetBIOS over TCP/P enabled.
The problems will appear when the name resolution for IP and NetBIOS are not working properly. So, if you are not sure about who is master browser there, and because is a W-NT4 network I strongly advise you to use WINS. As about DNS, it is very important for W2k, so better to have it too.
Don't forget to install latest SP for NT4 (I was using SP6a).

Cheers

Debbie

I will guess that all of the servers are on the same IP subnet. If you have more than one segment, remember that there is a Domain Master Browser, and a Segment Master Browser.
When server manager shows a machine as NT Server or Workstation, this means that the server manager is not communicating with these machines.
Besides the browser, there is also WINS. Check WINS and you may want to remove entries for these servers. Be sure to check your replication for WINS and ensure that old records are not being replicated over the new records. I have also gone as far as during a maintenance window of 12 hours or more, deleted ALL WINS databases and let the systems update automatically. I have done this many times and found it to work better than trying to troubleshoot incorrect records. At the same time you could also repair / reconfigure WINS replication to be efficient.

Also if you are using DNS on a WIN2K machine, remove the records for these machines also. Then from the command line on each machine in question do the following:

net stop netlogon
ipconfig / flushdns
ipconfig /registerdns
net start netlogon

By stopping and restarting the netlogon service, Lanmanager systems will appear to have rebooted and announce themselves to the browser and WINS.
By flushing and reregistering DNS, SRV records are updated on the DNS server.

There are some utilities in the resource kit that may also help you in troubleshooting.

I'm going to try the other suggestions but please keep the answers coming!!

Thanks...

It almost sounds like the browser service on these machines is not running. Check the Computer Browser service in the Services console and see if it is or is not running. If not, check the following registry key:

HKLM/System/Current Control Set/Services/Browser/Parameters

You should see two values:

IsDomainMaster: should be set to FALSE unless you want the server to act as a potential backup browser, in which case it should be TRUE

MaintainServerList: should be Auto unless IsDomainMaster is True, in which case it should be Yes.

Hope this helps!

I have the same problem in Server manager.
First look at the following (remove spaces):
http://support.microsoft.com/default.aspx?scid=kb;en-us;241847
I believe that it will not help much but it gives you an idea what you are dealing with.
In myServer Manager (I'm running Windows 2K AD Native mode) There is also a lot of computers that show up as Windows NT Workstation or Server, however I have realized that most of those machines (I couldn't confirm for sure) have not been on for a while.There is only one machine that is a Windows 2K Server that I know is online and shows up that way, and that is because it has NETBIOS over TCP/IP disabled in the Network settings (it is disabled on purpose).
Now with the problem of not being able to connecting using DameWare. DameWare uses NETBios to get a list of servers. If when you type in the name - not using the browse list, which you can do by slecting Machine > Remote Control - you still can't connect then my guess is that some ports are disabled on those machines, or that they are simply not on, and thier names still exist in the domain. If you can connect using either the IP address or the NETBios name then make sure that NETBios is not disabled on those machines.
To enable/disable NETBIOS over TCP/IP in Win2K:
1. Open the network properties by right clicking the My Network Places icon, or by going into conrtol panel.
2. Select the adapter, right click and choose proprties.
3. Select Internet Protocol TCP/IP and click onproperties
4. Click Advanced, select the WINS tab.
5. There are 3 settings: A. Enable NETBIOS over TCP/IP, B. Disable NETBIOS over TCP/IP, and C. Obtaing from DHCP Server. If it obtains it from the DHCP Server change it to enable and the problem should be gone. If it is disabled, enable it. If it is enabled then I don't know why this is happening.

I am also leaning towards a problem with NetBIOS over TCP/IP. I would try doing a port scan against these two Win2K servers to see if TCP ports 135 & 139 AND UDP ports 135, 137 & 138 are all open on the Win2K boxes. If not, then NetBIOS over TCP/IP is not running correctly.
My favorite port scanner is NMAP (www.insecure.org/nmap)

Now, Dameware does use the browser list just like an open Network Neighborhood window. Basically, anything you see in Network Neighborhood you can see in Dameware.But, since your machines are not listed, you can add them manually to Dameware, under the Non-Browsable Machines section. Just right-click on that, choose Add Machine, and add each one. YOu can then manage them with Dameware.

hope this helps

Before you reinstall the two Win2K servers that come up as NT4 machines, try this, if it is possible in your environment:
Remove both servers from your NT4 domain. Change them into being members of a WORKGROUP.
After that, go to Server Manager anddelete their incorrect entries. Then synchronize your PDC & BDC.
Next, add the servers back INTO the domain.

Maybe when they were added into the domain, the SID that was generated for their domain membership was incorrectly formatted. If you remove them from the domain, then manually remove their domain credentials from Server Manager, you can then add them back into the domain, and it is like they were brand new machines! They would get a new SID from the PDC.

Now, you'll have to do this on a weekend when the servers can be down for a while. Plus, you will need to check the servers for any services or processes that run under a domain account. When you join the servers back into the domain, these services that run under a domain account "should" start up just fine (but you never know). Obviously, when the servers are part of a WORKGROUP, the domain credentials used to run any services will fail.

Also, make sure you know the local Administrator login/password on both serversbefore you remove them from the domain, so you can log into them once they are in WORKGROUP mode.

hope this helps

As I stated in my answer - it doesn't matter what you went thru - the problem is with the NetBIOS since we see that 2 problmes that both has been proven to arrise when NetBIOS isn't working properly.
If you ask a question I can only give you answers with the facts and/or clues given. The facts/clues you gave shows that the problem is with NetBIOS, I'm not alone here all of the answers state the same. If you will just give clues where NetBIOS is failing someone might be able to help you. So faryou have only given cluse to show that NetBIOS is failing but not why, and you keep rejecting those answers, when in fact it is the answer to your question. If only you would give clues to why NetBIOS is failing we might be able to help you.

To: Joseph Moore
I tried that thinking it would just reregister itself but it did the same thing. I did however promote my BDC to a PDC and shut down the PDC. After about 30 minutes they showed up correctly and then in about 4 hours they went back to the original status.

TO: NewYorker211
I totally agree.. But if I knew why it was failing I would be able to fix it.. : )

I'm trying to tell you that I in fact don't have a clue as to why it's failing. I do have another bit of info to throw in. (Please see my above comment.)
I'm going to close the question after today so everybody that responds again with a VALID attempt will get the points.. Anybody that has already responded can just chime in and I'll take your previous answer..

If I could have responded but not rated the answers I would have. But everybody is telling me what I already knew with the exception of a few but I tried those and they didn't help..