newbie question re: hiding sql server from browse list 2

[namuheno]

Can someone tell me if it is possible to prevent a local/personal version of SQL Server 2000 from advertising itself in the server browse list. i.e. when you bring up Query Analyzer, you have a list of servers that are available and I would like to hide the presence of several servers from that list.

Thanks in advance

 

[TonyKhela]

Goto SQL Server Network Utility.

Choose TCP/IP, click on properties.

Select 'Hide Server' check box.

This should do it.

Hope it helps

TK

 

[namuheno]

Hmmmmm... Hence the term NEWBIE!! Many thanks.

 

[namuheno]

Even more apologies... since that didn't work. After checking "Hide Server" and restarting the local service, I still see that server listed in the "Select/Browse" list on another system' Query Analyzer.... Sorry to be a pain, but I'm out of my depth.

 

[TonyKhela]

Try disabling the Named Pipes (in Server Network Utility).
Leaving only TCP/IP as the 'Enabled Protocol'.
Try rebooting the client (to clear the cache) before trying 'Query Analyser'.
Let me know how you get on.
TK

 

[TonyKhela]

Also see

BUG: Hide Server Option Cannot Be Used on Multiple Instances of SQL Server 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;308091

 

[namuheno]

Thanks Tony,
This is obviously a twisted problem. I have been able, on a limited basis to get "some" machines to disappear, but removing named pipes causes other problems for some of the servers. I really appreciate your follow through in an effort to help. At the end of the day, I've taken a workaround tack and changed the security environment so it doesn't matter whether the particular machine I'm working with (that started this thread) is visible in the browse list or not. It's odd that the SQL browse list does not seem to be handled in the same way or by the same master browser as the regular domain info. I was under the impression that after the advent of NT only TCP/IP was required as a protocol for ALL network operations and therefore I, mistakenly, assumed that other protocols ignored the ramifications of the presence of 'other' channel protocols. Like netbios, I thought they would fade away as in a bad dream, but obviously they persist. Thanks again.