sql server replicatoin requires actual server name to make a connection to the server

Question

Post reply

sql server replicatoin requires actual server name to make a connection to the server

radhakrishnanganesh

Valued Member

Points: 50
More actions
October 27, 2007 at 4:37 am

#176608

I have two servers at different location
In both servers sql2005 is installed and have the same database instances
I wanted to create a replication between these two servers,
one location has static ip
iam able to connect to the remote server using the static ip, while in the replication, it is not accepting the ip, it is asking for the server name,
how do i handle this situation.???
sql server replicatoin requires actual server name to make a connection to the server, it is not accepting the alias name or ip address.
help me out

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply

Deepak-405225 SSCertifiable Points: 6120 More actions · Answer 1

Can you pls check this link and see if it is helpful ?

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=203340&SiteID=1

Regards

Deepak

[font="Verdana"]- Deepak[/font]

zenprofit SSC Enthusiast Points: 148 More actions · Answer 2

This is exactly the same problem I am having. The referenced article did not help.

My post is here:

http://www.sqlservercentral.com/Forums/Topic420797-291-1.aspx

Please someone respond.

Big Data Man SSCrazy Eights Points: 8536 More actions · Answer 3

Hi,

You must use server names and not ip addresses when configuring replication. You can create an alias to workaround the name problem. As you mentioned, you can use ip addresses for other operations, but replication is one feature you cannot use an ip address.

Thanks,

Phillip Cox

radhakrishnanganesh Valued Member Points: 50 More actions · Answer 4

hi,

You cannot name your IP, by giving an alias name, sql server replication does not accept it.

*************

Procedure alias name for your IP

Edit hosts (windows\system\driver\etc - using notepad

xxx.xxx.xxx.xxx alias name

**************

this is not accepted in the replication.

Finally I have creaed a VPN between these two networks and in both the machins i have resolved the IP by a Name which is now valied between thse two machines. Once VPN is established, these two locations become a local network and now your replication works.

Thx anyways

r. ganesh

Big Data Man SSCrazy Eights Points: 8536 More actions · Answer 5

Hi,

I was referring to SQL Server Alias, but nevertheless its worked out for you.

Thank you,

Phillip Cox

Lowell SSC Guru Points: 323518 More actions · Answer 6

if your other SQL server has a dynamic IP, and you need a real hostname for it, look at the free services at dyndns.org.

you run a service on your remote server, and any time it's extranl ip changes, due to dialup, or DSL or CABLE changes, it updates the ip to the hostname;

for example, you might get a free account for the hostname PhillipCoxSQLServer.dydns.org

and the service just updates DYNDNS.ORG whenever the ip changes; that way your static IP server can always find PhillipCoxSQLServer.dydns.org

I use it all the time.

if the server is INTERNAL on your LAN, you do not need this service.

you can pay extra for your own domain name, and you can try it for free as explained above.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

alen teplitsky SSC-Dedicated Points: 30014 More actions · Answer 7

you will need to get with others in your IT department for this but here is what you can do

i'm guessing you don't have name resolution to the remote site. first you need to set up name resolution. if you can't use the current DNS zone, set up a new dummy DNS zone put in a host record for the remote server and an alias dns record (forgot the right name). you will also need to have static IP's or the right firewall policies set up for this

zenprofit SSC Enthusiast Points: 148 More actions · Answer 8

I will contact the IT dept and suggest they create 'dummy' DNS. Thank you. The replication is a big issue for us.

bbqchickenrobot SSC Rookie Points: 41 More actions · Answer 9

Can't u just use the hosts file to add an entry on both ends of the repl? You wont' need to actually create/mess with DNS records for this...

sql-661508 Newbie Points: 5 More actions · Answer 10

Cause:

This error has been observed on a server that had been renamed after the original installation of SQL Server, and where the SQL Server configuration function ‘@@SERVERNAME’ still returned the original name of the server. This can be confirmed by:

select @@SERVERNAME

go

This should return the name of the server. If it does not then follow the procedure below to correct it.

Remedy:

To resolve the problem the server name needs to be updated. Use the following:

sp_addserver 'real-server-name', LOCAL

if this gives an error complaining that the name already exists then use the following sequence:

sp_dropserver 'real-server-name'

go

sp_addserver 'real-server-name', LOCAL

go

If instead the error reported is 'There is already a local server.' then use the following sequence:

sp_dropserver old-server-name

go

sp_addserver real-server-name, LOCAL

go

Where the "old-server-name" is the name contained in the body of the original error.

Stop and restart SQL Server.

khuzaima Newbie Points: 9 More actions · Answer 11

Hi,

I have a sql serve 2008 running on my cloud server. I have configured a publisher in the server. Now I want to create a subscription in my local SQL 2008 server but I am getting this message

'sql server replication requires the actual server name to make a connection to the server'

Can anyone help me in this matter?

Khuzaima