I just got a new computer here at work and set everything up. Unfortunately I am unable to connect to our domain. Our server is running Windows NT Server (old i know). I have my TCP/IP settings to obtain automatically. I tried going to system, computer name, change, and then checked the domain radio button, typed my domain name, and received an error. The error says:

"A domain controller for the domain ABC could not be contacted. Ensure the domain name is typed correctly (im sure it is) If the name is correct, click the details for troubleshooting information"

I have no experience with NT Server at all and dont know what is wrong/not working. More importantly i dont know what to do to fix the problem and get myself on the domain. Anyone know what to do? or something to try?

First check in your network connections to make sure that NetBIOS over TCP/IP is enabled. Can your machine indeed see the server? By that I mean, can you ping the server and receive a reply?

If the settings are correct and you can ping the server, make sure that you indeed have the proper privileges to add your client to the Domain.

Have you checked with your Domain Admin?

you just need to run the nw id wizard from the same screen you are trying to join the domain on. Also, nothing wrong at all with still running nt4 server, still runs, and runs, and runs!

I take it you mean check to make sure NetBios over TCP/IP is enabled on my XP Pro machine. And by pinging the server, i can ping the ip of the server and get a response. I went into the server and went to the server usage/administator menu which shows all machines attaced to the server (i think) and added my machine name to the domain here (i was logged on as the nt administrator). When i run the nw id wizard i enter my username/password as entered on the server. it then asks for my computer name information as found on the server, where do i get this info from or what are they talking about.

I've personally never used the Network ID Wizard. Have you gone into the Properties of the Network configuration (Right-click My Computer, Properties) and then click on the button to take you to the computer name and workgroup/Domain?

You might also want to make sure the built-in XP Firewall is not enabled.

the whole point of the nw id wizard is it creates a legit comp account on the domain if there isnt one. If you are an admin on the NT Domain, you will not have a problem with the wizard. You just put what you want your local pc to be named, the name of the domain you are joining, and a username on the domain with the permissions to do so.

Ok, i have tried everything listed so far, and no luck. When i run the NW id wizard, i get to the point where it asks for the computer name/computer domain. On the nt server,i have added the computer to the domain on the server manager, however, when i enter the computer name accordingly and then the correct domain name in the nw id wizard, i get the error that the domain controller could not be contacted. my windows firewall is turned off. i can ping the server by its ip address. when i look in the server manager, it shows my computer name and the icon is blue. it has a type of nt 5.1 workstation. if i try to double click this, it says a network path could not be found.

Along with the could not find a domain controller error, when i click the details i get all this information:

"The domain name ESI might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain ESI:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.ESI

Common causes of this error include the following:

- The DNS SRV record is not registered in DNS.

- One or more of the following zones do not include delegation to its child zone:

ESI
. (the root zone)

For information about correcting this problem, click Help."

Again, i am completely lost as to why this is happening. Again any and all help is well appreciated.

Ok, so i tried to ping my xp machine from the server and the request timed out, but my xp machine successfully pings the ip of the server, does anyone know what this means?

sounds like the firewall or another third party firewall/security sw is running? are you running an av suite, it may have something running you dont know about

I know that i have disabled the built in windows firewall. I do have norton installed, which might actually have a firewall service built in come to think of it. Let me ask this in regards to the configuration of my network.

We have a dsl modem that hooks up to a netgear router, the router then connects to a 16 port switch that all the computers and the server connect to. I have the server configured with a static ip address specifically 192.168.0.2 The servers gateway is the router, specifically 192.168.0.1 Each client computer has its tcp/ip setup to obtain its addressing information automatically. I know that the computers are using the 192.168.0.1 as the gateway. is this correct, or am i configuring things incorrectly there too? Should i have everything static and reference the server as the gateway?

this did work at one time, right and no changes have been made since then?

So you were definitely right about the antivirus package causing my problem. I disabled norton and had no problems from there. Thanks to everyone for all their help.

good deal. make sure you enable av (maybe u=just not the firewall), dangerous to not have that