Re: Sudden failure to connect to remote SQL Server from Enterprise
From: Steve Thompson (stevethompson_at_nomail.please)
Date: 02/22/05
- Next message: Steve Thompson: "Re: MBSA 1.2 and slammer"
- Previous message: Kevin McDonnell [MSFT]: "RE: Kerberos Delegation win2k3 AD/IIS/SQLSERVER seperate machines"
- In reply to: Steve B.: "Re: Sudden failure to connect to remote SQL Server from Enterprise"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 22 Feb 2005 13:58:31 -0500
"Steve B." <SteveB@discussions.microsoft.com> wrote in message
news:D6228697-3E6A-4AD1-9C34-E58E8E814EA3@microsoft.com...
> Thanks for responding. I have done these things, to no avail. The order of
> the protocols is TCP/IP first, named pipes second. Is the order
significant?
No the order is not significant, do double check the server (SQL Server
server network utility settings) are enabled. I assume they are since your
other client can connect. You're getting such a generic failure it's hard to
say where it occurs. Do check this troubleshooting guide:
http://support.microsoft.com/default.aspx?scid=827422
Steve
- Next message: Steve Thompson: "Re: MBSA 1.2 and slammer"
- Previous message: Kevin McDonnell [MSFT]: "RE: Kerberos Delegation win2k3 AD/IIS/SQLSERVER seperate machines"
- In reply to: Steve B.: "Re: Sudden failure to connect to remote SQL Server from Enterprise"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
