Problem with osql.exe -L

Hi Everyone,
I'm facing a small problem. Whenever I execute osql.exe -L command it lists all the server on the network except my local server instance (not default instance) and other similar server instance names on the network.
Earlier it use to list all the server instance but all of a sudden stopped listing.
What can be the problem? Please help me to rectify this issue.
Thanks in adv.
Regards,
BGS
OSQL -L uses the ODBC SQLBrowseConnect functionality. It's
not guaranteed to give a complete list due to broadcast
issues, network routers/subnet issues, instances may not
respond within the timeout period, etc. You can find issues
listed here:
http://www.sqldev.net/misc/ListSQLSvr.htm
-Sue
On Wed, 1 Jun 2005 20:15:46 +0530, "Gururaj Badam"
<gururajb@.msn.com> wrote:

>Hi Everyone,
>I'm facing a small problem. Whenever I execute osql.exe -L command it lists all the server on the network except my local server instance (not default instance) and other similar server instance names on the network.
>Earlier it use to list all the server instance but all of a sudden stopped listing.
>What can be the problem? Please help me to rectify this issue.
>Thanks in adv.
>Regards,
>BGS
|||Sue,
Is ListAvailableSQLServers in SQL-DMO is also same as "osql -L" command?
Actually I'm trying to populate a ComboBox with list of all the SQL Servers
on the network and set the default to the Local Server (desired instance).
Can you suggest some other better mechanism which can be used to acheive the
same?
-BGS
|||ListAvailableServers is also based on the ODBC function
SQLBrowseConnect. If you need a guaranteed list and are
running SQL 2000, you could register all SQL Servers in AD
and go through AD to list all of SQL Servers.
-Sue
On Thu, 2 Jun 2005 09:57:10 +0530, "Gururaj Badam"
<gururajb@.msn.com> wrote:

>Sue,
>Is ListAvailableSQLServers in SQL-DMO is also same as "osql -L" command?
>Actually I'm trying to populate a ComboBox with list of all the SQL Servers
>on the network and set the default to the Local Server (desired instance).
>Can you suggest some other better mechanism which can be used to acheive the
>same?
>-BGS
>
|||Sue,
Actually I'm not using SQL 2k but MSDE installation. It is a product, I
can't ask the client to install SQL Server 2000.
That's the reason I'm packing the MSDE along with the application
installation package.
-BGS
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:g9ut91daj141d35g8v2dn133q713uo9ieq@.4ax.com...
> ListAvailableServers is also based on the ODBC function
> SQLBrowseConnect. If you need a guaranteed list and are
> running SQL 2000, you could register all SQL Servers in AD
> and go through AD to list all of SQL Servers.
> -Sue
>
|||MSDE is SQL Server, so everything that Sue mentioned still applies.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Gururaj Badam" <gururajb@.msn.com> wrote in message news:OV9E6C3ZFHA.2916@.TK2MSFTNGP14.phx.gbl...
> Sue,
> Actually I'm not using SQL 2k but MSDE installation. It is a product, I
> can't ask the client to install SQL Server 2000.
> That's the reason I'm packing the MSDE along with the application
> installation package.
> -BGS
>
> "Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:g9ut91daj141d35g8v2dn133q713uo9ieq@.4ax.com...
>
|||Tibor,
How can I ask the user of my product to register the SQL Server with the AD,
that looks odd.
Is there any other way to approach this problem?
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23AYiWX3ZFHA.3040@.TK2MSFTNGP14.phx.gbl...
> MSDE is SQL Server, so everything that Sue mentioned still applies.
> --
> Tibor Karaszi, SQL Server MVP