October 7, 2002 at 6:00 pm
Hi,
I need to connect to a sql server over the network. There are two instances residing on the same machine. I am trying to connect via iis, and when I use the ip + port number I am unable to do so. Connecting the the default instance is OK. Do you have any suggestions or ideas as to what I may be doing wrong.
Many thanks,
Suada
October 7, 2002 at 6:17 pm
Determine the SQL Server instance port number.
To find the SQL Server instance port number:
On the Microsoft SQL Server 2000 server, start the SQL Server Network Utility.
Click the General tab, and then select the instance you want from the Instances drop-down menu.
Highlight TCP/ IP, and then click Properties. The port number for this instance is shown. Write down this port number for use later.
Configure the server alias on the client computer in client network utility, then you can use the alias.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
October 8, 2002 at 1:27 am
How are you entering ip+port number? It's not entered in the same way as a web address, but instead with a comma for port, like this:
192.168.0.123,1433
--
Chris Hedgate @ Apptus Technologies (http://www.apptus.se)
October 8, 2002 at 4:23 am
You can also configure an alias using the client utility.
Andy
October 8, 2002 at 12:11 pm
Thank you very much for your replies. Specifying the port number with a comma did the trick when connecting from an IIS server on the same domain.
Unfortunately I still have trouble connecting from the IIS server which is residing on a different domain. Connecting to the default sql server works fine.
The error I get is oledb for odbc provider error 80004005.
October 8, 2002 at 4:11 pm
What does your connection string look like?
Are you sure that the servers can reach eachother across the domains? Can you ping the SQL server from the IIS server?
--
Chris Hedgate @ Apptus Technologies (http://www.apptus.se)
October 8, 2002 at 6:21 pm
Also, if the other server is on a seperate domain you will not be able to use Windows Authentication unless you have a proper trust relationship established between the two domains. I suggest get a NT person to do this if you have not done. Otherwise use SQL Server authentication.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
October 10, 2002 at 10:46 am
We finally solved our problem! All that needed to be done was to install the latest version of MDAC on the IIS server.
Thank you for your help.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply