(Win2K Adv Server; Win 2K pro and XP pro wkstations)
Just installed sp3a on server and wkstations and now can't connect to
server.
I try to create a new SQL server registration, I see the instance
(TCASERVER\SQL2K and it is also running!). I have tried Windows
Authentication and SQL server authentication and get the following for both:

Invalid connection
Connection Open (Invalid Instance())

I can connect to sql server on the server and all workstations log in just
fine.
I have admin rights on my two wkstations too.

Help!

Hello Sydney, i had the same problem with the connection. I still
don't now how to fix but i know a way to work around:

On the Client you have to open the Clientkonfiguration tool. There go
to alias and enter one for TCP/IP with the instance name (normaly
'server\instance'). Then you have to enter the port manualy (get it
from properties/network/TCPIP/Settings on the instance).
After that your client should connect.

Why that: Normaly a service on the server listen on port 1434 for a
client. If a client ask for an instance name, the service returns the
port adresse for the connection. SP3a seems to disable the service.
This is a reason of the slammer virus.
In theory the service should only be disabled if you disable the
network for the instance. But even if i don't i couldn't connect.

Has anyone an idea for fixing? Configure every client isn't all times
a nice work.

Mike

"Sydney Lotterby" <sydney (AT) infosearch (DOT) com> wrote