approval relationship and a single domain

Question

Hello,

PB: a network of 12 workstations, one of the workstations is no longer able to connect to the network. In the Server Manager, when I click on the workstation in question, I get the following message: "The trust relationship between this workstation and the primary domain has failed," whereas there is only one domain in total. I attempted to remove it and add it back to the domain, but in vain. Similarly, when repeating this operation for another workstation, I encountered the same trust relationship message.
Thank you for your help

Val

denmas · Accepted Answer

I had the same problem with a Windows 7 laptop and the domain controller (Windows Server 2003). I solved it by redoing the network identity of the laptop.

We go to the computer properties, then modify the computer name settings. Next, click on the "network identity" button, we indicate that we are on a domain network, then we re-enter the same settings, a domain administrator name and its password. The domain controller may tell us that it found another computer profile with the same name. We respond that we want to use this profile. We then indicate that the domain administrator will be a member of the local administrators group. And we restart...

Sebastien · Answer

Hi,

Check the configuration of this machine. Are you sure the station is in the right domain? (check the spelling!).

Have you tried to add the station to the domain this way:

* In the server manager, delete the machine account
* On the machine in question, switch back to WORKGROUP.
* Restart the machine, log in with a local administrator account (when logging in, make sure the domain is the name of the machine)
* Right-click on Network Neighborhood and select "Properties."
* In the "Identification" tab, click on "Change."
* Put the machine in the domain (be careful with the syntax) and check "Create a computer account in the domain." You will need to enter the domain admin account name and its password.

If it still doesn't work, make sure to check the network settings (IP address, subnet mask, etc...)

BUT: you should also check the cable if the problem appeared suddenly! Connection issues are caused 75% of the time by cabling problems!!

That's it,

See you later and keep us updated

Seb

david · Answer

I'm encountering a problem:
Setting up a new workstation with XP PRO that I'm trying to connect to our network which includes a domain name and a domain controller under NT4
I'm able to connect to the domain by going through:
* Right-click on the network neighborhood and choose "properties".
* In the "Identification" tab, click on "Change".
* Put the machine on the domain (be careful with the syntax) I enter the domain admin account name and its password.
The network settings and cables are okay
however, when I reboot the machine and ask it to connect to the domain, it tells me that no server is available to validate my password.
An computer account has indeed been created on the controller but when I want to see the properties of the workstation from the computer management on the server, it tells me that there's a trust relationship missing!
How to establish a trust relationship between a server and a workstation on the same domain?
Could it be a trust relationship issue between an NT4 server and an XP PRO STATION?
Thanks for your help
@+
david

hni · Answer

Same problem for me, quite recurring on various machines (Windows 7, XP Pro) since the beginning of the year.
I just have to take the machine out of the domain and put it back in the local group.
I’m looking for an issue with the AD (2008 R2) but without success...

peg · Answer

Hello, I tried the denmas method and it worked. I have a seven post and a 2008 server for the domain controller. Thank you

a votre service · Answer

Hi, just change the job title or server and you're good to go @+

anonyme · Answer

Hello,
I got the same error message on a workstation. After trying a number of things (removing and rejoining the workstation to the domain, changing the cable and network config, static IP...) it turned out to be these registry keys that were the issue:
HKLM\System\CCS\Services\Netlogon\Parameters
DWORD RequireSignOrSeal = 1
DWORD RequireStrongKey = 1
Make sure they are set to the value "1"

See you later!

Approval relationship and a single domain

7 réponses

Texture issues in enshrouded

Driver his

Peritel to hdmi conversion

How to access the bios on a compaq notebook

Dsi won't turn on anymore

Search for a song with the lyrics

Left mouse click, touchpad click inactive

Codes stronghold crusader

Stuck computer system repair

Disable write protection mp3 player