Can't register remote SQL

When I try to register a remote SQL Server from a local desktop XP Pro PC, I
get the error:
"Client unable to establish connection. Named Pipes Provider: the network
path was not found. Timeout expired."
I checked and this is not a firewall problem because SQL ports are open. We
normally don't have a problem registering SQL servers like this; just this
one server. Any clues?
Thanks!!!Is that particular server using Named Pipes, or is it set for TCP/IP? Check
the Server Network Utility to ensure Named Pipes is turned on on the server,
since your client appears to be using Named Pipes instead of TCP/IP.
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:e4otsANKFHA.904@.tk2msftngp13.phx.gbl...
> When I try to register a remote SQL Server from a local desktop XP Pro PC,
> I
> get the error:
> "Client unable to establish connection. Named Pipes Provider: the network
> path was not found. Timeout expired."
> I checked and this is not a firewall problem because SQL ports are open.
> We
> normally don't have a problem registering SQL servers like this; just this
> one server. Any clues?
> Thanks!!!
>|||Hello,
Yes, I thought of that before, but I just checked again and the Server
Network Util says enabled protocols:
Named Pipes
TCP/IP
We are trying to register the SQL server remotely using the server's IP addr
which has always worked in the past. Anyone know what is wrong?
Thanks!!!
"Michael C#" <xyz@.yomomma.com> wrote in message
news:#HM9QONKFHA.3064@.TK2MSFTNGP12.phx.gbl...
> Is that particular server using Named Pipes, or is it set for TCP/IP?
Check
> the Server Network Utility to ensure Named Pipes is turned on on the
server,
> since your client appears to be using Named Pipes instead of TCP/IP.
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:e4otsANKFHA.904@.tk2msftngp13.phx.gbl...
> > When I try to register a remote SQL Server from a local desktop XP Pro
PC,
> > I
> > get the error:
> >
> > "Client unable to establish connection. Named Pipes Provider: the
network
> > path was not found. Timeout expired."
> >
> > I checked and this is not a firewall problem because SQL ports are open.
> > We
> > normally don't have a problem registering SQL servers like this; just
this
> > one server. Any clues?
> >
> > Thanks!!!
> >
> >
>|||Interesting. You're using the TCP/IP address, but it's trying to connect
via Named Pipes? Have you checked the Client Network Utility on your client
box to see if TCP/IP is enabled locally? Also have you established
connectivity to the remote server? i.e., can you Ping the remote box? It
sounds like you're trying to connect via TCP/IP, but it's falling back to
Named Pipes. I'd check the network settings on the server and make sure
it's reachable from the local box. There's a utility called SQLPing at
http://sqlsecurity.com/DesktopDefault.aspx (w/ source code) that can help
determine if you can see the other server from the local box.
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:OYoG%236NKFHA.2812@.TK2MSFTNGP15.phx.gbl...
> Hello,
> Yes, I thought of that before, but I just checked again and the Server
> Network Util says enabled protocols:
> Named Pipes
> TCP/IP
> We are trying to register the SQL server remotely using the server's IP
> addr
> which has always worked in the past. Anyone know what is wrong?
> Thanks!!!
>
> "Michael C#" <xyz@.yomomma.com> wrote in message
> news:#HM9QONKFHA.3064@.TK2MSFTNGP12.phx.gbl...
>> Is that particular server using Named Pipes, or is it set for TCP/IP?
> Check
>> the Server Network Utility to ensure Named Pipes is turned on on the
> server,
>> since your client appears to be using Named Pipes instead of TCP/IP.
>> "Dean J Garrett" <info@.amuletc.com> wrote in message
>> news:e4otsANKFHA.904@.tk2msftngp13.phx.gbl...
>> > When I try to register a remote SQL Server from a local desktop XP Pro
> PC,
>> > I
>> > get the error:
>> >
>> > "Client unable to establish connection. Named Pipes Provider: the
> network
>> > path was not found. Timeout expired."
>> >
>> > I checked and this is not a firewall problem because SQL ports are
>> > open.
>> > We
>> > normally don't have a problem registering SQL servers like this; just
> this
>> > one server. Any clues?
>> >
>> > Thanks!!!
>> >
>> >
>>
>