I found the problem.

I thought I upgraded the passive node, falied over to it & then upgraded the other server.

After upgrading the passive node, then the Active node I was...

I opened Failover Cluster Manager, expanded my cluster - there are 4 points to further expand: Services & Applications, Nodes, Storage & Networks.

In Services & Applications, right-click SQL Server...

Thanks. I hadn't thought of the NORECOVERY option, making the 2k5 database unavailable for updates.

Sorry for my tardy response, I've been on vacation.

I cannot connect from the DMZ, because that requires an IP address for the connection.

From inside my LAN I can connect via...

There is a firewall.

Access to the SQL server is restricted. The destination port is 1433, there is no restriction to the origination port, but there is to the origination...

What edition of Windows & SQL does this article relate to? I would assume Windows Enterprise due to limitations on memory with Standard edition. Will this 3 node solution work...

Thanks everyone, this is the information I needed.

If I encounter any problems along the way, I'll post them.

Good tip. I had forgotten SQL the logins needed to be 'replicated' 1st.

Thanks, I understand better now. Can you explain what happens in a 2-node cluster that is active/active? Does each instance 'mark' a database as active on that server & then...

I know how a 2-node active/passive cluster works. I thought I knew how a 3-node cluster works until I started reading your responses. My assumption with a 3-node cluster is...

I was hoping I could have 2 nodes active simultaneously. Sorta renders the prospect of 3 or more nodes less than efficient, unless all are active.

If all nodes are...

I found the solution in the publication. When adding or modifying the properties of the publication, in the Articles section, select Article Properties for each of tables, Stored Procedures, Views...

I've tried *.bak & .bak

Same situation.

I changed the subscription from a pull to a push & all is well.

The version of the distributor isn't a factor in this case.

However, when replicating between SQL2k5 & SQL2k8,...

I found the problem. The snapshot was in the wrong folder & the permission to access it was on the wrong folder, too.