Domain and PDC

Your error message indicates a NetBIOS name resolution problem. THis can usually be solved by using WINS or an LMHOSTS file. Since you are new to this LMHOSTS is probably your best solution.
Are you using multiple protocols? KIE TCP/IP and NEtBEUI and or IPX/SPX? When a Microsoft netork is configured with multiple protocols, the NIC binds the name resolution (Browser service) to the first protocol bound to the NIC. If your server is using NetBEUI and this is its first bound protocol and your workstations are using TCP/IP and then netBEUI, they will browse on TCP/IP and not locate the PDC on NetBEUI.
If you are not in a routed environment, then the simplist thing to do is us NetBEUI and forget the other protocols. If you are accessing the Internet or an Intranet then TCP/IP is the protocol to use.
Microsoft supplies a sample LMHOSTS file called lmhosts.sam. In win9x machines this is located in the Windows subdirectory. On NT/sooo machines it is located in Winnt\system32\drivers\etc. REMEMBR, the lmhosts.sam file is a sample. The file name for LMHOSTS has NO extension. Check your name after you save it to ensure it has no extension. Use explorer not notepad or word to check this.

ralph

I disagree with the previous answer about using LMHOSTS file v. a WINS server - I think a WINS server is much easier. First, you should be using DHCP to serve out TCP/IP addresses to your users. If you are not, then you have to be assigning staticIP addresses to each workstation. If you are doing static IP, you need to be sure they are all on the same subnet. For example, if your network is 192.168.0.x, with a subnet mask of 255.255.255.0, then each workstation must be using a 192.168.0.x address (192.168.0.1., 192.168.0.2, etc.) and must have the same subnet mask (255.255.255.0). If you're using DHCP, then all you need to do is define a DHCP scope with the network of 192.168.0.1 and a subnet mask of 255.255.255.0. Be sure you add the WINS/NBNS server and node type options to your DHCP scope, too. Q139904 is a good TechNet article on configuring DHCP scopes (if you don't have access to TechNet CDs, you can go to www.microsoft.com/technet and search for the number of the article). If you already understand TCP/IP and DHCP generally, this is easy. If you don't and don't need Internet connectivity, simply switch your whole network over to use NetBEUI as your protocol, get rid of TCP/IP entirely, and you won't need WINS either. However, if you want to do it "right" and if you need access to the Internet, you need to stick with TCP/IP - get a book or take a class and learn the basics. Then, all you need to do for name resolution is install WINS - you go to the Network Properties/Services dialog box, click Add and on the Services list select Microsoft Windows Internet Naming Service. Once installed, you'll find the WINS server manager listed on the Administrative Tools menu. Open that up and "connect" to your WINSserver by clicking Computer/Add and then typing in the IP address of your server (which should ALWAYS be static, by the way, not assigned by DHCP). Hope this helps!

I have a private "in-home" network, and while the previous answer seem viable, the way I managed to get my 2 Workstations (4.0) to "talk" to my NTSever (4.0), was simpler that those answers implied. From the NTServer:
Admin tools > Server Mngr > Computer > Add to Domain > Check "Windows NT...", enter the name of the Worksation, Click "Add", you're done.
When You boot the workstation, name your Domain, and it will work.
Happy Logging
Luis

Personally, I like using LMHOSTS to get "difficult" workstations to sync up with the PDC. It works much better across different subnets than WINS, IMO.
So, here is a TechNet article on how to set up the LMHOSTS file for domain authentication:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q180094
(please remove any spaces)

Hope this helps.

Really, in a small network, there is no need to use WINS. Create an 'lmhosts' file, WITHOUT the .txt extension, using the following format on one line:
'ip address of PDC' 'name of pdc' #PRE #DOM:'domain name'

For example, mine is :
192.168.1.2 gxa #PRE #DOM:ourhome

On each client, place this file in c:\winnt\system32\drivers\etc, again WITHOUT the .txt ending. Then in TCP/IP properties, under the WINS tab, select the 'enable LMHOSTS lookup', and reboot.

Note, there is an lmhosts.txt file in this folder, which can be used as a template, BUT, you really want to keep this file small, and (I know, I being redundant), you'll need to drop the .txt extension.
Also note, this lmhosts file that I describe will only help you get authenticated. If your users will be mapping each other's drives, then you will have to add other hosts to the lmhosts file, or go to WINS. You can create one single lmhosts file on one computer, and use the 'Import LMHOSTS' option on the WINS tab fromeach client.
Good luck,
chet

This question was auto closed due to inactivity