Replication to a web server in DMZ

Hello,
We have active/active SQL2000 SP3a on a Win2k3 cluster in our domain. We
need to copy some tables from a
database out to our web server.
The web server, is SQL2000 SP3a on Windows 2000, SP4. It is a stand-alone
server out in the DMZ.
We get the following error when trying to do this:
SubSystem Message - Job 'VIRTUALSERVERNAME\INSTANCENAME-WEBSERVER-13'
(0x5F1388610429AD4B8860D51DF8504198), step 2 - Login failed for user
'(null)'. Reason: Not associated with a trusted SQL Server connection. The
process could not connect to Subscriber 'WEBSERVER'.
Here are some thoughts we have. The SQL server in the domain runs on port
1303. The SQL server in the DMZ is running on a different port. Do the
ports need to match for the replication to occur?
We are not sure why this isn't working. Anyone have some input or some
documentation on how to set up replication to a web server in a DMZ. I am
sure this is something that is done at most companies, but we are missing
something.
Thanks in advance.
Hopefully this article will help out:
http://www.replicationanswers.com/InternetArticle.asp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I would try SQL Authentication.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"JJP" <anonymous@.discussions.microsoft.com> wrote in message
news:%23%23dsWsu6FHA.1276@.TK2MSFTNGP09.phx.gbl...
> Hello,
> We have active/active SQL2000 SP3a on a Win2k3 cluster in our domain. We
> need to copy some tables from a
> database out to our web server.
> The web server, is SQL2000 SP3a on Windows 2000, SP4. It is a stand-alone
> server out in the DMZ.
> We get the following error when trying to do this:
> --
> SubSystem Message - Job 'VIRTUALSERVERNAME\INSTANCENAME-WEBSERVER-13'
> (0x5F1388610429AD4B8860D51DF8504198), step 2 - Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL Server connection. The
> process could not connect to Subscriber 'WEBSERVER'.
> --
> Here are some thoughts we have. The SQL server in the domain runs on port
> 1303. The SQL server in the DMZ is running on a different port. Do the
> ports need to match for the replication to occur?
> We are not sure why this isn't working. Anyone have some input or some
> documentation on how to set up replication to a web server in a DMZ. I am
> sure this is something that is done at most companies, but we are missing
> something.
> Thanks in advance.
>
|||Thanks Paul, I am looking that over.
Hilary, the web server is using Windows and SQL, is that what you are
referring to?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ORJz63u6FHA.3416@.TK2MSFTNGP15.phx.gbl...
>I would try SQL Authentication.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "JJP" <anonymous@.discussions.microsoft.com> wrote in message
> news:%23%23dsWsu6FHA.1276@.TK2MSFTNGP09.phx.gbl...
>
sql

replication or mirroring

We have a sql server 2000 sp3 server on a win2k3 server standard
edition. This is on dell hardware with a dell scsi dasd enclosure
directly attached. We want to duplicate the hardware and replicate or
mirror the database to the backup server and do a manual or automatic
failover in case of outage(more than likely manual). Wondering right
now if replication - with say software like doubletake - is preferred
over sql database mirroring or vice versa. Thanks(mmark751969@.yahoo.com) writes:

Quote:

Originally Posted by

We have a sql server 2000 sp3 server on a win2k3 server standard
edition. This is on dell hardware with a dell scsi dasd enclosure
directly attached. We want to duplicate the hardware and replicate or
mirror the database to the backup server and do a manual or automatic
failover in case of outage(more than likely manual). Wondering right
now if replication - with say software like doubletake - is preferred
over sql database mirroring or vice versa. Thanks

Database mirroring is not available in SQL 2000.

When you say replication, you don't mean replication in SQL Server do
you? This can be used to implement a low-budget high-availability solution,
but setting up replication is a little messy. Not talking of failback
to the main server once you've failed over.

I know there are other means of replication which happens on disk level,
but I don't have any experience of it.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx