We just installed SQL 2000 on a remote server. We can't connect to SQL
remotely from a desktop PC. When we try to register the SQL server in
Enterprise Mgr. we get the error:
"Client unable to establish connection. Named Pipes Provider: The network
path was not found. Timeout expired."
I checked the protocols on the SQL server and there is: TCP/IP and Named
Pipes (the default), so I disabled Named Pipes, but the error still occurs.
Anyone know what might be the problem?
Thanks!What Network Operating System (NOS) are you running?
What service packs have been applied?
Are both servers in the same domain?
Do you have to go through a firewall?
More information would be helpful.
Rick Sawtell
MCT, MCSD, MCDBA
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> Hello,
> We just installed SQL 2000 on a remote server. We can't connect to SQL
> remotely from a desktop PC. When we try to register the SQL server in
> Enterprise Mgr. we get the error:
> "Client unable to establish connection. Named Pipes Provider: The network
> path was not found. Timeout expired."
> I checked the protocols on the SQL server and there is: TCP/IP and Named
> Pipes (the default), so I disabled Named Pipes, but the error still
occurs.
> Anyone know what might be the problem?
> Thanks!
>|||Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not SP2).
There is no firewall on the SQL server (not supposed to be). The server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
> More information would be helpful.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > We just installed SQL 2000 on a remote server. We can't connect to SQL
> > remotely from a desktop PC. When we try to register the SQL server in
> > Enterprise Mgr. we get the error:
> >
> > "Client unable to establish connection. Named Pipes Provider: The
network
> > path was not found. Timeout expired."
> >
> > I checked the protocols on the SQL server and there is: TCP/IP and Named
> > Pipes (the default), so I disabled Named Pipes, but the error still
> occurs.
> > Anyone know what might be the problem?
> >
> > Thanks!
> >
> >
>|||This is a multi-part message in MIME format.
--=_NextPart_000_0063_01C4ABE6.48846340
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Does the client PC list the sqlserver when you try to register it or you =type it in?
"Dean J Garrett" <info@.amuletc.com> wrote in message =news:e1vxB2#qEHA.1644@.tk2msftngp13.phx.gbl...
Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not =SP2).
There is no firewall on the SQL server (not supposed to be). The =server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
>
> More information would be helpful.
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > We just installed SQL 2000 on a remote server. We can't connect to =SQL
> > remotely from a desktop PC. When we try to register the SQL server =in
> > Enterprise Mgr. we get the error:
> >
> > "Client unable to establish connection. Named Pipes Provider: The
network
> > path was not found. Timeout expired."
> >
> > I checked the protocols on the SQL server and there is: TCP/IP and =Named
> > Pipes (the default), so I disabled Named Pipes, but the error =still
> occurs.
> > Anyone know what might be the problem?
> >
> > Thanks!
> >
> >
>
>
--=_NextPart_000_0063_01C4ABE6.48846340
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Does the client PC list the sqlserver =when you try to register it or you type it in?
"Dean J Garrett"
--=_NextPart_000_0063_01C4ABE6.48846340--|||This is a multi-part message in MIME format.
--=_NextPart_000_007F_01C4ABDA.3DAB8E50
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sounds like a security issue to me.
Are you using SQL validation or Windows validation? If Windows =validation, then you need to ensure that your workstation is trusted by =the W2k3 server's DC.
If you are trying to connect through a named pipe, then umm. (I'm a bit =out of my element on this one), but you may need to set up some type of =Share on the W2k3 server so that the pipe is able to connect to the =server.
Hope this helps, maybe someone with some additional insight can be of =service on this one.
Rick
"TJ" <tunj@.hotmail.com> wrote in message =news:eY%23g28ArEHA.1644@.tk2msftngp13.phx.gbl...
Does the client PC list the sqlserver when you try to register it or =you type it in?
"Dean J Garrett" <info@.amuletc.com> wrote in message =news:e1vxB2#qEHA.1644@.tk2msftngp13.phx.gbl...
Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not =SP2).
There is no firewall on the SQL server (not supposed to be). The =server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
>
> More information would be helpful.
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > We just installed SQL 2000 on a remote server. We can't connect =to SQL
> > remotely from a desktop PC. When we try to register the SQL =server in
> > Enterprise Mgr. we get the error:
> >
> > "Client unable to establish connection. Named Pipes Provider: =The
network
> > path was not found. Timeout expired."
> >
> > I checked the protocols on the SQL server and there is: TCP/IP =and Named
> > Pipes (the default), so I disabled Named Pipes, but the error =still
> occurs.
> > Anyone know what might be the problem?
> >
> > Thanks!
> >
> >
>
>
--=_NextPart_000_007F_01C4ABDA.3DAB8E50
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Sounds like a security issue to me. =
Are you using SQL validation or Windows =validation? If Windows validation, then you need to ensure that your workstation is =trusted by the W2k3 server's DC.
If you are trying to connect through a named =pipe, then umm. (I'm a bit out of my element on this one), but you may need =to set up some type of Share on the W2k3 server so that the pipe is able to =connect to the server.
Hope this helps, maybe someone with =some additional insight can be of service on this one.
Rick
"TJ"
Does the client PC list the sqlserver =when you try to register it or you type it in?
"Dean J Garrett"
--=_NextPart_000_007F_01C4ABDA.3DAB8E50--|||Can you ping the server from the client?
Jeff
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:u14$po#qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> Hello,
> We just installed SQL 2000 on a remote server. We can't connect to SQL
> remotely from a desktop PC. When we try to register the SQL server in
> Enterprise Mgr. we get the error:
> "Client unable to establish connection. Named Pipes Provider: The network
> path was not found. Timeout expired."
> I checked the protocols on the SQL server and there is: TCP/IP and Named
> Pipes (the default), so I disabled Named Pipes, but the error still
occurs.
> Anyone know what might be the problem?
> Thanks!
>|||This is a multi-part message in MIME format.
--=_NextPart_000_00BC_01C4AC60.FF9D8E10
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello, when I try to register the remote SQL Server, it does not list it =in the pull-down because I'm using a workstation in an office, and the =SQL Server is a machine in an ISPs data center across the country. =Instead, I type in the IP address for the remote SQL box, and then enter =SQL authentication that works fine when I'm using the SQL Server =directly (via remote desktop). The SQL registration process fails due to =the error:
"Client unable to establish connection. Named pipes provider: The =network path was not found. Time-out expired."
Any clues?
"TJ" <tunj@.hotmail.com> wrote in message =news:eY#g28ArEHA.1644@.tk2msftngp13.phx.gbl...
Does the client PC list the sqlserver when you try to register it or =you type it in?
"Dean J Garrett" <info@.amuletc.com> wrote in message =news:e1vxB2#qEHA.1644@.tk2msftngp13.phx.gbl...
Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not =SP2).
There is no firewall on the SQL server (not supposed to be). The =server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
>
> More information would be helpful.
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > We just installed SQL 2000 on a remote server. We can't connect =to SQL
> > remotely from a desktop PC. When we try to register the SQL =server in
> > Enterprise Mgr. we get the error:
> >
> > "Client unable to establish connection. Named Pipes Provider: =The
network
> > path was not found. Timeout expired."
> >
> > I checked the protocols on the SQL server and there is: TCP/IP =and Named
> > Pipes (the default), so I disabled Named Pipes, but the error =still
> occurs.
> > Anyone know what might be the problem?
> >
> > Thanks!
> >
> >
>
>
--=_NextPart_000_00BC_01C4AC60.FF9D8E10
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Hello, when I try to register the =remote SQL Server, it does not list it in the pull-down because I'm using a =workstation in an office, and the SQL Server is a machine in an ISPs data center across =the country. Instead, I type in the IP address for the remote SQL box, and =then enter SQL authentication that works fine when I'm using the SQL Server =directly (via remote desktop). The SQL registration process fails due to the error:
"Client unable to establish connection. =Named pipes provider: The network path was not found. Time-out =expired."
Any clues?
"TJ"
Does the client PC list the sqlserver =when you try to register it or you type it in?
"Dean J Garrett"
--=_NextPart_000_00BC_01C4AC60.FF9D8E10--|||This is a multi-part message in MIME format.
--=_NextPart_000_00C8_01C4AC61.6F469B80
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello, the SQL Server 2000 installation uses Mixed authentication, SQL =and Windows. When I try to register the SQL Server remotely from my =desktop, I enter SQL username/password. This always worked in the past =with other SQL servers.
I don't know if I'm trying to use named pipes, in fact I'd rather use =only TCP/IP. As a suggestion by another newsgroup member, I disabled =Name Pipes completely on the remote SQL server, but I still get the =error message below:
"Client unable to establish connection. Named pipes provider: The =network path was not found. Timeout expired."
Any clues?
"Rick Sawtell" <r_sawtell@.hotmail.com> wrote in message =news:#3KkuSBrEHA.332@.TK2MSFTNGP14.phx.gbl...
Sounds like a security issue to me.
Are you using SQL validation or Windows validation? If Windows =validation, then you need to ensure that your workstation is trusted by =the W2k3 server's DC.
If you are trying to connect through a named pipe, then umm. (I'm a =bit out of my element on this one), but you may need to set up some type =of Share on the W2k3 server so that the pipe is able to connect to the =server.
Hope this helps, maybe someone with some additional insight can be =of service on this one.
Rick
"TJ" <tunj@.hotmail.com> wrote in message =news:eY%23g28ArEHA.1644@.tk2msftngp13.phx.gbl...
Does the client PC list the sqlserver when you try to register it or =you type it in?
"Dean J Garrett" <info@.amuletc.com> wrote in message =news:e1vxB2#qEHA.1644@.tk2msftngp13.phx.gbl...
Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not =SP2).
There is no firewall on the SQL server (not supposed to be). The =server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
>
> More information would be helpful.
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > We just installed SQL 2000 on a remote server. We can't =connect to SQL
> > remotely from a desktop PC. When we try to register the SQL =server in
> > Enterprise Mgr. we get the error:
> >
> > "Client unable to establish connection. Named Pipes Provider: =The
network
> > path was not found. Timeout expired."
> >
> > I checked the protocols on the SQL server and there is: TCP/IP =and Named
> > Pipes (the default), so I disabled Named Pipes, but the error =still
> occurs.
> > Anyone know what might be the problem?
> >
> > Thanks!
> >
> >
>
>
--=_NextPart_000_00C8_01C4AC61.6F469B80
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Hello, the SQL Server 2000 installation =uses Mixed authentication, SQL and Windows. When I try to register the SQL Server =remotely from my desktop, I enter SQL username/password. This always worked in =the past with other SQL servers.
I don't know if I'm trying to use named =pipes, in fact I'd rather use only TCP/IP. As a suggestion by another newsgroup =member, I disabled Name Pipes completely on the remote SQL server, but I still get =the error message below:
"Client unable to establish connection. =Named pipes provider: The network path was not found. Timeout expired."
Any clues?
"Rick Sawtell"
Sounds like a security issue to me. =
Are you using SQL validation or Windows validation? If Windows validation, then you need to ensure that =your workstation is trusted by the W2k3 server's DC.
If you are trying to connect through a named =pipe, then umm. (I'm a bit out of my element on this one), but you may need =to set up some type of Share on the W2k3 server so that the pipe is able to =connect to the server.
Hope this helps, maybe someone =with some additional insight can be of service on this one.
Rick
"TJ"
Does the client PC list the =sqlserver when you try to register it or you type it in?
"Dean J Garrett"
--=_NextPart_000_00C8_01C4AC61.6F469B80--|||Yes, absolutely.
"Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
news:eGqYVuIrEHA.1272@.TK2MSFTNGP09.phx.gbl...
> Can you ping the server from the client?
> Jeff
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po#qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > We just installed SQL 2000 on a remote server. We can't connect to SQL
> > remotely from a desktop PC. When we try to register the SQL server in
> > Enterprise Mgr. we get the error:
> >
> > "Client unable to establish connection. Named Pipes Provider: The
network
> > path was not found. Timeout expired."
> >
> > I checked the protocols on the SQL server and there is: TCP/IP and Named
> > Pipes (the default), so I disabled Named Pipes, but the error still
> occurs.
> > Anyone know what might be the problem?
> >
> > Thanks!
> >
> >
>|||You're still trying to use Named Pipes. Use both Client and Server Network
Utilities to ensure TCP/IP
Jeff
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:#co#$xJrEHA.452@.TK2MSFTNGP09.phx.gbl...
Hello, the SQL Server 2000 installation uses Mixed authentication, SQL and
Windows. When I try to register the SQL Server remotely from my desktop, I
enter SQL username/password. This always worked in the past with other SQL
servers.
I don't know if I'm trying to use named pipes, in fact I'd rather use only
TCP/IP. As a suggestion by another newsgroup member, I disabled Name Pipes
completely on the remote SQL server, but I still get the error message
below:
"Client unable to establish connection. Named pipes provider: The network
path was not found. Timeout expired."
Any clues?
"Rick Sawtell" <r_sawtell@.hotmail.com> wrote in message
news:#3KkuSBrEHA.332@.TK2MSFTNGP14.phx.gbl...
Sounds like a security issue to me.
Are you using SQL validation or Windows validation? If Windows
validation, then you need to ensure that your workstation is trusted by the
W2k3 server's DC.
If you are trying to connect through a named pipe, then umm. (I'm a bit
out of my element on this one), but you may need to set up some type of
Share on the W2k3 server so that the pipe is able to connect to the server.
Hope this helps, maybe someone with some additional insight can be of
service on this one.
Rick
"TJ" <tunj@.hotmail.com> wrote in message
news:eY%23g28ArEHA.1644@.tk2msftngp13.phx.gbl...
Does the client PC list the sqlserver when you try to register it or you
type it in?
"Dean J Garrett" <info@.amuletc.com> wrote in message
news:e1vxB2#qEHA.1644@.tk2msftngp13.phx.gbl...
Rick,
The SQL Server is Windows 2003 Server, the desktop is XP Pro (not
SP2).
There is no firewall on the SQL server (not supposed to be). The
server and
desktop PC are not in the same domain. Any clues?
Thanks!
"Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...
> What Network Operating System (NOS) are you running?
> What service packs have been applied?
> Are both servers in the same domain?
> Do you have to go through a firewall?
>
> More information would be helpful.
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
>
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > Hello,
> >
> > We just installed SQL 2000 on a remote server. We can't connect to
SQL
> > remotely from a desktop PC. When we try to register the SQL server
in
> > Enterprise Mgr. we get the error:
> >
> > "Client unable to establish connection. Named Pipes Provider: The
network
> > path was not found. Timeout expired."
> >
> > I checked the protocols on the SQL server and there is: TCP/IP and
Named
> > Pipes (the default), so I disabled Named Pipes, but the error
still
> occurs.
> > Anyone know what might be the problem?
> >
> > Thanks!
> >
> >
>
>|||This is the strange thing, I've checked both the Client and Server Network
utils and both show Name Pipes disabled. I've rebooted the server twice.
Maybe I'll have to remove the Name Pipes protocol from the server (not sure
of the ramifications of doing that).
"Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
news:#tXe5#KrEHA.2724@.TK2MSFTNGP14.phx.gbl...
> You're still trying to use Named Pipes. Use both Client and Server Network
> Utilities to ensure TCP/IP
> Jeff
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:#co#$xJrEHA.452@.TK2MSFTNGP09.phx.gbl...
> Hello, the SQL Server 2000 installation uses Mixed authentication, SQL and
> Windows. When I try to register the SQL Server remotely from my desktop, I
> enter SQL username/password. This always worked in the past with other SQL
> servers.
> I don't know if I'm trying to use named pipes, in fact I'd rather use only
> TCP/IP. As a suggestion by another newsgroup member, I disabled Name Pipes
> completely on the remote SQL server, but I still get the error message
> below:
> "Client unable to establish connection. Named pipes provider: The network
> path was not found. Timeout expired."
> Any clues?
> "Rick Sawtell" <r_sawtell@.hotmail.com> wrote in message
> news:#3KkuSBrEHA.332@.TK2MSFTNGP14.phx.gbl...
> Sounds like a security issue to me.
> Are you using SQL validation or Windows validation? If Windows
> validation, then you need to ensure that your workstation is trusted by
the
> W2k3 server's DC.
> If you are trying to connect through a named pipe, then umm. (I'm a bit
> out of my element on this one), but you may need to set up some type of
> Share on the W2k3 server so that the pipe is able to connect to the
server.
> Hope this helps, maybe someone with some additional insight can be of
> service on this one.
> Rick
> "TJ" <tunj@.hotmail.com> wrote in message
> news:eY%23g28ArEHA.1644@.tk2msftngp13.phx.gbl...
> Does the client PC list the sqlserver when you try to register it or
you
> type it in?
> "Dean J Garrett" <info@.amuletc.com> wrote in message
> news:e1vxB2#qEHA.1644@.tk2msftngp13.phx.gbl...
> Rick,
> The SQL Server is Windows 2003 Server, the desktop is XP Pro (not
> SP2).
> There is no firewall on the SQL server (not supposed to be). The
> server and
> desktop PC are not in the same domain. Any clues?
> Thanks!
>
> "Rick Sawtell" <ricksawtell@.hotmail.com> wrote in message
> news:ushY2w#qEHA.2340@.TK2MSFTNGP11.phx.gbl...
> > What Network Operating System (NOS) are you running?
> > What service packs have been applied?
> > Are both servers in the same domain?
> > Do you have to go through a firewall?
> >
> > More information would be helpful.
> >
> > Rick Sawtell
> > MCT, MCSD, MCDBA
> >
> >
> >
> > "Dean J Garrett" <info@.amuletc.com> wrote in message
> > news:u14$po%23qEHA.2588@.TK2MSFTNGP12.phx.gbl...
> > > Hello,
> > >
> > > We just installed SQL 2000 on a remote server. We can't connect
to
> SQL
> > > remotely from a desktop PC. When we try to register the SQL
server
> in
> > > Enterprise Mgr. we get the error:
> > >
> > > "Client unable to establish connection. Named Pipes Provider:
The
> network
> > > path was not found. Timeout expired."
> > >
> > > I checked the protocols on the SQL server and there is: TCP/IP
and
> Named
> > > Pipes (the default), so I disabled Named Pipes, but the error
> still
> > occurs.
> > > Anyone know what might be the problem?
> > >
> > > Thanks!
> > >
> > >
> >
> >
>
>
No comments:
Post a Comment