Jump to content

Recommended Posts

Posted
Have you ever tried using the NLTest command? Unlike NetDom.exe, it is included with Windows 7 as standard and is a bit quicker than re-joining the computer to the domain.

 

nltest /sc_verify:YourDomain

 

http://i.imgur.com/Vwe86.png

 

No I haven't as yet as I came across it today. When I receive another trust related problem, I'll give it a go :)

Posted

We have the same.

 

It happens on desktops and laptops, wired and wireless, some imaged some oem.

 

I have started having some that after removing from domain will not re-join.

 

Next time I will try some of the above tips.

 

cheers.

Posted

I am having a similar issue. We have recently upgraded around 1200+ machine to Win 7 SP1 using SCCM.

Over the last 3 months or so we have been getting jobs logged for trust issues. In most cases the fix is as simple as a reboot but in some we have to do the whole disconnect and re-join the domain....

 

In most of the cases the issue happens when the user stays logged into their machine overnight . The next morning when the user goes to unlock there machine they get the trust issue. Unplugging the network cable allows the user to unlock the machine and carry on (once the cable is plugged back in that is...).

 

I think the issue started happening when we had DNS scavenging turned on but I can't be sure. I know we do have issues where DNS appears to be slow to replicate so we need up with multiple machines with the same IP.

Also the issue isn't happening on the same machine more than once (that we can tell) as of yet so it makes it very hard to troubleshoot.

 

Any thoughts??

Posted
i wonder if its to do with naming. i recently replaced a suite pc so i changed old pcs name and turned it off (diddnt reboot). added new pc with the name id released and it seemed to work fine till login. Redomained plenty of times eventually added an a to the end of the name and its worked fine ever since
Posted

Hi sted,

As part of our rollout the names of any existing machines were changed by prefixing them with a 3 character suffix, also a large number were replaced with new machines.

As we use the machines serial number with the 3 character prefix there is no chance of the names been the same (he says crossing his fingers)…

 

Does anyone know how the machine password process works when it comes to Windows 7 and Server 2003 Ad?

 

I have found an article from 2009 but the Reg. keys that store the current and previous password that are talked about in this article don’t exist in Win 7 (at least not in the same location) and the attributes on the server where they should be stored are empty…

Posted
ok can't login as administrator as that is disabled. cant login as domain admin due to trust relationship error. only account that lets me in is standard local account. any ideas?

 

If you boot into safe mode it should be enabled then.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...