Old thread, but +1.

Easily tested. But I have not

LOL that is funny, I did not think about it that way.

The script works well with one exception. If your logical name for the database files contains spaces, it will cause issues.

If you alter the stored procedure and enclose the...

Yes, that's what I was thinking, that the Client, outside the firewall, and the Publisher server, inside the firewall, would be able to communicate as a result of the Distributor...

But the DMZ has to have the correct ports open to reach the Publisher server. That's what I was saying (and may have worded poorly).

The client needs no direct...

Yeah, one would think.

I now have about 95% of this worked out (in addition to a bad headache). I'll try to boil it all down to a step-by step...

In the Config for the named instance, I changed the Enabled setting for 10.0.11.132 to "No". Then I was able to get the named instance to start with its ports...

My two IPs are, let's say, 10.0.11.111 and 10.0.11.132. I have been running the default instance for years on IP1 (10.0.11.111). I have just installed the named instance, bound IP2...

Yes. ownership has not changed and the owner is an admin of the SQL Server. Thsi exact sp runs successfully on other servers, and used to, on this one.

'

Thnaks. Let me look a little further, now that I reaized that your script created the jobs. If I am still stuck I will e-mail you. Thanks for your very...

Your job looks very impressive. But the concept of tokens and how they are used is way above my head. I am not sure I will be able to build...

Oh, man. Of course.

Thanks. That's very helpful. Thanks for the quick replies. :hehe::)

Thanks. Not really a SQL guy- this has been thrown at me. Can you detail a little further?

Thanks.

This problem is KILLING me. SPNs are OK, I have deleted and re-created the SPN several times. It's making me nuts.

D2 still gets "Cannot Generate SSPI context" even when ODBCPING-ing...