replacing the hardware

[damnpc]

This is not the best way of going about this, but due to media/skills and other serious problems I am forced to do an install that worries me. I am moving a nt pdc with sql(6.5) onto new hardware and as a stand alone server. What I intend to do is install nt(new domain - smae machine name) as a stand alone server, then install sql and other apps on the d: drive (as on the old server) then restore the old servers d: driver over the new. So the server is theoretically the same as the old one inclueding ip and machine name. Now done and dusted I cannot get my clients to connect anymore. Yet I can ping and connect via enterprise manager via IP not by host name. Any Ideas??

p.s. I renamed the machine, gave it a new ip, redid the clients odbc and it worked a treat. But I seriously need to have it use the same machine name and IP.

 

[globalstrata]

When you restored, you probably restored all the permissions for all files that you had previously on the old machine. In addition, if there were services such as SQL, running under an account name, this may have been overwritten so the account may not have the proper access such as Log on as a service permission and other. This means that the SIDs (security IDs) for all the accounts are different from the current machine's SIDs.

What I suggest you is to go to the services window and check that all the services are using the proper accounts (accounts working on that new domain). Then check that those accounts have the proper Access (I have not done this for some time but when you open the User Manager, the select the second Menu and either the second or third option gives you access to look at these permissions. There is a box in the bottom of that window that should be checked so you can see all the permissions)

This is the hard part - Once you do this, you may want to go to the root of D and take over ownership of every folder and then manually go to every folder and setup the proper permissions (the problem is that this may take a long time and it may not work correctly)

If all you wanted to do is to move the SQL server from one server to another and you did not care about the PDC, I would even sugest re-doing everything over again. However, instead or restoring, I would only move the databases from one server to another. I did this one time but I don't remember the steps. All I remember is that there is a way that you can back up only the database from inside SQL and then move the database to another server. You may need to ask questions in the SQL group for this.

Gladys I. Rodriguez - MCSE, CCDA, MCP+I
GlobalStrata Solutions Inc.

http://www.globalstrata.com

 

[damnpc]

Thanx for the advice globalstrata, I have had a look at this, the permissions were allready the same. I am wondering if it is a name resolution come networking problem, more than a permissions problem. It works fine as long as I have it on a different name and ip address. The minute it is configured exactly the same as the old server it falls over. I have even recycled the 3com corebuilder its plugged into to clear the arp cache.