Re: connection issue from our developer

When you get symptoms like this where it only affects the
user on a particular PC then you need to look at that PC.
You'd probably start by testing basic connectivity to the
server from the PC: Can the user ping the server by name,
can the user ping the server by IP, what network related
issues are found in the Event logs on the PC, can the user
connect to the server using sqlcmd, etc. Also, have you
tried logging in from that users PC?
If you find that the issue is comes up only with Management
Studio, have the user increase the connect timeout in SSMS:
When logging on, click on the options button in the Connect
to Server window and increase the connection timeout to
something greater than the 15 second default.
It would also be worth checking the users MDAC installation
using the component checker. You can download this from:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
You may also want to look at applying the latest SQL Server
service pack to the client on that PC having problems.

-Sue

On Thu, 29 Mar 2007 15:38:05 -0700, Lynn
<Lynn@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Sue,

The developer's client protocol order is TCP and NP. We didn't enable Named
Pipe in server at the beginning, that's why the first message is NP message
due to client will try to connect in the protocol order in the client. As I
menetioned, after I turn on Named Pipes in server, user's machine is able to
connect to server. But, the issue our developers had is that they couldn't
connect with TCP protocol from their machine. (I can connect by TCP protocol
from my machine. The developer login to my machine and his win account can
connect to the server as well). His machine is able to connect to our SQL
2000 with TCP protocol, but just can't connect to 2005 with TCP protocol. I
was thinging is firewall in server to caused this issue, but firewall didn't
enable in the server at all. So, I don't know what cause the issue.

Please advise.

.