Domain Issue.

[bobsa32]

Ok a bit of history first.

We took over a site that had two servers. sbs2003 and server 2000 as TS. When we arrived there appeared to be some majot domain/network issues. When running dcdiag/netdiag there were a number of errors, mainly that both server held all FSMO roles (how can that be). anyway, after a bit of digging we discovered that the Win2K server had been added in later, and when the engineer had promoted it to a domain controller instead of adding it to the domain he created another new domain controller. we reomved the TS server, re promoted it, ran service packs and everything looked great. However, some pc's are no longer able to logon or get access to the network if they have remained logged on, also i can't connect to any of the effected pc's as i "don't have permission".

1. is this because they would have been on the "other domain"
2. if it is, how do i fix it, i cant re-connect as they dont see the PDC
3. Help

Regards

 

[TechSoEasyMVP]

Yeah... sounds like they got some screwey instructions from the "old domain". So here's what you need to do to get them on the SBS's domain correctly:

At the client machine:
1. Log in with THAT machine's LOCAL administrator account.
2. Unjoin it from whatever domain it belongs to into a WORKGROUP
3. Change the name of the computer (this is not an option, you must use a name that is unique and hasn't been used before on your SBS)
4. Delete or rename the following directory C:\Program Files\Microsoft Windows Small Business Server\Clients if it exists
5. Make sure that the network settings are configured to get an IP address automatically (DHCP enabled) from the SBS
6. Reboot

Then on the server, from the Server Management Console:
1. Remove the client computers if it still shows in the Client Computer screen on the Server Management Console
2. Add the client with it's NEW name using the Add Computer wizard

Then, go back to the client machine, log back in with the local Administrator account and join the domain by opening Internet Explorer and navigating to

http://<servername>/connectcomputer

That will take care of your errant workstations. You might want to review the guide on properly deploying a Windows 2000 Terminal Server in an SBS environment just to be sure you got things right:

http://sbsurl.com/tss2k

Jeffrey B. Kane
TechSoEasy

http://www.techsoeasy.com

 

[bobsa32]

I have managed to sort out the system, it would appear there was more than one problem.

1. The HP Procurve switch was goosed
2. There was huge data loss on the network cables
3. There was a virus on the server

It would seem that there are still some rogue IT peeps out there giving us a bad name.