Replication between 2 SQL from 2 Windows SBS 2003?

Replication between 2 SQL from 2 Windows SBS 2003?
I have 2 SBS servers with SQL 2000. I would like to do a Merge
replication, I did it using wizard and everywhere I choose not trusted
connection but SQL login and password:
Configure '192.168.10.3' as a Publisher. Use '192.168.10.3' as the
Distributor.
Use '\\192.168.10.3\f$\Microsoft SQL
Server\MSSQL\ReplData' as the root snapshot folder for
Publishers using this Distributor.
Store the distribution database 'distribution' in 'f:\Microsoft
SQL Server\MSSQL\Data'.
Store the distribution database log file in 'f:\Microsoft SQL
Server\MSSQL\Data'.
Enable the following databases on '192.168.10.3' for merge
replication:
SampleDataBase
Enable the following servers as Subscribers to
publications on '192.168.10.3':
10.9.0.1
But I receive:
SQL Server Enterprise Manager could not configure '192.168.10.3' as the
Distributor for '192.168.10.3'.
Error 18483: Could not connect to server â'NSSâ' because
â'distributor_adminâ' is not defined as a remote login at the server.
But:
SELECT @.@.SERVERNAME, SERVERPROPERTY('ServerName') returns
NSS NSS
So it seems properly.
Ping nss working properly..
I need help!!! Any concepts? Maybe something connected with
distributor_admin and trusted connection â' I heard somewhere that it is
possible to disable trusted connection for distributor_admin but I donâ't
know how to do it?Hello,
I understand that when you try to create a merge replication, you receive
the error message "Error 18483: Could not connect to server "NSS" because
"distributor_admin" is not defined as a remote login at the server."
However, the servername is correct and it is the same as
SERVERPROPERTY('ServerName'). If I'm off-base, please let me know.
This issue could occur when the Machine name at windows level (Hostname) is
different from SQL Server Name (Select @.@.servername).
And this happens when the machine on which SQL Server is installed is
renamed after SQL Server installation. If it is so you will have to do the
following using Query Analyzer:
Sp_dropserver ?<server>?
(Replace <server> with the name returned by Select @.@.servername query)
Sp_addserver ?<server>?, ?local?
(Replace <server> with the machine name (Hostname) if it is default
instance otherwise <server>\instancename for named instance)
Also, did you try to use servername "NSS" when configure merge replication
and not using IP adress directly? I suspect this issue may also related to
network name resolution.
More related information:
818334 Replication setup is not successful when SQL Server is deployed by
using a disk image
http://support.microsoft.com/default.aspx?scid=kb;EN-US;818334
321822 HOW TO: Replicate Between Computers Running SQL Server in
Non-Trusted Domains or Across the Internet
http://support.microsoft.com/default.aspx?scid=kb;EN-US;321822
If you have any update, please let's know. Thank you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Peter Yang [MSFT] napisaÅ?(a):
> Hello,
> I understand that when you try to create a merge replication, you receive
> the error message "Error 18483: Could not connect to server "NSS" because
> "distributor_admin" is not defined as a remote login at the server."
> However, the servername is correct and it is the same as
> SERVERPROPERTY('ServerName'). If I'm off-base, please let me know.
yes its true!
> This issue could occur when the Machine name at windows level (Hostname) is
> different from SQL Server Name (Select @.@.servername).
> And this happens when the machine on which SQL Server is installed is
> renamed after SQL Server installation. If it is so you will have to do the
> following using Query Analyzer:
Select @.@.servername
returns
NSS
and full computer name is:
nss.domain.local
it is a domain server (SBS)
so computer name is nss and never been changed!
> Sp_dropserver �<server>�
> (Replace <server> with the name returned by Select @.@.servername query)
>
> Sp_addserver �<server>�, �local�
> (Replace <server> with the machine name (Hostname) if it is default
> instance otherwise <server>\instancename for named instance)
> Also, did you try to use servername "NSS" when configure merge replication
> and not using IP adress directly? I suspect this issue may also related to
> network name resolution.
> More related information:
>
> 818334 Replication setup is not successful when SQL Server is deployed by
> using a disk image
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;818334
>
> 321822 HOW TO: Replicate Between Computers Running SQL Server in
> Non-Trusted Domains or Across the Internet
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;321822
I will try it this...

Replication between 2 SQL from 2 Windows SBS 2003?

Replication between 2 SQL from 2 Windows SBS 2003?
I have 2 SBS servers with SQL 2000. I would like to do a Merge
replication, I did it using wizard and everywhere I choose not trusted
connection but SQL login and password:
Configure '192.168.10.3' as a Publisher. Use '192.168.10.3' as the
Distributor.
Use '\\192.168.10.3\f$\Microsoft SQL
Server\MSSQL\ReplData' as the root snapshot folder for
Publishers using this Distributor.
Store the distribution database 'distribution' in 'f:\Microsoft
SQL Server\MSSQL\Data'.
Store the distribution database log file in 'f:\Microsoft SQL
Server\MSSQL\Data'.
Enable the following databases on '192.168.10.3' for merge
replication:
SampleDataBase
Enable the following servers as Subscribers to
publications on '192.168.10.3':
10.9.0.1
But I receive:
SQL Server Enterprise Manager could not configure '192.168.10.3' as the
Distributor for '192.168.10.3'.
Error 18483: Could not connect to server ‘NSS’ because
‘distributor_admin’ is not defined as a remote login at the server.
But:
SELECT @.@.SERVERNAME, SERVERPROPERTY('ServerName') returns
NSS NSS
So it seems properly.
Ping nss working properly..
I need help!!! Any concepts? Maybe something connected with
distributor_admin and trusted connection – I heard somewhere that it is
possible to disable trusted connection for distributor_admin but I don’t
know how to do it?Hello,
I understand that when you try to create a merge replication, you receive
the error message "Error 18483: Could not connect to server "NSS" because
"distributor_admin" is not defined as a remote login at the server."
However, the servername is correct and it is the same as
SERVERPROPERTY('ServerName'). If I'm off-base, please let me know.
This issue could occur when the Machine name at windows level (Hostname) is
different from SQL Server Name (Select @.@.servername).
And this happens when the machine on which SQL Server is installed is
renamed after SQL Server installation. If it is so you will have to do the
following using Query Analyzer:
Sp_dropserver <server>
(Replace <server> with the name returned by Select @.@.servername query)
Sp_addserver <server>, local
(Replace <server> with the machine name (Hostname) if it is default
instance otherwise <server>\instancename for named instance)
Also, did you try to use servername "NSS" when configure merge replication
and not using IP adress directly? I suspect this issue may also related to
network name resolution.
More related information:
818334 Replication setup is not successful when SQL Server is deployed by
using a disk image
http://support.microsoft.com/defaul...kb;EN-US;818334
321822 HOW TO: Replicate Between Computers Running SQL Server in
Non-Trusted Domains or Across the Internet
http://support.microsoft.com/defaul...kb;EN-US;321822
If you have any update, please let's know. Thank you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
========================================
==========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications
<http://msdn.microsoft.com/subscript...ps/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscript...rt/default.aspx>.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.|||Peter Yang [MSFT] napisa?(a):
> Hello,
> I understand that when you try to create a merge replication, you receive
> the error message "Error 18483: Could not connect to server "NSS" because
> "distributor_admin" is not defined as a remote login at the server."
> However, the servername is correct and it is the same as
> SERVERPROPERTY('ServerName'). If I'm off-base, please let me know.
yes its true!

> This issue could occur when the Machine name at windows level (Hostname) i
s
> different from SQL Server Name (Select @.@.servername).
> And this happens when the machine on which SQL Server is installed is
> renamed after SQL Server installation. If it is so you will have to do the
> following using Query Analyzer:
Select @.@.servername
returns
NSS
and full computer name is:
nss.domain.local
it is a domain server (SBS)
so computer name is nss and never been changed!

> Sp_dropserver ?<server>?
> (Replace <server> with the name returned by Select @.@.servername query)
>
> Sp_addserver ?<server>?, ?local?
> (Replace <server> with the machine name (Hostname) if it is default
> instance otherwise <server>\instancename for named instance)
> Also, did you try to use servername "NSS" when configure merge replication
> and not using IP adress directly? I suspect this issue may also related to
> network name resolution.
> More related information:
>
> 818334 Replication setup is not successful when SQL Server is deployed by
> using a disk image
> http://support.microsoft.com/defaul...kb;EN-US;818334
>
> 321822 HOW TO: Replicate Between Computers Running SQL Server in
> Non-Trusted Domains or Across the Internet
> http://support.microsoft.com/defaul...kb;EN-US;321822
I will try it this...

Replication between 2 SBS (small business server) Trusts

I have SQL running on SBS Server A. It is a publisher and a distributor of a
database that has 1 subscriber a SQL Server running on SBS Server 2. How does
one replicate in a untrusted enviroment.
there was also a free ware dll that allowed sql to invoke the ras dialer..
does anyone have the valid url to this?
-- Current Standings (taken from my post on the SBS Site) --
I posted on the SQL server site and was referred to Q321822. This Q article
had only 2 paragraphs that mentioned connection between 2 non-trusted
domains. essentially it suggested creating a server agent account on both
machines. it says you 'must set up pass through authentication'. There is was
some data missing from the article.
1) How do you set up 'pass through authentication" via a SQL Agent Account?
2) Assuming 'Pass Through' is enabled, how does one reference the SBS Server?
a) 'Local Area Connection' IP Address (not likely) 192.168.0.2 (private)
b) Local Server Name. MyServer
c) FQDN MyCompany.MyServer.
d) Public Resolvable Domain Name MyCompany.com
i) With extension .com
ii) Without extension
e) Network Connection IP Address of Server 68.XXX.XXX.217 (Public)
None of the above options worked for me, response "Server doesn't exsist or
Access denied" (which is it? MDAC doesn't even know if the Server Exists?
What’s with that?)
I found the information sources lacking. None seemed to illustrate a Point A
to Point Z scenario on SBS. This is not a Version 1 product and being that
trusts are not allowed it's conceivable that many companies would be
attempting non-trusted replication.
PS, I've checked Kbase, SQL BOL, 4 MVP sites, Newsgroups, Online Concierge
and SSWUG. I was exposed to answer bits, in addition to the above mentioned
options, there was mentioned RPC over TCP, RPC over UDP, Linked server
options, Remote server options, SSL options, replication via Backup and
Restore, replication via output files, Replication via terminal services
etc..
Now, I'm a person of reasonable intelligence, willing to the put the time
and effort into research, but am I wrong here when I suggest that the
documentation is all over the map? I will be posting this reply in both the
SQL Connectivity and SQL Replication newsgroups. In my opinion Microsoft does
a great job of documenting the scope and detail of it's technologies but
often falls short when it comes to implementation documentation. They are 2
distinct types of technical writing. I love Microsoft products and take the
time to scribe my opinion in hopes that it will yield stronger product line.
With that said, I ask again for a -concise, thorough, list of steps on how
to set up a push transaction based SQL replication subscription between 2
Non-trusted Small Business Servers?
"Mario Michela" wrote:

> I have SQL running on SBS Server A. It is a publisher and a distributor of a
> database that has 1 subscriber a SQL Server running on SBS Server 2. How does
> one replicate in a untrusted enviroment.
> there was also a free ware dll that allowed sql to invoke the ras dialer..
> does anyone have the valid url to this?

Replication between 2 SBS (small business server) Trusts

I have SQL running on SBS Server A. It is a publisher and a distributor of a
database that has 1 subscriber a SQL Server running on SBS Server 2. How does
one replicate in a untrusted enviroment.
there was also a free ware dll that allowed sql to invoke the ras dialer..
does anyone have the valid url to this?
Mario,
have a look at this article: http://support.microsoft.com/?id=321822
(HOW TO: Replicate Between Computers Running SQL Server in Non-Trusted
Domains or Across the Internet).
HTH,
Paul Ibison
|||ooops i spoke too soon..
This Q article had only 2 paragraphs that mentioned connection between 2
non-trusted domains. essentially it suggested creating a server agent account
on both machines. it says you 'must set up pass through authentication'.
There is was some data missing from the article.
1) How do you set up 'pass through authentication" via a SQL Agent Account?
2) Assuming 'Pass Through' is enabled, how does one reference the SBS Server?
a) 'Local Area Connection' IP Address (not likely) 192.168.0.2 (private)
b) Local Server Name. MyServer
c) FQDN MyCompany.MyServer.
d) Public Resolvable Domain Name MyCompany.com
i) With extension .com
ii) Without extension
e) Network Connection IP Address of Server 68.XXX.XXX.217 (Public)
None of the above options worked for me, response "Server doesn't exsist or
Access denied" (which is it? MDAC doesn't even know if the Server Exists?
What’s with that?)
I found the information sources lacking. None seemed to illustrate a Point A
to Point Z scenario on SBS. This is not a Version 1 product and being that
trusts are not allowed it's conceivable that many companies would be
attempting non-trusted replication.
PS, I've checked Kbase, SQL BOL, 4 MVP sites, Newsgroups, Online Concierge
and SSWUG. I was exposed to answer bits, in addition to the above mentioned
options, there was mentioned RPC over TCP, RPC over UDP, Linked server
options, Remote server options, SSL options, replication via Backup and
Restore, replication via output files, Replication via terminal services
etc..
Now, I'm a person of reasonable intelligence, willing to the put the time
and effort into research, but am I wrong here when I suggest that the
documentation is all over the map? I will be posting this reply in both the
SQL Connectivity and SQL Replication newsgroups. In my opinion Microsoft does
a great job of documenting the scope and detail of it's technologies but
often falls short when it comes to implementation documentation. They are 2
distinct types of technical writing. I love Microsoft products and take the
time to scribe my opinion in hopes that it will yield stronger product line.
With that said, I ask again for a -concise, thorough, list of steps on how
to set up a push transaction based SQL replication subscription between 2
Non-trusted Small Business Servers?
"Paul Ibison" wrote:

> Mario,
> have a look at this article: http://support.microsoft.com/?id=321822
> (HOW TO: Replicate Between Computers Running SQL Server in Non-Trusted
> Domains or Across the Internet).
> HTH,
> Paul Ibison
>
>
|||Mario,
much of this article applies to your situation, although admittedly it's not
immediately obvious
Remember to set up the alias using the client network utility, rather than
the IP address.
Try using sql server authentication rather than pass-through.
Set up FTP forthe initial snapshot if it isn't a nosync one.
If you want things a little easier, you can use a VPN.
HTH,
Paul Ibison
"Mario Michela" <MarioMichela@.discussions.microsoft.com> wrote in message
news:75DB0BE3-9379-4C57-BC35-3E62104060E7@.microsoft.com...
> ooops i spoke too soon..
> This Q article had only 2 paragraphs that mentioned connection between 2
> non-trusted domains. essentially it suggested creating a server agent
account
> on both machines. it says you 'must set up pass through authentication'.
> There is was some data missing from the article.
> 1) How do you set up 'pass through authentication" via a SQL Agent
Account?
> 2) Assuming 'Pass Through' is enabled, how does one reference the SBS
Server?
> a) 'Local Area Connection' IP Address (not likely) 192.168.0.2
(private)
> b) Local Server Name. MyServer
> c) FQDN MyCompany.MyServer.
> d) Public Resolvable Domain Name MyCompany.com
> i) With extension .com
> ii) Without extension
> e) Network Connection IP Address of Server 68.XXX.XXX.217 (Public)
> None of the above options worked for me, response "Server doesn't exsist
or
> Access denied" (which is it? MDAC doesn't even know if the Server Exists?
> What's with that?)
> I found the information sources lacking. None seemed to illustrate a Point
A
> to Point Z scenario on SBS. This is not a Version 1 product and being that
> trusts are not allowed it's conceivable that many companies would be
> attempting non-trusted replication.
> PS, I've checked Kbase, SQL BOL, 4 MVP sites, Newsgroups, Online Concierge
> and SSWUG. I was exposed to answer bits, in addition to the above
mentioned
> options, there was mentioned RPC over TCP, RPC over UDP, Linked server
> options, Remote server options, SSL options, replication via Backup and
> Restore, replication via output files, Replication via terminal services
> etc..
> Now, I'm a person of reasonable intelligence, willing to the put the time
> and effort into research, but am I wrong here when I suggest that the
> documentation is all over the map? I will be posting this reply in both
the
> SQL Connectivity and SQL Replication newsgroups. In my opinion Microsoft
does
> a great job of documenting the scope and detail of it's technologies but
> often falls short when it comes to implementation documentation. They are
2
> distinct types of technical writing. I love Microsoft products and take
the
> time to scribe my opinion in hopes that it will yield stronger product
line.[vbcol=seagreen]
> With that said, I ask again for a -concise, thorough, list of steps on how
> to set up a push transaction based SQL replication subscription between 2
> Non-trusted Small Business Servers?
>
>
> "Paul Ibison" wrote:
|||Yes the article is good in many respects, i learned a lot, perhaps a bit too
much in that it introduced several differernt approches. ok, now you mention
alaising using the client utility? there are only 3 boxes, can you give me an
example of what to put in them. remember this is a push from the publisher.
so wouldn't the publisher connect to the client server? MS is mixing
mediphores. Am i wrong to assume that data flows from a server (publisher)
using a distributer to a client (subscriber). This can't be that difficult.
currently i have created a domain user (admin rights) on both servers, both
have the same username and password. I"ve also gone into routing/ip
routing/nat/basic firewall and in the public ip address added the following:
Desc of Svc: SQLServer
On public Interface
Using TCP
Incoming Port: 1433
Priv IP:192.168.10.2
OutGoing port: 1433
Desc of Svc: SQLServer UDP
On public Interface
Using UDP
Incoming Port: 1434
Priv IP:192.168.10.2
OutGoing port: 1434
I've been trying to test my creating a UDL. (both servers have an Admin
account, both have the same password -so windows authenticed).
now because the documentation can't seem to use consistant mediphoores. i've
done every on both server in a despirate attempt to shotgun my way into
success (not the best way to go about things but look at what i've got to
work with.)
ok now on to ailases. (again i will build identicle alaises on both machines
untill advised otherwise).
Server Alais: aawwserver (machine/server name)
Server Name: aawwserver
Dynamically Determine port.
is there a wizard or some sort of tool i should be using for this?
i can't believe that this entire process up till this point is covered in a
single paragraph.
At one point I had the whole set up using a vpn (not practicle) but the
transaction agent failed because it couldn't drop a function because it was
being used by replication(funny i never dropped it? why should the
replication agent) so i removed replication and attempted to start from
scratch. I've been at this for aprox 40 hours non-stop not including the 4
days prior. if this is what is concidered a reasonable implimemtation I have
to question the product. So for the sake of my sanity Please Please, provide
an example. using the following 'aliases' (sorry i couldn't resist)
-Example Name-
Publisher:
Machine Name: srvPub
Public IP: 0.0.0.1
Private IP: 0.0.0.2
database: DBPub
Domain: DomPub.com
sql Agent Acct: agtRep
sql Agent Password: agt@.Rep
Subscriber:
Machine Name: srvSub
Public IP: 0.0.0.3
Private IP: 0.0.0.4
database: DBSub
Domain: DomSub.com
sql Agent Acct: agtRep
sql Agent Password: agt@.Rep
The Challange:
Can anyone take the variables I've listed and form them into a coherent set
of instructions.
This has been more stressfull then having to sing the national anthem naked
at the olympics..
Thanks you so very much, for your assistance. .
"Paul Ibison" wrote:

> Mario,
> much of this article applies to your situation, although admittedly it's not
> immediately obvious
> Remember to set up the alias using the client network utility, rather than
> the IP address.
> Try using sql server authentication rather than pass-through.
> Set up FTP forthe initial snapshot if it isn't a nosync one.
> If you want things a little easier, you can use a VPN.
> HTH,
> Paul Ibison
>
> "Mario Michela" <MarioMichela@.discussions.microsoft.com> wrote in message
> news:75DB0BE3-9379-4C57-BC35-3E62104060E7@.microsoft.com...
> account
> Account?
> Server?
> (private)
> or
> A
> mentioned
> the
> does
> 2
> the
> line.
>
>
sql

Replication between 2 SBS (small business server) Trusts

I have SQL running on SBS Server A. It is a publisher and a distributor of a
database that has 1 subscriber a SQL Server running on SBS Server 2. How doe
s
one replicate in a untrusted enviroment.
there was also a free ware dll that allowed sql to invoke the ras dialer..
does anyone have the valid url to this?-- Current Standings (taken from my post on the SBS Site) --
I posted on the SQL server site and was referred to Q321822. This Q article
had only 2 paragraphs that mentioned connection between 2 non-trusted
domains. essentially it suggested creating a server agent account on both
machines. it says you 'must set up pass through authentication'. There is wa
s
some data missing from the article.
1) How do you set up 'pass through authentication" via a SQL Agent Account?
2) Assuming 'Pass Through' is enabled, how does one reference the SBS Server
?
a) 'Local Area Connection' IP Address (not likely) 192.168.0.2 (private)
b) Local Server Name. MyServer
c) FQDN MyCompany.MyServer.
d) Public Resolvable Domain Name MyCompany.com
i) With extension .com
ii) Without extension
e) Network Connection IP Address of Server 68.XXX.XXX.217 (Public)
None of the above options worked for me, response "Server doesn't exsist or
Access denied" (which is it? MDAC doesn't even know if the Server Exists?
What’s with that?)
I found the information sources lacking. None seemed to illustrate a Point A
to Point Z scenario on SBS. This is not a Version 1 product and being that
trusts are not allowed it's conceivable that many companies would be
attempting non-trusted replication.
PS, I've checked Kbase, SQL BOL, 4 MVP sites, Newsgroups, Online Concierge
and SSWUG. I was exposed to answer bits, in addition to the above mentioned
options, there was mentioned RPC over TCP, RPC over UDP, Linked server
options, Remote server options, SSL options, replication via Backup and
Restore, replication via output files, Replication via terminal services
etc..
Now, I'm a person of reasonable intelligence, willing to the put the time
and effort into research, but am I wrong here when I suggest that the
documentation is all over the map? I will be posting this reply in both the
SQL Connectivity and SQL Replication newsgroups. In my opinion Microsoft doe
s
a great job of documenting the scope and detail of it's technologies but
often falls short when it comes to implementation documentation. They are 2
distinct types of technical writing. I love Microsoft products and take the
time to scribe my opinion in hopes that it will yield stronger product line.
With that said, I ask again for a -concise, thorough, list of steps on how
to set up a push transaction based SQL replication subscription between 2
Non-trusted Small Business Servers?
"Mario Michela" wrote:

> I have SQL running on SBS Server A. It is a publisher and a distributor of
a
> database that has 1 subscriber a SQL Server running on SBS Server 2. How d
oes
> one replicate in a untrusted enviroment.
> there was also a free ware dll that allowed sql to invoke the ras dialer..
> does anyone have the valid url to this?