I am trying to setup a merge (push) replication to a server/database
in a
remote network. I created the publication and connected to the remote
network using VPN but cannot register nor see the remote sql server.
In sql
server 2000, I was able to register the server in my Enterprise
Manager
(after creating an alias) and then created the push subscription. I
connect
to the remote network server using VPN. How do I go about doing this
in SQL
Server 2005? The publisher is a WorkGroup edition while the subscriber
is
standard edition. Authentication is set to both win and sql and
verified
the user and password used to attempt registration. Any help will be
greatly appreciated.
Create an alias on the publisher to the subscriber. Use client network
utility to do this, and for the server name use its fully qualified domain
name. Try to ping both servers from each other.
You may have to use anonymous subscribers to get this to work if you can't
map an unc drive between the two.
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
<pete970t@.gmail.com> wrote in message
news:1182891307.332293.251610@.u2g2000hsc.googlegro ups.com...
>I am trying to setup a merge (push) replication to a server/database
> in a
> remote network. I created the publication and connected to the remote
> network using VPN but cannot register nor see the remote sql server.
> In sql
> server 2000, I was able to register the server in my Enterprise
> Manager
> (after creating an alias) and then created the push subscription. I
> connect
> to the remote network server using VPN. How do I go about doing this
> in SQL
> Server 2005? The publisher is a WorkGroup edition while the subscriber
> is
> standard edition. Authentication is set to both win and sql and
> verified
> the user and password used to attempt registration. Any help will be
> greatly appreciated.
>
Showing posts with label aremote. Show all posts
Showing posts with label aremote. Show all posts
Wednesday, March 7, 2012
Connecting to a remote sql server
Hi,
I have a web application installed on a server. I want to connect to aremote database server. I have access to both the servers, I can assignany user privileges or settings that are needed. How do I do this? Itried it the usual way, specifying the conn string and opening theconn, and expectedly it throwed an sql server does not exists error.
Thanks.
When you say you specifiy the connection string, I'm assuming it's a correct string, but you didn't give us any info about the string - - Are you trying an explicit logon (uid/pwd) or Windows Authentication?
|||I am trying an explicit logon with username and password. The string isthe same one you normally use if you are connecting to a localdatdbase. I just tried changing the server name to the remote servername. Everything else is same.
|||That should work. The format for a local string will work for a remote string - if using SQL Authentication (explicit username and passwords).
The only difference is instead of a local IP (e.g., 127.0.0.1) or server name, use an IP accessiable from your webserver (e.g., 123.123.123.123, or mydatabase.mywebsite.com), whether private or public.
Of course, if you're getting "remote server cannot be found" kind of message, it could be firewall issue. Connecting this way to any SQL Server (local or remote) requires the correct port to open and reachable (default for SQL Server is 1433).
Some things to also keep in mind are the fact that your connection string is being sent over your private or public network (i.e., the internet) unencrypted, and that making open internet connections to SQL Server may require special licensing (as some have suggested).
Hope that helps.
|||Thanks Scott.
I have a web application installed on a server. I want to connect to aremote database server. I have access to both the servers, I can assignany user privileges or settings that are needed. How do I do this? Itried it the usual way, specifying the conn string and opening theconn, and expectedly it throwed an sql server does not exists error.
Thanks.
When you say you specifiy the connection string, I'm assuming it's a correct string, but you didn't give us any info about the string - - Are you trying an explicit logon (uid/pwd) or Windows Authentication?
|||I am trying an explicit logon with username and password. The string isthe same one you normally use if you are connecting to a localdatdbase. I just tried changing the server name to the remote servername. Everything else is same.
|||That should work. The format for a local string will work for a remote string - if using SQL Authentication (explicit username and passwords).
The only difference is instead of a local IP (e.g., 127.0.0.1) or server name, use an IP accessiable from your webserver (e.g., 123.123.123.123, or mydatabase.mywebsite.com), whether private or public.
Of course, if you're getting "remote server cannot be found" kind of message, it could be firewall issue. Connecting this way to any SQL Server (local or remote) requires the correct port to open and reachable (default for SQL Server is 1433).
Some things to also keep in mind are the fact that your connection string is being sent over your private or public network (i.e., the internet) unencrypted, and that making open internet connections to SQL Server may require special licensing (as some have suggested).
Hope that helps.
|||Thanks Scott.
Subscribe to:
Posts (Atom)