April 18, 2007 at 2:18 am
Hi,
I've just installed VS.Net 2005, and then 2 instances of SQL Server 2000 on my desktop and my notebook. If it makes a difference, I am not sure whether I installed both instances, and then applied SP4 to them, or whether I installed 1 instance, applied SP4, and then the other.
Basically, I cannot connect to the named instance because it will not report in the browser list - I've viewed the data returned from a UDP packet sent to the machine, and it only reports the default instance, and the SQLEXPRESS - not my second named instance. I can obviously work with it in Enterprise manager and in query analyser on the machine, but no other machine can connect because the browser will not return the information when requested.
I've checked all I know - it's on port 1435 (set by me), and it's not hidden. I can telnet from a remote machine to both 1433 and 1435, so it's not a firewall issue - my biggest problem is that SQL Browser simply doesn't acknowledge that instance - any ideas how to fix that? FWIW I think it's the SQL Browser for 2005, not 2000.
Cheers,
Dino
April 19, 2007 at 5:55 am
Dean,
the SQL Browser service is new in 2005 and as far as I know it won't effect SQL 2000 instances.
Did you try creating an alias for your instance?
Markus
[font="Verdana"]Markus Bohse[/font]
April 19, 2007 at 12:29 pm
Have you tried connecting using the IP Address? Such as 192.168.1.101\InstanceName ?
April 19, 2007 at 1:39 pm
Problem is, to connect to an instance, you have to query whatever is listening to port 1434 UDP to get the TCP port the named instance is listening on - and port 1434 was replying that my named instance did not exist, therefore nothing will work - machine name, IP address, nothing because it will have no port to connect to.
April 20, 2007 at 12:48 am
Dean,
if your named instance uses a fixed port you can define an alias on the client. In that case the client don't need to query the UDP port.
Markus
[font="Verdana"]Markus Bohse[/font]
April 20, 2007 at 1:28 am
True, but I'd rather solve the problem of the non-reporting than get around it.
One reason is that this app is available on or offline, and I use the port 1434 to do very quick detection of whether the server is online or not - otherwise I have to wait for a connection timeout, and passing lower timeout values with the connection string doesn't seem to work - it still seems to lock the app for about 30 seconds - and given the app is Outlook and users want to get their mail, it's not really what I want.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply