Available server list 1

[NathanGriffiths]

I am using SQL Server 2000 and I've noticed that when SQL Server is displaying a list of available servers e.g. for New SQL Server Registration in Enterprise Manager, or Connecting to SQL Server in query analyser, that only some of the available servers are displayed.

Can anyone tell me whether its a client or server setting that affects which servers are displayed in the list, and if I can change this to ensure all available servers are displayed?

thanks,

Nathan

 

[FilthPig]

There's a Client Configuration utility in the program group that's installed with SQL Server, and it uses servers entered in there to build it's list of available servers. Marc Creviere

 

[NathanGriffiths]

Thanks Mark,

I think you mean the Client Network Utility? I've had a look at that and there are no servers explicitly listed there as far as I can tell, yet some servers still appear in the available list. The same servers appear for different client machines, so I'm guessing its something to do with the server settings?

Can you tell me how I would add a server using the Client Network utility?

As you can probably tell, I'm fairly new to SQL Server

thanks,

Nathan

 

[EdVassie]

The server list is built by pinging the SQL Server port on all machines in your network segment. If a response is received, the machine is added to the list. If no response, the machine is not added. This process is sometimes called Discovery.

Things that can stop discovery working are:

a) The SQL Server service was not active at the time you built the list. If it is not active, it is difficult for it to respond.

b) A SQL Server instance was configured to use a non-standard port. If it is listening on a different port, it will not hear your ping and will not respond.

c) The NT/W2K/XP configuration flag to hide the server is set. This might (or might not...) prevent discovery of the SQL Server instance.

d) The server is on a different network segment. It will not receive your ping.

Items a) and d) are the most likely cause of your problem.

Even if your server is not found by Discovery, you can force a registration by manually entering the server name. I have to do this to register instances at our BCO site, where SQL Server is normally not active.

Disclaimer: All information given is a personal opinion which may not match reality. This posting is a personal opinion only, and may not reflect reality.