June 16, 2008 at 11:25 am
Hi there. I've got a problem which I can't seem to solve. This is going to be lengthy as I will try to give maximum details so no misunderstanding 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.
From B, established VPN connection from B to A successfully using admin account in A. Address obtained with IP 192.168.1.82. Ping plauzun and plauzun.plauzundom.plyfoam.loca returns 192.168.1.1.
Using SSMS, connect to local server PLOUIS\PLOUIS
Under replication, New Subscriptions Publisher:
In Connect to Server, server name: PLAUZUN\PLAUZUN
returns: Cannot connect to PLAUZUN\PLAUZUN.
Additional information: TCP Provider, Error 0 and MSSQL Server Error: 10060
But if I connect to server PLAUZUN\PLAUZUN, 1433 in the object explorer, it is successful. If I try to use the above servername\instance, tcpport in the Subscription window I get
“SQL Server replication requires the actual server name to make a connection to the server. Connections through a server alias, IP address, or any other alternate name are not supported. Specify the actual server name, 'PLAUZUN\PLAUZUN'. (Microsoft.SqlServer.Express.Replication.Utilities)”
Any ideas at to what I must do?
June 16, 2008 at 2:41 pm
Having just come from the same church, different pew, check the following:
Surface configuration: Make sure that TCP/IP is enabled for SQL Server, and experiment with Named Pipes turned off and on (I don't think pipes matter, but TCP/IP must be enabled).
Check to make sure whether you are using SQL Server authentication or windows authentication. Then check again - in some screens I don't think the labeling is as clear as it should be. Be certain that you are using Impersonation, and that the IDs and passwords are IDENTICAL for both machines.
It's also possible that you may need to check the privileges granted to the ID on both servers.
Security diagnostics are, by design, ambiguous. So, you have to eliminate all possibilities, until you succeed in pushing through. Even after you succeed, it may be helpful to continue checking, and documenting all settings, so that the next time, you can avoid the issue or at least know where to look.
Hope this helps.
June 16, 2008 at 11:31 pm
Ok. Had to go out for a while. Will check everything you said soon and will update posting. Thanks.
June 18, 2008 at 5:00 am
It's all working correctly now. I had to add an alias as:
Alias name: PLAUZUN\PLAUZUN
TCP/IP Port: 1433
Server: PLAUZUN
at the PLOUIS server to do the job. Thanks for the inputs!
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply