We are using anonymouse pull subscriptions over the internet. We are not
using VPN.
The physical SQL Server is called SQL22Server. We have a Domain assigned to
it called something like company.com.
However, I found that on the client machine, I had to put in a hosts entry
to route SQL22Server to the IP address. I was hoping I could just use the
domain name.
This creates an administrative overhead because we have to do add a host
entry during the client install instead of having just assigning value to the
merge object.
If I try the domain, the error I get is: The remote server does not exist or
has not been designated as a valid Publisher.
I created the replication using the SQL22Server name.
Thanks,
Buzz
use the activeX scripts to deploy your subscriptions. In it there are
PublisherNetwork, DistributorNetwork, PublisherAddress, and
DistributorAddress properties. These map to the entries you would otherwise
put in your CNU or hosts file to make this work.
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
"Buzz" <buzz@.online.nospam> wrote in message
news:2C0E041F-5DA1-4DAB-B747-E52E2196395D@.microsoft.com...
> We are using anonymouse pull subscriptions over the internet. We are not
> using VPN.
> The physical SQL Server is called SQL22Server. We have a Domain assigned
to
> it called something like company.com.
> However, I found that on the client machine, I had to put in a hosts entry
> to route SQL22Server to the IP address. I was hoping I could just use the
> domain name.
> This creates an administrative overhead because we have to do add a host
> entry during the client install instead of having just assigning value to
the
> merge object.
> If I try the domain, the error I get is: The remote server does not exist
or
> has not been designated as a valid Publisher.
> I created the replication using the SQL22Server name.
> Thanks,
> Buzz
|||Thanks for the quick reply.
I am publishing what I found for the newsgroup.
For us, the publisher and the distributer are the same machine. We are using
FTP for the initial snapshot. We are using SQL Server 2000 SP4 on the server
and MSDE SP4 on the laptop subscribers.
I found I did not need the distributer values because my distributer and
publisher where the same machine. I will most likely set them anyway so that
someday in production I can have a different distributer.
Here are the subscriber properties of the Merge object:
.Distributor = "SQL22Server"
.DistributorSecurityMode = SECURITY_TYPE.DB_AUTHENTICATION
.DistributorAddress = "company.com"
.DistributorNetwork = NETWORK_TYPE.TCPIP_SOCKETS
.DistributorLogin = "login"
.DistributorPassword = "password"
.Publisher = "SQL22Server"
.PublisherAddress = "company.com"
.PublisherDatabase = "data"
.PublisherNetwork = NETWORK_TYPE.TCPIP_SOCKETS
.Publication = "data"
.PublisherSecurityMode = SECURITY_TYPE.DB_AUTHENTICATION
.PublisherLogin = "login"
.PublisherPassword = "password"
The one last thing to make sure is that when setting up the FTP on the
server, use the PublisherAddress value. So "company.com" so that the
subscriber hits ftp://company.com/.
Also if you do this in production be careful the change to the FTP address
causes the publication to force a recreation of the initial snapshot.
Thanks,
Buzz
"Hilary Cotter" wrote:
> use the activeX scripts to deploy your subscriptions. In it there are
> PublisherNetwork, DistributorNetwork, PublisherAddress, and
> DistributorAddress properties. These map to the entries you would otherwise
> put in your CNU or hosts file to make this work.
> --
> 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
> "Buzz" <buzz@.online.nospam> wrote in message
> news:2C0E041F-5DA1-4DAB-B747-E52E2196395D@.microsoft.com...
> to
> the
> or
>
>
|||Hi Buzz,
It looks more than a network issue.
- Could you PING SQL22Server from client and get the response?
- Could you telnet SQL22Server from client use the command like below
telnet <SQL22Server Domain Name>: 1433
- Do you have firewall between server and client? Have you open the TCP
port for them?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
Monday, March 12, 2012
Replication over the Internet - Resolving server name
Labels:
anonymouse,
database,
domain,
internet,
microsoft,
mysql,
notusing,
oracle,
physical,
pull,
replication,
resolving,
server,
sql,
sql22server,
subscriptions,
vpn
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment