barton_1954
asked on
Windows XP Professional connection to Windows NT4
I have just set up a computer room with 22 PC's all with identical XP professional setups, 4 od them will not connect to uor nt4 server. They display the follwoing error message.
Windows cannot connect to this domain either because the domain controller is down or otherwise unavailable or because your computer account was not found. I have tried the MS knowledge base article 318266 but this doesn't fix it. I have installed the latest NIC card drivers. The other strange thing is that I can only log on locally using the Administrator account none of the others local account work.
Windows cannot connect to this domain either because the domain controller is down or otherwise unavailable or because your computer account was not found. I have tried the MS knowledge base article 318266 but this doesn't fix it. I have installed the latest NIC card drivers. The other strange thing is that I can only log on locally using the Administrator account none of the others local account work.
ASKER
Sorry, don't have that software available. Also XP is a bit fussy about things like this isn't it? I have tried removingthe IP adress and removing it from the domain but didn't make any difference
Another solution to "ghost" (I have already tried it, but with 2k Windows, and it works [but, like in your case, you must have a windows installed on the destination disk]) is to boot from a third PC with the 2 other 2 hard drives.
And just copy files from the working comp's HD to the non-working comp's HD... but I agree that it really looks like a "patched-up job".
As you said you have XP and I think it will not like this "solution" more than the first one.
And just copy files from the working comp's HD to the non-working comp's HD... but I agree that it really looks like a "patched-up job".
As you said you have XP and I think it will not like this "solution" more than the first one.
Try logging on lacally and rightclick "my computer" and go to properties.
Change the network identification settings by changing the name of the conmputer and add the computer again to the domain. You need a domain admin username and password but I suspect you know that ;)
This way you create a new account on the NT server and it solved similair problems for me several times.
Perhaps you need to check on the NT server in the computer accounts to remove the malfunctioning (now obsolete) accounts.
Change the network identification settings by changing the name of the conmputer and add the computer again to the domain. You need a domain admin username and password but I suspect you know that ;)
This way you create a new account on the NT server and it solved similair problems for me several times.
Perhaps you need to check on the NT server in the computer accounts to remove the malfunctioning (now obsolete) accounts.
ASKER
cbakker - thanks for that I was nearly there myself with that one. Someone told me that this is a known problem. If you delete the entry from the Server Manager, it also fixes it as you then can add it back in again.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
barton_1954:
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations! No comment means you don't care.
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations! No comment means you don't care.
Or test a non-working comp with the hard drive of a working comp.