I built a brand new server for a client of mine. The day before the install of the new server, their old sbs 2003 had both of the hard drives fail. Fortunately they had back ups of all of the important data. I went in and installed the new server. I first attempted to connect it to the current domain. I managed to promote it to domain controller. I had issues with connecting client computers to the new server. The connection program downloads fine, however once you input username and password, after about 3 minutes the client computers would show an error saying that the server is unavailable. I was able to get only 1 of the 10 computers connected to the server on the same domain as the old server. The other computers kept showing that error. I read around on a few blogs and found some interesting information stating that because I couldn't demote the old server before I promoted the new one that I was inevitably going to run into issues.
The next day I decided to completely re-install the 2012 r2 software with the intent on changing the domain name so there would be no conflicts. instead of their typical domain <domain> I added a 1 after <domain1>. I set the server up according to the microsoft support site steps, however each computer is still showing the same error. From each client computer I removed it from the previous domain, and just made them work group users while attempting to connect them to the server. I have gone through all of the steps that Microsoft has regarding the server is not available error. I synchronized the time, as well as a few other things.
I was wondering if anyone has experience with this? I need help, what was supposed to be a few hour project has turned into a week so far. I can't seem to get these client computers connected to the server. If there are any suggestions I am certainly all ears, and I appreciate in advance any help in this matter.
Thanks for your time
James