Small Business Server

The issue is not the domain name change but the fact that the pdc has a new security identifier attached to it after the rebuild. Thus, the bdc doesn't know what it is. Try deleting the bdc from server manager. Then, on the bdc change its domain name to whatever your tech renamed the domain. On the pdc, add the bdc and on the bdc try to get it to rejoin the new domain.

The short answer is no. You have a problem: "After installation of a Windows NT Server PDC or BDC, that computer must remain in its designated domain, or have Windows NT Server reinstalled on it." -Supporting MS Windows NT 4.0 Core Technologies, Microsoft Press, 1997. The normal method when a PDC fails is to promote a BDC to PDC, rebuild the (old)PDC, Have it join the domain as a BDC, then promote it in turn. The problem here is that SBS will only be a PDC. Your technician probably changed the domain name because he could not get SBS to play nice with the other server. Even with the same name, you might still wind up with a SID problem. MS might have a way around these difficulties, but it is too late without rebuilding the SBS a second time.

Part 2: If you do wind up rebuilding your SQL Server, you might consider making it a member "vanilla" server, not a BDC. This will avoid the problem in the future, and free your SQL Server from logon validation traffic. The drawback is that if your Small Business Server crashes, your network is down until recovery unless you add another BDC. Question to ponder: What limited your recovery options to a scratch install?

Unfortunately with NT, the only way to rename a domain on a server is with a reinstall of the operating system. Sorry.

Sorry - you may have fixed your problem by now, but I thought I would add my 10 cents worth :-)

I agree with the later replies to your message. You will need to re-load NT on the BDC as a BDC for things to work again.

I also would recommend SQL being a member server instead of a BDC.

Because there can be no trusts between an SBS server and another domain, I think you a little out of luck.

You can't even go about it backwards, by promoting the BDC to PDC, then re-installing the PDC as a BDC on the old domain as SBS only supports it's configuration as a PDC.

You may find it quicker to dump your databases and rebuild the SQL box. - Sorry.

This question was auto closed due to inactivity