New 2008R2 Server To 2003 Domain

[SailingNut]

OK, now for the first real operational problem!

 

I have a laptop that we hibernate when not in use. We have opened it up & logged in several times since the domain changes. Well now when trying to unlock the machine (it exits hibernation in a locked state) I get the following error (with a known good passeord, have tried several times) "The security database on the server does not have a computer account for this workstation trust relationship"

 

I tried creating a machine account for the computer on the server, but to no avail. :-(

 

I have searched on Google a bit and have not found any satisfactory answers.

 

I think this all points back to the SID problem that I mentioned the other day. What do you think?

 

Looking forward to an answer! My wife is not happy without her laptop! And I'm even more unhappy without it! ;-)

 

Thanks!

[ICTCity]

Actually this problem may not really be related to the domain migration.

 

I think that clients experiencing this problem are VISTA / 7 with SP1.

 

The only thing I think you can do is this: (on your domain):

 

Open GP: Computer Configuration -> Policies -> Administrative Templates -> Network -> DNS Client

 

Check DNS suffix, if it's set, remove the entry ("Not Configured").

 

Apply policy and retry.

 

To be sure that on the machine the GPO has been applied, run this (from the WS):

 

RSOP.msc

 

And under:

computer configuration/administrative templates/network/dns client

 

You should see DNS suffix as NOT CONFIGURED.

 

Let me know.

[SailingNut]

Actually this problem may not really be related to the domain migration.

 

I think that clients experiencing this problem are VISTA / 7 with SP1.

 

The only thing I think you can do is this: (on your domain):

 

Open GP: Computer Configuration -> Policies -> Administrative Templates -> Network -> DNS Client

 

Check DNS suffix, if it's set, remove the entry ("Not Configured").

 

Apply policy and retry.

 

To be sure that on the machine the GPO has been applied, run this (from the WS):

 

RSOP.msc

 

And under:

computer configuration/administrative templates/network/dns client

 

You should see DNS suffix as NOT CONFIGURED.

 

Let me know.

 

The setting on the server was already set to "Not Configured" and I checked on the client and there are no network policies set on the client.

 

However if I run ipconfig /all I do see that a primary DNS suffix is set. (Not sure if this is related or not.)

[ICTCity]

What's the notebook's OS?

 

if it's Vista with SP1, can you please remove the SP1?

 

Only this client has this kind of problem?

[SailingNut]

What's the notebook's OS?

 

if it's Vista with SP1, can you please remove the SP1?

 

Only this client has this kind of problem?

 

It's Win7 SP1

 

It's the only client having the problem, but we really don't have to login to our other systems much because we keep them running.

 

I can't really test on the laptop because I left and re-joined the domain and the problem went away.

[ICTCity]

I hope you will not have problems anymore :)