bobrossi56
asked on
Problems running Windows Server 2003 for Small Business Server
I have a Dell server that is 6.5 years old and is running Windows Server 2003 for Small Business Server. This is the only server in my office so it acts as a domain controller, file server, houses the free SQL database as well as Quickbooks. It also controls DHCP and DNS. My LAN connects via a NetGear unmanaged 48 port switch. The server has worked perfect for many many years, and I have never had any issues with it. Until now…in the past few weeks we upgraded our 20 client PCs from XP to Windows 7 Pro. Now we are experiencing freeze ups of the clients when they access anything on the server, Excel, Word, Quickbooks or SQL, or the network connection just drops and a reboot is required by the client to get the server connection back. Also now when I join a new client to the domain I get a warning that Win 7 is not compatible with Windows Server 2003 for Small Business Server, but I can click a checkbox that say “do not show this again” and then I click “run anyway” and the join is made. I have attached that screen shot.
My issue is I am afraid to spend $4-5K on a new server running Windows Server 2012 Std and then find it does not remedy the problem. Any suggestions or comments to steer me in the right direction would be most appreciated. I also did a test and I cannot join the domain at all with a Windows 10 PC.
Thx Experts…BobR
dc1-error.jpg
My issue is I am afraid to spend $4-5K on a new server running Windows Server 2012 Std and then find it does not remedy the problem. Any suggestions or comments to steer me in the right direction would be most appreciated. I also did a test and I cannot join the domain at all with a Windows 10 PC.
Thx Experts…BobR
dc1-error.jpg
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If the router is fine, then upgrading to Server 2012 should not be an issue and probably faster than troubleshooting a 7 year server.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I connected my own Windows 8.1 machine to a client's SBS 2003 for a bit while we were replacing it. It was no trouble to maintain a stable connection for long periods of time. Same with Windows 7 before that.
Don't get me wrong John, I agree, normally you can just plug in a Windows Vista or higher OS into an SBS 2003 network without issue. However, the changes in the IP stack did cause issues to pop up.
-saige-
-saige-
More information on the Essentials/Exchange on the same server recommendation:
https://social.technet.microsoft.com/Forums/windows/en-US/231a91bd-3ff7-45fa-9520-09c54afd3964/windows-server-2012-essentials-dc-and-exchange?forum=winserveressentials
https://technet.microsoft.com/en-us/library/jj200172.aspx
-saige-
https://social.technet.microsoft.com/Forums/windows/en-US/231a91bd-3ff7-45fa-9520-09c54afd3964/windows-server-2012-essentials-dc-and-exchange?forum=winserveressentials
https://technet.microsoft.com/en-us/library/jj200172.aspx
-saige-
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I tried a few of the suggestions in the links, rebooted the server to no avail. I think everybody hit the nail on the head...GET A NEW SERVER, not worth messing with a server almost 7 years old. Other than price my other fear is I have ZERO idea how to migrate from the old server to the new. I will post that in a new post and award points here.
thx for everyone's help
thx for everyone's help
You need to get some good local consultant(s) to help you migrate from SBS 2003 to Server 2012. You need to first uninstall Exchange if it is running, migrate over and then demote the old server. Could be a very full day or a couple of days to do this.
ASKER
Ya, we do not use Exchange, just Excel, Word files, Quickbooks, 4 printers, and the free SQL database for an app we have.
Thanks. But do check for Exchange. We just migrated a client to Server 2012 who never used Exchange. It was still installed and had to be removed first. This is why I suggest a good consultant.
ASKER