SQL Server Performance

replication over vpn

Discussion in 'SQL Server 2005 Replication' started by jedimaster, Jun 17, 2008.

  1. jedimaster New Member

    Hi there. I've got a problem which I can't seem to solve. This is goingto be lengthy as I will try to give maximum details so nomisunderstanding occurs.

    Location A
    Windows 2k3 Enterprise with latest updates and 2 NICs
    Active Directory, Computer name: PLAUZUN
    Domain: PLAUZUNDOM, FQDN: plauzun.plauzundom.plyfoam.local
    Running DNS, DHCP, RRAS and SQL Server 2005 with SP1
    DNS configured with 2 Forwarders (ISP DNS) and domain: plauzundom.plyfoam.local
    RRAS configured with static pool: 192.168.1.81 – 192.168.1.100 (20 addresses)
    NIC1 IP 192.168.1.1, Gateway: empty, DNS: 192.168.1.1
    NIC2 IP 192.168.11.2, Gateway: 192.168.11.1, DNS 192.168.1.1
    Netgear ADSL Router LAN: 192.168.11.1 and with public IP.

    Netgear firewall allow SQL(TCP 1433, UDP 1434) and VPN/PPTP(TCP 1723)

    Sql Server 2005 contains testdb1 published with merge replication.
    All TCP/IP interfaces protocols configured with static port 1433.


    Location B
    Windows 2k3 Enterprise with latest updates and 2 NICs
    Active Directory, Computer name: PLOUIS
    Domain: PLOUISDOM, FQDN: plouis.plouisdom.plyfoam.local
    Running DNS, DHCP, RRAS and SQL Server 2005 with SP1
    DNS configured with 2 Forwarders (ISP DNS) and domain: plouisdom.plyfoam.local
    RRAS configured with static pool: 192.168.2.81 – 192.168.2.100 (20 addresses)
    NIC1 IP 192.168.2.1, Gateway: empty, DNS: 192.168.2.1
    NIC2 IP 192.168.12.2, Gateway: 192.168.12.1, DNS 192.168.2.1
    Netgear ADSL Router LAN: 192.168.12.1 and with public IP.
    Netgear firewall allow SQL(TCP 1433, UDP 1434) and VPN/PPTP(TCP 1723)


    Registered dynamic address at dyndns.org for both locations.

    FromB, established VPN connection from B to A successfully using adminaccount in A. Address obtained with IP 192.168.1.82. Ping plauzun andplauzun.plauzundom.plyfoam.loca returns 192.168.1.1.
    Using SSMS, connect to local server PLOUISPLOUIS
    Under replication, New Subscriptions  Publisher:
    In Connect to Server, server name: PLAUZUNPLAUZUN
    returns: Cannot connect to PLAUZUNPLAUZUN.
    Additional information: TCP Provider, Error 0 and MSSQL Server Error: 10060

    Butif I connect to server PLAUZUNPLAUZUN, 1433 in the object explorer, itis successful. If I try to use the above servernameinstance, tcpportin the Subscription window I get

    “SQL Server replicationrequires the actual server name to make a connection to the server.Connections through a server alias, IP address, or any other alternatename are not supported. Specify the actual server name,'PLAUZUNPLAUZUN'. (Microsoft.SqlServer.Express.Replication.Utilities)”

    Any ideas at to what I must do?


  2. ghemant Moderator

  3. jedimaster New Member

    Yes that's how it it. Forgot to mention that. sqlService is a local admin account on each servers with same login/password user SQL Agent. I've used the same account for Publishers and at the Subscribers also.
  4. ghemant Moderator

    when I did this I have faced a problem in connecting subscriber and the issue is distributer was not able to identify and resolve subscriber by its actual physical netbios name i.e. subscriber1, where as it can able to find and ping it with fully qualified dns name i.e. subscriber1.somedomain.local. We had a call with our network team and has some workaround (adding some entry to hosts file and so on) to get it done which finally allowed to connect both machine. I would suggest to check this options with your network team and see if firewall is properly set.
  5. satya Moderator

    To correct the issue you have to ensure the servername (@@SERVERNAME) matches to the actual machine or instance name.
  6. jedimaster New Member

    It's all working correctly now. I had to add an alias as:
    Alias name: PLAUZUNPLAUZUN
    TCP/IP Port: 1433
    Server: PLAUZUN

    at the PLOUIS server to do the job. Thanks for the inputs!

Share This Page