Andrew J. Kelly SQL MVP
"Trex" <randytrexler@hotmail.com> wrote in message
news:KZdvf.3140$%W1.115@newsread2.news.atl.earthlink.net...
> I'm sorry this is the error message I'm receiving:
>
> TITLE: New Server Registration
> ------------------------------
> Testing the registered server failed. Verify the server name, login
> credentials, and database, and then click Test again.
>
> ------------------------------
> ADDITIONAL INFORMATION:
>
> 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 SQL Server does not allow remote connections.
> (provider: SQL Network Interfaces, error: 26 - Error Locating
> Server/Instance Specified) (Microsoft SQL Server, Error: -1)
>
> For help, click:
>
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476 >
> ------------------------------
> BUTTONS:
>
> OK
> ------------------------------
>
>
> "Trex" <randytrexler@hotmail.com> wrote in message
> news:1Xdvf.3139$%W1.71@newsread2.news.atl.earthlink.net...
>>I have an instance of SQL Server 2005 on two different development
>>machines. At first we could not connect to Machine A until we read about
>>how it comes locked down. We went to SQL Server Config Mgr and enabled
>>all necessary protocols and can connect just fine to it. When we did the
>>same to machine B, nothing happened. Our client apps just hang. The
>>server is ping-able but sql test connections just fail. Any thoughts what
>>or where I could look at next?
>>
>> Regards.
>>
>
>