| Groups | Blog | Home |
sql server clients : connection issue from our developer
SQL 2005 EE is installed on W2k3 box and firewall is off in this server. From my client machine, my window account and that developer window account all can login into this server with ODBC, sql client, telent to 1433 or VS connection. But, this developer can't login to SQL server from him machine with any appliction. He is in the same domain as server and my machine. I don't know what's the reason to cause this issue now. Please advise. Thank you. Lynn -- Best Regards,
What is the exact error message and error number he gets
when he tries to log into SQL Server? -Sue On Thu, 22 Mar 2007 10:33:45 -0700, Lynn [quoted text, click to view] <Lynn@discussions.microsoft.com> wrote:
>Hi, > >SQL 2005 EE is installed on W2k3 box and firewall is off in this server. >From my client machine, my window account and that developer window account >all can login into this server with ODBC, sql client, telent to 1433 or VS >connection. But, this developer can't login to SQL server from him machine >with any appliction. He is in the same domain as server and my machine. I >don't know what's the reason to cause this issue now. > >Please advise. Thank you. > >Lynn
We only enable Shared Memory and TCP/IP protocal in server side. And, those
are the error they are getting. osql -- SQL server doesn't exist or access denied Query Analyzer -- General network error. Check your network documentation VS 2005 -- (without specifing TCP protocal in connection) A connection was succssfully established with the server, but then an error occured during the pre-login handshake. When connecting .....(provider: Named Pipes provider, error: 0 - No process is on the ther end of the pipe) VS 2005 -- (specify TCP protocal in connection) An error has occurred while establishing a connection to the server. When connecting to SQL server 2005, this failure may be caused by the fact that under the default settings ... (provider: TCP provider: 0 -- A connection attempt failed because the connected party didn't not properly respond after a period of tiem, or established connection failed because connected host has failed to respond.) Again, this developer is able to login by using my machine with his WIN account. After I enable Named Pipes in server. This developer is able to connect to server on his machine by using Named Pipe. Firewall is off in the server, so I can't think of the issue for TCP connection on developer's machine. Please advise. Thank you. -- Best Regards, Lynn [quoted text, click to view] "Sue Hoegemeier" wrote:
> What is the exact error message and error number he gets > when he tries to log into SQL Server? > > -Sue > > On Thu, 22 Mar 2007 10:33:45 -0700, Lynn > <Lynn@discussions.microsoft.com> wrote: > > >Hi, > > > >SQL 2005 EE is installed on W2k3 box and firewall is off in this server. > >From my client machine, my window account and that developer window account > >all can login into this server with ODBC, sql client, telent to 1433 or VS > >connection. But, this developer can't login to SQL server from him machine > >with any appliction. He is in the same domain as server and my machine. I > >don't know what's the reason to cause this issue now. > > > >Please advise. Thank you. > > > >Lynn >
Check the following article in Books Online:
http://msdn2.microsoft.com/en-us/library/ms175496.aspx -Sue On Fri, 23 Mar 2007 09:15:08 -0700, Lynn [quoted text, click to view] <Lynn@discussions.microsoft.com> wrote:
>We only enable Shared Memory and TCP/IP protocal in server side. And, those >are the error they are getting. > >osql -- SQL server doesn't exist or access denied >Query Analyzer -- General network error. Check your network documentation >VS 2005 -- (without specifing TCP protocal in connection) A connection was >succssfully established with the server, but then an error occured during the >pre-login handshake. When connecting .....(provider: Named Pipes provider, >error: 0 - No process is on the ther end of the pipe) >VS 2005 -- (specify TCP protocal in connection) An error has occurred while >establishing a connection to the server. When connecting to SQL server 2005, >this failure may be caused by the fact that under the default settings ... >(provider: TCP provider: 0 -- A connection attempt failed because the >connected party didn't not properly respond after a period of tiem, or >established connection failed because connected host has failed to respond.) > >Again, this developer is able to login by using my machine with his WIN >account. > >After I enable Named Pipes in server. This developer is able to connect to >server on his machine by using Named Pipe. > >Firewall is off in the server, so I can't think of the issue for TCP >connection on developer's machine. > >Please advise. Thank you.
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. -- Best Regards, Lynn [quoted text, click to view] "Sue Hoegemeier" wrote:
> Check the following article in Books Online: > http://msdn2.microsoft.com/en-us/library/ms175496.aspx > > -Sue > > On Fri, 23 Mar 2007 09:15:08 -0700, Lynn > <Lynn@discussions.microsoft.com> wrote: > > >We only enable Shared Memory and TCP/IP protocal in server side. And, those > >are the error they are getting. > > > >osql -- SQL server doesn't exist or access denied > >Query Analyzer -- General network error. Check your network documentation > >VS 2005 -- (without specifing TCP protocal in connection) A connection was > >succssfully established with the server, but then an error occured during the > >pre-login handshake. When connecting .....(provider: Named Pipes provider, > >error: 0 - No process is on the ther end of the pipe) > >VS 2005 -- (specify TCP protocal in connection) An error has occurred while > >establishing a connection to the server. When connecting to SQL server 2005, > >this failure may be caused by the fact that under the default settings ... > >(provider: TCP provider: 0 -- A connection attempt failed because the > >connected party didn't not properly respond after a period of tiem, or > >established connection failed because connected host has failed to respond.) > > > >Again, this developer is able to login by using my machine with his WIN > >account. > > > >After I enable Named Pipes in server. This developer is able to connect to > >server on his machine by using Named Pipe. > > > >Firewall is off in the server, so I can't think of the issue for TCP > >connection on developer's machine. > > > >Please advise. Thank you. >
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 [quoted text, click to view] <Lynn@discussions.microsoft.com> 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.
Sue,
Thank you again. Definitely, we already checked the network connect from those developers machine. The connection issue happens to all related developers. The developers were able to ping the server by name and IP from their machine. But, the issue only happened on connecting to SQL 2005 with TCP protocol. We tested through ODBC (with TCP/IP), osql, telnet to 1433 port, VS, but all connection were failed. One developer already reinstall SQL 2005 client, but the problem is still resisted. Will ask them to update to sp2 and go from there. -- Best Regards, Lynn [quoted text, click to view] "Sue Hoegemeier" wrote:
> 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
Don't see what you're looking for? Try a search.
|
March 2003
May 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |