Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
I have a fresh copy of Winnt. I am trying to set up my NIC to connect to my network. But when I try to specify the DOMAIN, I get the error "The domain controller for this domain cannot be located. I have already set up the TCP/IP and NETBUI.
Did you make a computer account on the server.(and user account)
That error message doesnt help much. Make sure you network connection is ok. If you're using TCPIP check your addresses and mask...
0 
You shouldn't have to create the computer account beforehand as you should be able to add the workstation to the domain when you specify the domain, simply chose the option to create computer account in domain.
This however doesn't sound like the real problem. Provided you have a decent quality nic card, are there one or more lights on the back of the card, green usually means the drivers successfully loaded and the nic card is a go. No lights is usually bad. Do you have the correct TCP/IP settings? Is the machine a DHCP machine, or does it use a static IP address?
0
Try applying or reapplying SP 4. Many times I have network communication problems that are solved by this SP. (especially if NT Networking is installed after the SP is applied, then you have to reapply).
0
I tried using different NICs. The same error msg appears. I do see lights at the back of the NIC. I've tried installing SP 4 beforehand, and that didn't work. I've checked my TCP/IP settings and they look fine. I'm using a static IP address. I've even tried using different static IPs.
0
Did the NIC pass the loopback test? (ping 127.0.0.1) Have you tried a different NIC and new reload???
0
Check you cabling....
Check the account you're using to log onto the server. THat message that MS gives doesnt really give a good clue as to what's wrong. Usually that message means the connection isnt being made...Remember do the simple things first, then work to the complex solutions.....
0
IN MY EVENT VIEWER I HAVE THE FOLLOWING ERROR "A DEVICE ATTACHED TO THE SYSTEM IS NOT FUNCTIONING". I DON'T THINK IT'S A NIC PROBLEM BECAUSE I TRIED USING ANOTHER NIC. MAYBE THIS IS RELATED TO THE "DOMAIN CONTROLLER FOR THIS DOMAIN CANNOT BE LOCATED" ERROR.
0
You need to make sure you are using the correct drivers for your network card. I've seen this error plenty of times while setting up new machines and it was all down to an incorrect driver being used.
Hope this helps.
0
I concur with Gary, and to further troubleshoot this problem this is what I would (and have) done. Don't join the domain right now. Just finish the load by joining it's own workgroup. Seeing how you have installed both TCP/IP and NETBeui then once you finish the install, log on to the local machine (the workgroup) and try and browse network neighborhood. If you see nodes in the list then the card is ok or Intermit. At any rate, if you don't see anything then your card is more than likely being asked to run on BAD/WRONG drivers. One other thing to keep in mind. IF...you don't have TCP/IP set correctly, and there is no Domain Controller on the same segment of your network for NETBeui to talk to to get authentication then you wont join. Hence...if your a workgroup computer and you see those nodes...then I would look at the TCP/IP config.
0
I'VE SOLVED THE PROBLEM.
SOLUTION: I WAS USING THE RIGHT DRIVERS, BUT THE "PNP O/S" OPTION IN THE BIOS WAS TURNED ON. THIS IS OK IF USING WIN95, BUT WITH NT THIS COULD POSE PROBLEMS. THING WORKED WHEN I TURNED OFF THE "PNP O/S"
0  |
 Tape backup Hangs in SQL ...
|
NT memory/ performance op...
|
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
