Cant get Access Database Synchronizer set up on client machine

I have created a PPC application that uses ADS to synchronize my sqlce db with a desktop MS Access database. It works fine on my computers, but my client cant get it to work on his. Here is the situation.

His "Computer Name" as it's stated in his 'My Computer' properties is "PAVSGP024FE.NWFSC.NOAA.GOV"

However his Access.MDW File is located in the directory "C:\Documents and Settings\Joe Nobody\Application Data\Microsoft\Access\System.MDW".

There is no directory called "C:\Documents and Settings\PAVSGP024FE.NWFSC.NOAA.GOV\Application Data\Microsoft\Access\System.MDW".

His current config.xml file looks like this.

<?xml version="1.0" encoding="UTF-8"?>
<SystemNode>
<AccessDB>C:\Program Files\NOAA Release Logger\NOAA_ReleaseLogger.mdb</AccessDB>
<DeviceDB>\Program Files\NOAA Release Logger\NOAA_ReleaseLogger.sdf</DeviceDB>
<Login>Joe Nobody</Login>
<URL>http://Joe Nobody:1024/</URL>
<WinDir>C:\</WinDir>
</SystemNode>

He has tried adding port 1024 as an exception for his firewall settings, has installed Access Database Synchronizer on his computer, and I have also tried using the "long" computer name as the url setting in the config file. (i.e. <URL>http://PAVSGP024FE.NWFSC.NOAA.GOV:1024/</URL> but this throws the error

"The HTTP request failed due to incorrect format or content. Try restarting the IIS server.[]"

I dont know what else to try! Anybody have any suggestions?

I have had the same problems when I first installed. THen for some reason things started working. Now a few weeks later, when I get back to trying it, no work anymore. I suggest you read the readme.doc that comes with it. THere are some things to check there. Make sure IIS is running. THen you add a 1024 port if you have the firewall enabled. I also had some success when I manually copied the .cab file to the device, then installed that way. I don't think I have ever got it to work just downloading the sample project.

Another thing to verify is that your internet connection is going from device to desktop. Open IE and try to open http://<computer>:1024/. Presently, I am unable to do this so I think something is wrong on my Desktop platform. I am going to try another platform that used to work.

|||

Tried to run the synchronizer on the other platform that it used to work on also. Now that one is not working either. I went through all the steps I know of to get it working, no luck. I cannot get the IE to link up to the web service either which I am thinking must be the main problem.

I am sorry to say, I need to give up trying to get it to work now.

|||

Wanted to check, have you got it running now.

Please note: You do not IIS to run ADS applications. Stop the IIS and try.

The path of the .msw file should be C:\Documents and Settings\"User Name"\Application Data\Microsoft\Access\System.MDW.

So if his user name on the computer is "Joe Nobody" then specify the path as "C:\Documents and Settings\"User Name"\Application Data\Microsoft\Access\System.MDW" as indicated in your post.

|||

We did finally get this working but, only because we gave up installing it on this particular computer. His computer was part of a business network and something about it would not allow this to work. Once he installed everything on a non-network computer everything worked as it should. So, unfortunately, we never did actually get to the root of this particular problem.

Mike

Cant get Access Database Synchronizer set up on client machine

I have created a PPC application that uses ADS to synchronize my sqlce db with a desktop MS Access database. It works fine on my computers, but my client cant get it to work on his. Here is the situation.

His "Computer Name" as it's stated in his 'My Computer' properties is "PAVSGP024FE.NWFSC.NOAA.GOV"

However his Access.MDW File is located in the directory "C:\Documents and Settings\Joe Nobody\Application Data\Microsoft\Access\System.MDW".

There is no directory called "C:\Documents and Settings\PAVSGP024FE.NWFSC.NOAA.GOV\Application Data\Microsoft\Access\System.MDW".

His current config.xml file looks like this.

<?xml version="1.0" encoding="UTF-8"?>
<SystemNode>
<AccessDB>C:\Program Files\NOAA Release Logger\NOAA_ReleaseLogger.mdb</AccessDB>
<DeviceDB>\Program Files\NOAA Release Logger\NOAA_ReleaseLogger.sdf</DeviceDB>
<Login>Joe Nobody</Login>
<URL>http://Joe Nobody:1024/</URL>
<WinDir>C:\</WinDir>
</SystemNode>

He has tried adding port 1024 as an exception for his firewall settings, has installed Access Database Synchronizer on his computer, and I have also tried using the "long" computer name as the url setting in the config file. (i.e. <URL>http://PAVSGP024FE.NWFSC.NOAA.GOV:1024/</URL> but this throws the error

"The HTTP request failed due to incorrect format or content. Try restarting the IIS server.[]"

I dont know what else to try! Anybody have any suggestions?

I have had the same problems when I first installed. THen for some reason things started working. Now a few weeks later, when I get back to trying it, no work anymore. I suggest you read the readme.doc that comes with it. THere are some things to check there. Make sure IIS is running. THen you add a 1024 port if you have the firewall enabled. I also had some success when I manually copied the .cab file to the device, then installed that way. I don't think I have ever got it to work just downloading the sample project.

Another thing to verify is that your internet connection is going from device to desktop. Open IE and try to open http://<computer>:1024/. Presently, I am unable to do this so I think something is wrong on my Desktop platform. I am going to try another platform that used to work.

|||

Tried to run the synchronizer on the other platform that it used to work on also. Now that one is not working either. I went through all the steps I know of to get it working, no luck. I cannot get the IE to link up to the web service either which I am thinking must be the main problem.

I am sorry to say, I need to give up trying to get it to work now.

|||

Wanted to check, have you got it running now.

Please note: You do not IIS to run ADS applications. Stop the IIS and try.

The path of the .msw file should be C:\Documents and Settings\"User Name"\Application Data\Microsoft\Access\System.MDW.

So if his user name on the computer is "Joe Nobody" then specify the path as "C:\Documents and Settings\"User Name"\Application Data\Microsoft\Access\System.MDW" as indicated in your post.

|||

We did finally get this working but, only because we gave up installing it on this particular computer. His computer was part of a business network and something about it would not allow this to work. Once he installed everything on a non-network computer everything worked as it should. So, unfortunately, we never did actually get to the root of this particular problem.

Mike

Can't drop SQL Mobile subscription at Publisher

I have a program running on Pocket PCs that synchronizes with a desktop SQL database using SQL Mobile. My problem is that I can't delete old subscriptions from the publication; now the publication has 25 subscriptions and won't accept any more (limit of SQL Workgroup edition). I can delete non-SQL Mobile subcriptions just fine.

Running sp_replmonitorhelpsubscription provides this information:

subscriber: LVCONTACTSMERGE - 5FA305234F0C
subscriber_db: Program Files\PocketLVContacts\LVContacts.sdf
publisher_db: LVContacts
publication: LVContactsMerge

So I set up this bit of code:

USE LVContacts
EXEC sp_dropmergesubscription
@.publication = 'LVContactsMerge',
@.subscriber = 'LVCONTACTSMERGE - 5FA305234F0C',
@.subscriber_db = 'Program Files\PocketLVContacts\LVContacts.sdf',
@.subscription_type='all';
GO

No errors are reported, but the subscription doesn't get deleted.

I've tried shutting down SQL Server Agent (mentioned in another thread); makes no difference.

Any ideas?

--Evan

If you query sysmergesubscriptions, do you get the same values returned as|||

If you query sysmergesubscriptions, do you get the same values returned as sp_replmonitorhelpsubscription? I'm just wondering if the subscriber_db name returned is correct or not.

|||

Yes, both sysmergesubscriptions and sp_replmonitorhelpsubscription give the same subscriber_db name. Note that the name returned, i.e. 'Program Files\PocketLVContacts\LVContactsData.sdf', is the path on the mobile device.

I wonder if it is safe to manually delete a row from sysmergesubscriptions. It seems to work, but no Distributor clean-up is done.

|||

I've found where I was going wrong. The code I cited in my original post DOES work, but to see the changes you must use sysmergesubscriptions, NOT sp_replmonitorhelpsubscription. The latter apparently reflects the distribution database, which is not cleaned up when you use sp_dropmergesubscription.

When you use SQL Server Management Studio to delete a subscription on a mobile device running SQL Mobile, the subscription on the Publisher is NOT also deleted; you must do it manually (or wait until the subscription expires). But it is difficult to determine which subscription on the Publisher corresponds to the one you want to delete on the mobile Subscriber. What I did was first query the mobile Subscriber system table __sysMergeSubscriptions, note the SubscriptionID field, then query the sysmergesubscriptions on the Publisher database, and find the row with a SubID that matches. Then you can run sp_dropmergesubscription using the subscriber_server field as @.subscriber and the db_name field as @.subscriber_db.

Can't connect using management studio while using remote desktop connection on lan.

I get the error message:

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.

I am not able to find this setting. Could someone please inform me of where to look and maybe what to do?

Thanks in advance.

Start/Programs/Microsoft SQL Server 2005/Configuration Tools/SQL Server Surface Area Configuration Manager/
Click Surface Area Configuration for Services and Connections
Click Database Engines / Remote connections
Select Local and Remote connections and one of the 3 choices below

also make sure the Allow Remote Connection to This Server option is checked on the
Server Properties/Connections page

|||

lkh wrote:

Start/Programs/Microsoft SQL Server 2005/Configuration Tools/SQL Server Surface Area Configuration Manager/
Click Surface Area Configuration for Services and Connections
Click Database Engines / Remote connections
Select Local and Remote connections and one of the 3 choices below

also make sure the Allow Remote Connection to This Server option is checked on the
Server Properties/Connections page

I have found the settings within the configuration tools up to the part where you mention the 3 choices below with success.

The part:
also make sure the Allow Remote Connection to This Server option is checked on the
Server Properties/Connections page

Is that from within the same configuration area or elsewhere?
Thanks so much.|||In Object Explorer in SQL Server Management Studio (SSMS) right click the server, click properties.|||

lkh wrote:

In Object Explorer in SQL Server Management Studio (SSMS) right click the server, click properties.

I'm sorry, there is nothing listed under object explorer pane. I see a default server under database engine in the registered servers pane.

Maybe because I haven't been able to connect yet? I'm not sure where else to look. I'm prolly goofed atm.

Maybe I'll have to do this the normal way and actually connect locally on that computer, then set that setting you mention.

I was hoping I could avoid having to do that, but I will if I have to.|||

right-click the default server, then click Connect/Object Explorer

SQL Server service also has to be started

|||Thanks so much for the help, the second part is already set to allow remote connections.
Turns out the problem I was having was due to my logging in as the second admin account on that pc. I could swear I installed it from that user account but it's acting like I can only connect to SQL via the original account on the pc.
Can't put my finger on it as it's been too long since the install.

Thanks for the help, all's good for now.|||Are you connecting with server\instance?

Can't Connect to SQL 2005 Using Remote Desktop and Local Administr

I installed SQL 2005 Standard on Windows 2003 R2, and when I connect to the
server (no firewall involved) using Remote Desktop, I can't login to
Management Studio using the local administrator account. However, I can log
in using the domain administrator account. The local administrator account i
s
not locked out. I get the following error when trying to access Management
Studio using the local admin. account:
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: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (.Net SqlClient Data Provider)
Any ideas?***UPDATE***
Actually, it has nothing to do with remote connectivity. I tried to log in
to Management Studio locally as the local administrator, and it still
wouldn't let me and gave the same error. As mentioned previously, the domain
admin. works.
Thanks.
"Marks70" wrote:

> I installed SQL 2005 Standard on Windows 2003 R2, and when I connect to th
e
> server (no firewall involved) using Remote Desktop, I can't login to
> Management Studio using the local administrator account. However, I can lo
g
> in using the domain administrator account. The local administrator account
is
> not locked out. I get the following error when trying to access Management
> Studio using the local admin. account:
> 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: Named Pipes Provider, error: 40 - Could not open a connection t
o
> SQL Server) (.Net SqlClient Data Provider)
> Any ideas?

Can't connect to SQL

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!
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...[vbcol=seagreen]
> 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...
network
> occurs.
>
|||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...[vbcol=seagreen]
> 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...
network
> occurs.
>
|||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...[vbcol=seagreen]
> 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...
network
> occurs.
>
|||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!
>
|||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...[vbcol=seagreen]
> 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...
network
> occurs.
>
|||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...[vbcol=seagreen]
> 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...
network
> occurs.
>
|||Yes, absolutely.
"Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message
news:eGqYVuIrEHA.1272@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> 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...
network
> occurs.
>
|||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...[vbcol=seagreen]
> 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...
SQL[vbcol=seagreen]
in[vbcol=seagreen]
network[vbcol=seagreen]
Named[vbcol=seagreen]
still
> occurs.
>

Can't connect to SQL

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!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" 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 anddesktop PC are not in the same domain. Any clues?Thanks!"Rick Sawtell" =wrote in messagenews: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" 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: Thenetwork> > 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--|||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" 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" 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 anddesktop PC are not in the same domain. Any clues?Thanks!"Rick Sawtell" =wrote in messagenews: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" 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: Thenetwork> > 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--|||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" 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" 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 anddesktop PC are not in the same domain. Any clues?Thanks!"Rick Sawtell" =wrote in messagenews: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" 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: Thenetwork> > 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--|||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" =wrote in message news:#3KkuSBrEHA.332@.T=K2MSFTNGP14.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" 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" 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 anddesktop PC are not in the same domain. Any clues?Thanks!"Rick Sawtell" wrote in messagenews: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" = 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: =Thenetwork> > 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--|||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!
> > >
> > >
> >
> >
>
>