connecting to an instance name in SQL Server, remotely

[LSV]

Hello.

I have a SQL Server that, say, has an instance name of ibm/mydata.

On a local workstation, I open ODBC and establish a connection easily. Ibm/mydata automatically appears as the path when I'm using the ODBC wizard.

However, take that worstation to a remote location and I cannot see Ibm/mydata.
I understand that since "IBM" is my server's name and I have no name resolution enabled, I cannot see that path.

I figured, however, that I could type the path such as serverIP/mydata, and it would work. It hasn't.

Note that I can connect to the Server hosting SQL server, remotely in any other way. I have all permissions; can login, edit files, etc., just not establish a connection to SQL. I get the message of "test failed", when trying to test the ODBC connection from the remote station.

Is there a configuration in SQL that enables me to use its IP instead of "ibm", or is this strictly a communications issue and I must enable DNS across the extranet?

Thank you. Leandro

 

[mrdenny]

What version of SQL, what Service Pack, and What OS?

IP should work fine instead of name service. Anything in the SQL Log or the Event log that would say that it's not accepting remote connections?

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[nrj1999]

You need at least MDAC version 2.6 on your client PC to connect to a named SQL Server instance so check that you have this first.

If you have this, when setting up the ODBC connection you reach a page where you input authentication details. On this page is a button called client configuration which takes you to the client network utility. Click on this button.

On the window which will be titled Add Network Library Configuration, make the server alias IBM, to use your example, then check the TCP/IP radio button and enter the IP address of your remote server in the server name box.
If you have more than one instance on the server, you will have to provide a port number but if there is only one you can check the dynamically determine port box.

Once you have entered all the information, click OK and you will be returned to the ODBC connection wizard. Fill in the rest of the details as you have been doing and you should be able to connect to the remote server.

This applies to a Windows 2000 client specifically but can be adapted to any windows version with a little common sense.

Hope this helps