Prev: SQL server message
Next: How to restore a .bak from full-recovery mode without trans logs
From: TheSQLGuru on 9 Jan 2008 09:00
First thing I would check for is something (i.e. firewall) blocking port
1434 to/from the machines that don't get the info and the servers. IIRC
that is the tcp port used for 'hey, are you a sql server and if so how are
you doing' stuff.

--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net


<bringmewater(a)gmail.com> wrote in message
news:699f9f1f-2eff-48da-964f-9ecf5d90188b(a)v46g2000hsv.googlegroups.com...
> thanks for they reply. any idea why it works on some of our 2000
> servers and not others?


From: bringmewater on 9 Jan 2008 13:05
it's port 1433 and since i can connect I know that port is not blocked
From: bringmewater on 10 Jan 2008 07:11
is it just a bug and doesn't work right with sql 2000 dbs ?
From: Tibor Karaszi on 11 Jan 2008 10:29
Hmm, is that really determined from the communication with SQL Server Browser (via 1434)? I thought
that this information is drawn from some other protocol (something closer to basic windows Service
API's)? I believe for instance that once upon a time this was only available though Named Pipes (not
IP Sockets) - probably in the 6.x days. If one has some more network knowledge than I do, it would
be interesting to trace or similar port numbers etc when one starts SSMS/EM.

For instance, I can stop (and disable) the SQL Server browser service and my SSMS still tell me that
my default instance is started where my two named instances are stopped.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"TheSQLGuru" <kgboles(a)earthlink.net> wrote in message news:13o9kr1cd80c78(a)corp.supernews.com...
> First thing I would check for is something (i.e. firewall) blocking port 1434 to/from the machines
> that don't get the info and the servers. IIRC that is the tcp port used for 'hey, are you a sql
> server and if so how are you doing' stuff.
>
> --
> Kevin G. Boles
> Indicium Resources, Inc.
> SQL Server MVP
> kgboles a earthlink dt net
>
>
> <bringmewater(a)gmail.com> wrote in message
> news:699f9f1f-2eff-48da-964f-9ecf5d90188b(a)v46g2000hsv.googlegroups.com...
>> thanks for they reply. any idea why it works on some of our 2000
>> servers and not others?
>
>

From: Beth on 18 Jan 2008 13:46
Hey, I'm seeing the same thing, except the server is 2005 on someone else's
box.
It's annoying because it takes about 20 seconds to connect and I thought the
whole idea behind registering servers is that it doesn't have to go through
the re-authentication again.

Is this normal?
Is there something I can do to get my white circle green like the SQLExpress
one I don't use?

Thanks for any info.

"bringmewater(a)gmail.com" wrote:

> What does it mean when my servers have a white circle instead of a
> green circle with a white arrow in it in SQL Server Management
> Studio? My dbs are 2000.
>
> Thanks
>
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: SQL server message
Next: How to restore a .bak from full-recovery mode without trans logs