bubarooni1
Technical User
Hi,
I've cloned a production computer that houses 2 instances of MSDE and one instance of SQL 2005 Express on to a test box so that a software vendor can perform some tests on it before upgrading our Great Plains to v10.0 and it's underlying database (one of the MSDE instances) to SQL 2005 Express.
I need both boxes to be on the network at once, but when I change the name of the test box so that i doesn't conflict with the already running production box, sql manager stops working and I can no longer access any of the databases. If I remove the test box from the network by pulling by removing the ethernet cable and rename it to the production server's name, it's fine.
Is there a simple hack to fix this? I really want the box on the network so that the software vendor can get in here and do their thing and get out of my hair.
Thanks In Advance
I've cloned a production computer that houses 2 instances of MSDE and one instance of SQL 2005 Express on to a test box so that a software vendor can perform some tests on it before upgrading our Great Plains to v10.0 and it's underlying database (one of the MSDE instances) to SQL 2005 Express.
I need both boxes to be on the network at once, but when I change the name of the test box so that i doesn't conflict with the already running production box, sql manager stops working and I can no longer access any of the databases. If I remove the test box from the network by pulling by removing the ethernet cable and rename it to the production server's name, it's fine.
Is there a simple hack to fix this? I really want the box on the network so that the software vendor can get in here and do their thing and get out of my hair.
Thanks In Advance