Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I have 2 computers on my network that are keeping each other from connecting. When one is on the other cant connect.
I thought it was a SID problem but i ran newSID from the Sysinternals tools on both PC's but no change.
The event that led to this problem is this: PC#1 received an upgrade.. new board, processor, HDD, etc. PC#2 was hit by lightning so i used the old HDD from PC#1 to get PC#2 back operational. I installed the old HDD w/o formatting. I simply just added the logon info for PC#2. This is what led to me thinking it was possibly a SID issue but like i said I ran newSID on both PC's.
So every morning, PC#2 is connected to the network first, then when PC#1 tries to connect it says domain not available. But if I remove PC#1 from the domain and re-install it back with the exact same credentials it will connect. Now both PC's are connected to the network but if one of them log's off it cannot connect back until i do the remove/install again.
The old HDD still has the log on account from PC#1 but it is not used as we use a different log on now for PC#2.
What am i missing?

Yes they are different... now. But at first they were not.
The used HDD came out of the computer named accounting2. When I upgraded that computer i named it accounting2 again. So when i installed the old HDD in the damaged one it came up as accounting2 also. But i have since renamed it to DSS.

check/clean up your servers DNS entries concerning these workstations
Imagine the power if you knew how to internet search

I would also remove the computer accounts from AD and the clients from the Domain, then re-add the clients to the Domain.
Life's more painless for the brainless.

Sorry for the delay response...
I removed the comps from the AD and re-added. Everything seems to be working good now.
Thanks Jennifer

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |