I have a server which is not applying replication. I ghost most of my workstations with Norton ghost then use the NewSid generator to give it a different computer sid number so there arent any duplicates on the network.

I have some computers with duplicate SIDs but a lot of computers have differents Sids. Could that be a reason why group policies is not applying?

It's not a good idea to ghost DC's, it's definetly a reason why its not replicating, but also, check all of the site links, try to force replication and read the errors with repmon and repladmin.

i dont ghost the DCs, I ghost my workstation which are not accepting the GPOs.

See ghost doc's and MS docs on how to prepare a system to be imaged.
Might be able to fix it with a remove from domain, delete computer in ad, make new computer in ad, rejoin computer.

I read it wrong and answer it wrong too. So get off my case you peanut.

I have a server which is not applying replication. I ghost most of my workstations with Norton

I highly doubt ghosting workstations will have anything to do with replication between DC's. I may be wrong, but I seriously doubt the one is relevant to the other. Dupe SID's might cause problems for the unit with the dupe trying to join the domain, but shouldn't in any way affect replication between servers.

If it's isolated, which is to say, only one server is not replicating with the others, then you have your starting point for troubleshooting. The DC that's not replicating obviously has some setting that isn't correct.

Compare all settings with the server's that are replicating. Check Event Viewer for references to the replication problem and research the information you'll see in EE on MS's knowledge base.

OK after reading your question again, you need to be more clear. Is the problem replication between multiple domain controllers, or is the problem that workstations are not applying group policy. We don't call anything that happens between a server and a workstation replication.