Cannot Connect to Server -- sql server connect

Narayana Vyas Kondreddi
9/18/2003 7:49:00 AM

Are you able to ping that server by name, from the machine you are trying to
connect from?

Are you able to make connections locally?

--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
What hardware is your SQL Server running on?
http://vyaskn.tripod.com/poll.htm

[quoted text, click to view]
I have just created a new SQL server instance on Windows
2003 server. I can open databases using interprise
manager on the local machine but when I try to connect
using the enterprise manager from another machine I get
the error message: "A connection could not be
established to [server]; Reason: server does not exist or
access denied." I attempting to connect as sa. I know
that the server exist. I can even see the server when I
browse servers in the server registration wizard. I have
tested to make sure the password works on the server. I
have configured my computer to see the port using the
client network utility. What more must I do to connect?

Tim
9/18/2003 8:01:45 AM

Are you having difficulty connecting to the default
instance or a named instance? If a named instance, how
many do you have?

Tim

[quoted text, click to view]

Derek V. Taylor
9/18/2003 11:32:43 AM

Thanks Tim,

I am having trouble connecting to the default instance,
which is the only one installed on machine.

[quoted text, click to view]

Tim
9/18/2003 11:52:51 AM

I just got to the bottom of some connection issues we
were having, but they involved multiple named instances.

Check and see if you can connect by using the Client
Network utility to create an alias to the server. Try
both TCP/IP and named pipes (you can only do one at a
time if you are using the server name as your alias name).

That you can connect with a alias, but not without one
may be a useful clue.

Tim

[quoted text, click to view]

Sharon
9/18/2003 1:55:54 PM

I am having the same problem. Did you resolve yours yet?

The new Win 2003 machine has SQL Server 2000 Enterprise.
My client is actually from a SQL Server STandard media.
I don't know if that matters.

I checked client and network utilities on both ends, they
are only using TCP/IP, and I have dynamic ports on the
aliases. I tried even designating the port.

I still get the "cannot access" message.

But it works fine when all work is done locally to the
machine.

Let me know if you find something out and I'll keep

Sharon
9/19/2003 3:02:03 PM

FYI, hope this helps you....

We actually solved my connection problem today (sounded
same as yours).

We noticed that the new installation on the Win 2003
machine was version (RTM) (Release to Manufacturing).
They had tried installing SP3, but it must not
have "taken".

It was missing the Service Packs, especially SP2 which
includes resolving some connectivity issues.

So we installed SP3, the latest, and now I have no

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about sql server connect

sql server connect : Cannot Connect to Server