August 13, 2002 at 10:48 am
can you create a linked server that is at another site? If so, do you need to just allow remote access on your Win2k server and have the other server logged in? Any help is appreciated.
August 13, 2002 at 1:04 pm
You'll have to worry about anything that may be in the middle such as firewalls and the like. Can you give us a little more information about the setup?
K. Brian Kelley
http://www.truthsolutions.com/
K. Brian Kelley
@kbriankelley
August 13, 2002 at 3:30 pm
here's the setup. Server A, is located at building A, within a private network. A third party points the public IP to one of our private LAN addresses. Server B will be set up at building B with its own dedicated public IP address. I want to connect from A to B. I am familiar with the ability to set up linked servers within your network, but how would you set up linked servers not within your LAN. Would you just allow the Server B remote access to Server A, making it a part of your network. I only say this because I see when setting up linked servers in sp_addlinkedserver it appears to recognize names, and not IP addresses. Did I clear this up or have I made this confusing. Again, thanks for posting and your help.
August 13, 2002 at 3:37 pm
I am not sure of all the background for IP designations, but within our organization we have an intranet and and internet with a firewall in between. I have some jobs that run using the alias IP name designated in the SQL Client Configuration tool. I set both sides of the fence up and the jobs run well.
As a side note... We were using linked servers to do this, but our push/pull of data was not that frequent and we chose to not have the linked server channel available all the time. The sql job (dts package) opens and closes the connection only for the duration of the job.
Hope this sheds some light for you...
Jody
August 13, 2002 at 4:07 pm
Thanks, Jody. So, by setting up a named-alias, and its parameters including IP address and port number, I could reference this name in sp_addlinkedserver, or in a dts package and it would work assuming that the other end would allow access to the login name specified. Is this right. I think I'm starting to get the picture here.
August 13, 2002 at 4:08 pm
I'm sorry. Did you mean the server alias set up on both sides as well?
August 13, 2002 at 4:26 pm
On each sql server I run the Server Network Utility to establish the listening port and IP of the Server. On the opposing sql server I run the Client Network Utility to establish the alias. I also turn off all protocols except TCP/IP.
The Alias name is referenced from the linked server set up or from the DTS package and a valid login.
One of the changes we made to our sql environment was to establish domain accounts for SQL services to run under. You have to set the account enabled to run as service and make it a member of the local server administrator group. It is key that SQLAgent be running as this account as well.
Another security step that we take is to remove the builtin Admins in SQL Server and have created a domain group for DBA membership that replaces that account.
I should mention that we have a Windows 2000 and mixed sql 7/2000 server environments.
Glad to help, keep asking away...
Jody
August 13, 2002 at 4:42 pm
thanks jody, that was great help. I'll give that a go. Also, good tip on the sql accounts. Thank god for this site and the people on it.
-Pat
August 13, 2002 at 4:43 pm
You are most welcome, Pat and an Amen to that too!
Jody
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply