Machines can't connect to domain after some time when EWF is activ

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

If EWF is off there is now problem in connecting to the domain. If EWF is on
as time goes on, one machine after the other isn’t able anymore to connect to
the domain.
All machines have different SIDs. All machines have static IP-addresses. All
XPe network components are part of the image. The customer (Tyco) uses
Kerberos authentication. We think the problem is because of the certificate
interchange.
 
Hello Guenter,

There are several things to try here. There are known issues with EWF and
domain participation. The main problem that people experience is that the
domain controller and XPe system negotiate a new computer account password
on the domain but after the change is made on the server and the EWF machine
reboots it's password is now out of sync. I've read some of a few solutions.
One is to commit EWF at shutdown. That may not be available to you as a
solution. You can read about the others here:

Look at Steve Farrants solution in this thread:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=352907

Also look at this Microsoft article for another possible solution:
http://support.microsoft.com/defaul...port/kb/articles/q154/5/01.asp&NoWebContent=1

Maybe those will help.

I also seem to remember a possible patch coming from MS that addressed this
problem. Maybe that is available or someone else can advise on it. :-)

HTH,
Brad
 
Thanks for your reply Brad,

The information you gave me is also intresting for me. Concerning this
problem MS has a solution. Heres the answer from Andy:

Good news, we understand this problem and there’s a fix for it, but you need
to contact PSS (Product Support) to obtain it. You need an add on feature to
EWF that will allow a particular registry key to persist. What’s happening is
that your domain controller is updating a ‘secrets’ key that needs to persist
on the client machines and EWF is filtering it out. This new EWF feature will
persist just that registry key for you.

HTH,
Guenter
 
Thanks for your reply Brad,

The information you gave me is also intresting for me. Concerning this
problem MS has a solution. Heres the answer from Andy:

Good news, we understand this problem and there’s a fix for it, but you need
to contact PSS (Product Support) to obtain it. You need an add on feature to
EWF that will allow a particular registry key to persist. What’s happening is
that your domain controller is updating a ‘secrets’ key that needs to persist
on the client machines and EWF is filtering it out. This new EWF feature will
persist just that registry key for you.

HTH,
Guenter
 
Back
Top