Anmelden
 
HomeLibraryDownloadsSupportWebcasts & EventsCommunityForenBlogs
Ressourcen für IT-Professionals >
> 
> 
Replication Problem between 2 non trusted domains

Frage Replication Problem between 2 non trusted domains

  • Dienstag, 26. Februar 2013 11:16
     
     
    Anmelden
    0

    Hi guys

    I need a little help, I am new to SQL

    I have setup replication between two sql 2005 servers internally on the same network ( this was my testing environment)

    All works great replication was working well with all tables etc updating as they should

    Now this is where the problem started, I needed to replicate this between two remote servers so I did just that created the servers installed all service packs and lastest patched etc etc

    I created a vpn to connect them both I put in the ip to resolve the name in the host file

    And can now browse the servers between etc other via servername.domain.local this then executes the username and password box for windows.

    Right the next stage was to setup replication I have configure servsql to be the publisher, I then went onto Chatsql to setup the subscription but everytime I go to do this I get the following error message:

    TITLE: Connect to Server
    ------------------------------

    Cannot connect to servsql.domain.local

    SQL server replication requires the actual server name to make connection to the server.

    Connections through a server alias, ip address or any other alternate name are not supported

    Specify the actual server names, ServSQL (replication utilities )

    ------------------------------
    ADDITIONAL INFORMATION:
    I have google searched this problem and tried all user recommendations I've found.

    - I have correctly forwarded ports on my router (e.g. I can access the remote desktop from remote places without problem)

    - The Windows firewall is well configured, I have added ports 1433, 1434 and I've tried it even with windows firewall turned off.

    - I have enabled all protocols needed and revised all setting concerning remote connections within configuration manager and surface configuration

    Nothing has helped.

    • Bearbeitet ace27211 Dienstag, 26. Februar 2013 12:00
    •  
     

Alle Antworten

  • Dienstag, 26. Februar 2013 15:59
    Moderator
     
     
    Anmelden
    2

    what does this return on both server?

    select @@ServerName

    GO

    use master

    exec xp_cmdshell ' hostname'

    They must be the same - ignoring any instances.

    looking for a book on SQL Server 2008 Administration? http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search? http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

     
  • Mittwoch, 27. Februar 2013 10:42
     
     
    Anmelden
    0

    Hi Hilary


    thanks very much for your reply but I seemed to have progressed on, it seems like it was a issue with alias on the local and remote sql

    if you dont mind can i ask another question

    I am in the process of creating replication between 2 remote servers, server 1 is the distributor and publisher and server 2 is the subscription

    server 1
    windows 2003 server
    192.168.10.1 connected by vpn
    SQL 2005
    domain1.local

    server 2
    windows 2003 server
    192.168.10.1 connected by vpn
    SQL 2005
    domain2.local

    when i setup up the replication all looked fine until i looked at the sync status and is said

    The Agent could not be started

    an exception occurred while executing a transact-sql statement or batch

    sqlserveragent error request to run job
    server1-username blah blah blah

    from user sa refused because the job is already running from a request by user sa changed database context to technical error 22022

    I can't seem to locate what the problem is any help would be much appreciated

    thanks


     
  • Mittwoch, 27. Februar 2013 15:40
    Moderator
     
     
    Anmelden
    0

    Use replication monitor to see if the job you are interested in is already running. The log reader agent should always be running. The snapshot agent will run continuously until the snapshot is generated.

    The merge agent normally runs on a scheduled basis and will run until complete.

    The distribution agent by default will always be running.

    Now, there is a possiblity that something is messed up, the easiest way to fix this is to bounce SQL Server Agent, but don't do that until you confirm that the correct agents are running either continuously or on a scheduled basis.

    looking for a book on SQL Server 2008 Administration? http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search? http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941