Domain controller connection issue

Are the network settings of your workstation configured? (IP address, gateway, DNS server, and WINS?)

Hello everyone,

Here’s how I managed to solve the problem:
- Remove the computer from the domain (switch to Workgroup)
- Turn off the computer
- Delete the computer name in ServerManager
- Remove the computer from everywhere it can be found (DHCP, WINS, DNS, ARP table of the servers)
- Restart all secondary controllers then the primary
- Wait for the computer to disappear from the list of computers in ServerManager (between 15 minutes and 2 hours)
- Restart the computer
- Put it back on the domain (and pray to Saint PetitMou...)

If your god is good or your prayer is effective, you’re done.
I think our problem comes from the fact that we have different versions of Windows (NT4, 2000, 2003) for the servers and Win95, 98, NT4, XP for the workstations.

Thank you all

THIAPAC

Hello brothers!
Please help me
I added my account to a domain on the Windows Server 2003 and I'm unable to access this domain.
When I enter my username and password, the following message appears:
"Windows cannot connect to the domain. The domain controller is not functioning or unavailable ..........."
What should I do to gain access? Thank you in advance.

Unfortunately for me, I have the same issue. I took the PC out of the domain and can't get it back in. Message:

The specified domain does not exist or could not be contacted

Help!

Ouki Ouki, it was just a guess!
Do you have any other suggestions for this issue?!
Thank you.

Hello, if you're working on a Windows Server 2003, check in the DHCP for the reservations of your machines
1 if the reserved IP address and MAC address match those of your machines.

Yes, everything is configured!
Everything worked very well for several months or even more.

Then, overnight, the connection became impossible!

Even after a system restore.

Where could this be coming from?

Is there a way to take control of the domain controller and how?

Is it at the time of connecting or at the time of joining the computer to the domain?

If it's the second case, I've had this problem before! If I remember correctly, it was because of the IPX/SPX protocol! The new machines that didn't have this protocol couldn't join the domain.

On the other hand, if it's the first case, I don't see:
try logging in as a local admin:
run an ipconfig and ping localhost to see if the card responds.
If it responds, ping the server's address.
I think the problem comes from either the card or the connection (cable or wall socket)
if the cable is on a hub, check for any loops.

thank you
I am not in front of the computer in question but I will try

that said, when I log in as a local administrator and then do a network neighborhood, I can access the network, the server, and the other connected computers.

should I do an ipconfig renew?

Hello,
I have the same problem as Chris1300... and I would like to know, did you solve your problem? Thank you.

after leaving and reintegrating into the field, it works again
... as for knowing what happened ;-)

thank you very much

Hello

I had the same problem, and it was due to the antivirus (Kaspersky) having the protection level set to high
Otherwise, you need to completely disable it to see

Best regards

Hello,

I have the same problem, which seems to be spreading; let me explain:
I have a network of 250 workstations and 30 servers, divided into subnets 172.16.X.X; 172.17.X.X...:
The DHCP server is located in 172.16.X.X, all the workstations on that network are fine
The workstations in 172.17.X.X, 172.18.X.X... had no issues until a few days ago when a few PCs started refusing to log onto the domain. By insisting (for about 45 minutes), we can eventually log onto the domain. The most curious part is that the password does not lock despite a policy of 3 attempts and 50 tries. If we log in locally, the workstation is well on the network, it responds to pings, and can ping others (including the DHCP server). The problem was on one workstation, and in recent days I have encountered a second, then a third. By switching the workstation to Workgroup and then back to the domain, it worked correctly for 2 days, then it was back to the same issue. If I move the workstation from the 172.17.X.X network to the 172.16.X.X network, it logs in correctly.
I am starting to wonder if a virus might be the cause of this. I do not have antivirus on the workstations, but the network is protected by antivirus, the workstations have neither CD Rom nor floppy disk drives nor active USB ports. Thank you for helping me if anyone has an idea.

By any chance do you have automatic updates enabled?
We have the same problem since we installed the MS patch MS07-39.
We completely lose connectivity with the DC. The Netlogon and Workstation services fail to start. Thanks to the folks from Redmond!!

I have a somewhat similar problem...
I have mobile workstations that use a VPN connection via 3G. We can access the network fine, the server is visible, but when we try to access it, it asks for authentication. When the credentials are entered, it says that the domain controller could not be reached to validate the user.
The strangest thing is that if instead of entering \\domainname\username I enter \\serverDCname\username, it works...

Hello,

Almost the same problem:
Several computers are connected to the domain, accessing the internet: Everything is fine.. xD
I want to add a new computer to the domain, and there: IMPOSSIBLE to add it to the domain!
So as the local administrator, I tried changing the computer name, I checked the TCP-IP settings, set it to WORKGROUP: everything is OK! .. After rebooting... still no way to get this computer into the domain.
NOTE that: From the computer, I can ping the domain controller, but not the other way around...

Thanks for your help... if anyone can assist me.

No, since I am not on the domain, I am actually trying to enter the domain, but I receive a message stating that the domain controller for the domain "xxx" could not be found, and this is even before it asks me for the administrator username and password. So I am logged in as a local administrator on the workstation that I want to add...

Yes yes, all my TCP IP settings are good (IP, subnet mask, gateway, DNS)..

It's a network I'm not very familiar with, could it be due to a license issue, if they are all being used?!

If there are any other answers, I'm open to suggestions... Thank you

Here’s how I solved this puzzle.

By completely reinstalling the domain controller, and since everything was working properly this time, I disabled the updates.

A good month of operation without any problems to date.

Good luck ++