At work we have an old server running Windows 2000 Server. It has SQL Server 2000 installed on it. It is our production db server. We recently bought a new server, a Windows 2003 Server and installed SQL Server 2000 onto it, with the intention of migrating our production db to the ne3w server. The old server is a member server of a Windows 2000 Active Directory network; it is not a domain controller. Well, the old server has begun to cause us a lot of problems. All of the servers are on what is known as a KVM switch (?keyboard, video and mouse?), so that all we need are 2 keyboards, 2 monitors and 2 mice in order to interact with the servers. The old production server has stopped being able to response to either the mouse or keyboard and it no longer displays anything on the monitor. Clearly we are going to have to do something, and soon. One option we have discussed is copying the production databases from off of the old server and putting them onto the new server. (We are using Veritas Backup Exec for our backup system.) Then what we might do is turn the old server off, take the new server out of the network, rename it to the same name and IP address of the old server, and then bring it back up again. What I am wondering is, will SQL Server behave itself it we take the new server out of the network, rename the server and then try and bring it back into the network? Rod ******************************************************** This Weeks Sponsor StressedPuppy.com Games Feeling stressed out? Check out our games to relieve your stress. http://www.StressedPuppy.com ******************************************************** To Unsubscribe, set digest or vacation mode or view archives use the below link. http://thethin.net/win2000list.cfm