named pipes vs tcp

Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
enable in network libraries. I noticed in EM under current activity and
process info for some processes named pipes is used and for other processes
something called LPC is used. Is LPC aka TCP/IP? It looks like when the
"host" for the process is the server, then it uses LPC but when the "host" i
s
a workstation it uses named pipes. Does it use named pipes for the
workstations because it is listed first in the network libraries? Is named
pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
second or just remove named pipes?
Thanks,
--
Dan D.Hi Dan
"Dan D." wrote:

> Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
> enable in network libraries. I noticed in EM under current activity and
> process info for some processes named pipes is used and for other processe
s
> something called LPC is used. Is LPC aka TCP/IP? It looks like when the
> "host" for the process is the server, then it uses LPC but when the "host"
is
> a workstation it uses named pipes. Does it use named pipes for the
> workstations because it is listed first in the network libraries? Is named
> pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
> second or just remove named pipes?
> Thanks,
> --
> Dan D.
LPC is a shared memory connection, that is why the host is the server
itself. The protocol used will be order by they are listed on the client, if
you client had TCP as the first protocol to use and the server has TCP/IP
enabled then that would be used. TCP/IP was made the primary protocol in SP3
a
so you may want to check what versions you are using. To see the client
protocols installed use the Client Networking Utility (on the client) there
are buttons that will let you change the order, and to check the for server
protocols use the Server Networking Utility on the server.
As far as speed, I believe they can be about the same, but with names pipes
there are potential security issues as you are connecting directly through
the filesystem of the server.
As far as removing named pipes, it is your choice.
John|||I understand. Thanks.
--
Dan D.
"John Bell" wrote:

> Hi Dan
> "Dan D." wrote:
>
> LPC is a shared memory connection, that is why the host is the server
> itself. The protocol used will be order by they are listed on the client,
if
> you client had TCP as the first protocol to use and the server has TCP/IP
> enabled then that would be used. TCP/IP was made the primary protocol in S
P3a
> so you may want to check what versions you are using. To see the client
> protocols installed use the Client Networking Utility (on the client) ther
e
> are buttons that will let you change the order, and to check the for serve
r
> protocols use the Server Networking Utility on the server.
> As far as speed, I believe they can be about the same, but with names pipe
s
> there are potential security issues as you are connecting directly through
> the filesystem of the server.
> As far as removing named pipes, it is your choice.
> John|||"Dan D." wrote:

> I understand. Thanks.
> --
> Dan D.
That is one of us then! I didn't realise it read so badly!
John

named pipes vs tcp

Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
enable in network libraries. I noticed in EM under current activity and
process info for some processes named pipes is used and for other processes
something called LPC is used. Is LPC aka TCP/IP? It looks like when the
"host" for the process is the server, then it uses LPC but when the "host" is
a workstation it uses named pipes. Does it use named pipes for the
workstations because it is listed first in the network libraries? Is named
pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
second or just remove named pipes?
Thanks,
Dan D.
Hi Dan
"Dan D." wrote:

> Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
> enable in network libraries. I noticed in EM under current activity and
> process info for some processes named pipes is used and for other processes
> something called LPC is used. Is LPC aka TCP/IP? It looks like when the
> "host" for the process is the server, then it uses LPC but when the "host" is
> a workstation it uses named pipes. Does it use named pipes for the
> workstations because it is listed first in the network libraries? Is named
> pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
> second or just remove named pipes?
> Thanks,
> --
> Dan D.
LPC is a shared memory connection, that is why the host is the server
itself. The protocol used will be order by they are listed on the client, if
you client had TCP as the first protocol to use and the server has TCP/IP
enabled then that would be used. TCP/IP was made the primary protocol in SP3a
so you may want to check what versions you are using. To see the client
protocols installed use the Client Networking Utility (on the client) there
are buttons that will let you change the order, and to check the for server
protocols use the Server Networking Utility on the server.
As far as speed, I believe they can be about the same, but with names pipes
there are potential security issues as you are connecting directly through
the filesystem of the server.
As far as removing named pipes, it is your choice.
John
|||I understand. Thanks.
Dan D.
"John Bell" wrote:

> Hi Dan
> "Dan D." wrote:
>
> LPC is a shared memory connection, that is why the host is the server
> itself. The protocol used will be order by they are listed on the client, if
> you client had TCP as the first protocol to use and the server has TCP/IP
> enabled then that would be used. TCP/IP was made the primary protocol in SP3a
> so you may want to check what versions you are using. To see the client
> protocols installed use the Client Networking Utility (on the client) there
> are buttons that will let you change the order, and to check the for server
> protocols use the Server Networking Utility on the server.
> As far as speed, I believe they can be about the same, but with names pipes
> there are potential security issues as you are connecting directly through
> the filesystem of the server.
> As far as removing named pipes, it is your choice.
> John
|||"Dan D." wrote:

> I understand. Thanks.
> --
> Dan D.
That is one of us then! I didn't realise it read so badly!
John

named pipes vs tcp

Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
enable in network libraries. I noticed in EM under current activity and
process info for some processes named pipes is used and for other processes
something called LPC is used. Is LPC aka TCP/IP? It looks like when the
"host" for the process is the server, then it uses LPC but when the "host" is
a workstation it uses named pipes. Does it use named pipes for the
workstations because it is listed first in the network libraries? Is named
pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
second or just remove named pipes?
Thanks,
--
Dan D.Hi Dan
"Dan D." wrote:
> Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
> enable in network libraries. I noticed in EM under current activity and
> process info for some processes named pipes is used and for other processes
> something called LPC is used. Is LPC aka TCP/IP? It looks like when the
> "host" for the process is the server, then it uses LPC but when the "host" is
> a workstation it uses named pipes. Does it use named pipes for the
> workstations because it is listed first in the network libraries? Is named
> pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
> second or just remove named pipes?
> Thanks,
> --
> Dan D.
LPC is a shared memory connection, that is why the host is the server
itself. The protocol used will be order by they are listed on the client, if
you client had TCP as the first protocol to use and the server has TCP/IP
enabled then that would be used. TCP/IP was made the primary protocol in SP3a
so you may want to check what versions you are using. To see the client
protocols installed use the Client Networking Utility (on the client) there
are buttons that will let you change the order, and to check the for server
protocols use the Server Networking Utility on the server.
As far as speed, I believe they can be about the same, but with names pipes
there are potential security issues as you are connecting directly through
the filesystem of the server.
As far as removing named pipes, it is your choice.
John|||I understand. Thanks.
--
Dan D.
"John Bell" wrote:
> Hi Dan
> "Dan D." wrote:
> > Using SS2000 SP4. We have both named pipes (it's listed first) and TCP/IP
> > enable in network libraries. I noticed in EM under current activity and
> > process info for some processes named pipes is used and for other processes
> > something called LPC is used. Is LPC aka TCP/IP? It looks like when the
> > "host" for the process is the server, then it uses LPC but when the "host" is
> > a workstation it uses named pipes. Does it use named pipes for the
> > workstations because it is listed first in the network libraries? Is named
> > pipes slower than using TCP/IP. Should I list TCP/IP first and named pipes
> > second or just remove named pipes?
> >
> > Thanks,
> > --
> > Dan D.
> LPC is a shared memory connection, that is why the host is the server
> itself. The protocol used will be order by they are listed on the client, if
> you client had TCP as the first protocol to use and the server has TCP/IP
> enabled then that would be used. TCP/IP was made the primary protocol in SP3a
> so you may want to check what versions you are using. To see the client
> protocols installed use the Client Networking Utility (on the client) there
> are buttons that will let you change the order, and to check the for server
> protocols use the Server Networking Utility on the server.
> As far as speed, I believe they can be about the same, but with names pipes
> there are potential security issues as you are connecting directly through
> the filesystem of the server.
> As far as removing named pipes, it is your choice.
> John|||"Dan D." wrote:
> I understand. Thanks.
> --
> Dan D.
That is one of us then! I didn't realise it read so badly!
Johnsql

named pipes under alias

I have a SQLSERVER INSTANCE A, to which I want to connect from a Client as TEST, using the SQL Server alias functionality under the client network utility program. The alias is working fine with the TCP\IP connection but it fails when I try to connect to the SQL Server using the named pipes. In my case I'm trying to connect to a named instance of SQL Server 2000 using the following pipe: \\servername\pipe\mssql$instancename\sql\query

Any help?I have just tried this. Pain in the neck, too. When you change the name of the alias, the client network utility is all helpful, and changes the actual path, and server name. So you have to get the right path, and save it of in notepad or something. Change the name of the alias, replace the name of the server with the name of the server you want, then recover the path from notepad. I tried it, and it did not work. Then I hit the Apply button. Now it works. Does that approximate what you went through?|||I can connect to any server using the alias name with the TCP/IP, but the same doesn't work with the Named Pipes.

Named Pipes

I have a SQL Server 2000 Enterprise Edition database with a Windows 2000
operating system. The Client Network Utility the protocols that are Enabled
are TCP/IP and Named Pipes.
TCP/IP is the first protocol in the list and second is Named Pipes.
Could Named Pipes in the Enable protocol list slow down the database or
connection performance?
Thank You,
If it's just the fact that the Named Pipes protocol is enabled, there
shouldn't be any performance implication. If you are talking about the
performance implication of using named pipes vs. using TCP/IP, I'm not aware
of any significant difference as of late, although there were some references
in the past (well, way back) about named pipes being less performant in some
cases (see http://support.microsoft.com/?kbid=156430 for an example. Note
that it's last reviewed in 2003)
In general, I prefer TCP/IP not because of any performance implication, but
for administrative convenience. For instance, names pipes depend on NetBIOS,
and require more ports through a firewall.
Linchi
"Joe K." wrote:

> I have a SQL Server 2000 Enterprise Edition database with a Windows 2000
> operating system. The Client Network Utility the protocols that are Enabled
> are TCP/IP and Named Pipes.
> TCP/IP is the first protocol in the list and second is Named Pipes.
> Could Named Pipes in the Enable protocol list slow down the database or
> connection performance?
> Thank You,
>

Named Pipes

I am using TCP/IP for my network protocol. Is there any
need to use Named Pipes? I would like to remove this
protocol in SQL Server Network Utility.
Thank you.There's really no reason to remove it. It gives you an alternate IPC to
connect to the server with if for example we're unable to bind to the TCP
port. MDAC 2.6 clients then also have alternate means to connect to your
server. If they attempt to connect via sockets and fail, the client
transparently will attempt making a Named Pipe connection. This is of
great benefit to users who are no interested in how SQL connects, just that
it connects.
If your SQL Server is behind a firewall, the firewall should be configured
to only allow the tcp traffic for SQL. There's no additional overhead on
the server to listen on both netlibs.
If you're using a SQL Cluster then you won't be able to remove Named Pipes
after applying sp3.
831127 Named Pipes Support Cannot Be Removed on a Virtual Server That Is
http://support.microsoft.com/?id=831127
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||If the SQL instance runs in a cluster, Microsoft advises
you not to remove the support for named pipes. Otherwise,
bad things can happen (See KB article 831127).
Also check out KB 818806 -- Some Named Pipes Features Are
Not Disabled After You Disable the Named Pipes Protocol.
I hate to run into an unexpected dependency at a most
inconvenient time, and have chosen to keep both named
pipes and TCP sockets as a standard.
Do you have any specific reasons for preventing SQL Server
from listening on named pipes?
Linchi

quote:

---

>--Original Message--
>I am using TCP/IP for my network protocol. Is there any
>need to use Named Pipes? I would like to remove this
>protocol in SQL Server Network Utility.
>Thank you.
>.
>

---

|||Kevin;

quote:

---

> If they attempt to connect via sockets and fail,
> the client transparently will attempt making a
> Named Pipe connection. This is of

---

What are the exactly conditions for this 'transparent
attempt of making a Named Pipe connection' to occur? What
are scenarios in which this transparent attempt will not
be 'attempted'? I'm thinking about the situation when you
use a server alias or prefix your server name with 'tcp:'.
Linchi

quote:

---

>--Original Message--
>There's really no reason to remove it. It gives you an

---

alternate IPC to

quote:

---

>connect to the server with if for example we're unable to

---

bind to the TCP

quote:

---

>port. MDAC 2.6 clients then also have alternate means to

---

connect to your

quote:

---

>server. If they attempt to connect via sockets and fail,

---

the client

quote:

---

>transparently will attempt making a Named Pipe

---

connection. This is of

quote:

---

>great benefit to users who are no interested in how SQL

---

connects, just that

quote:

---

>it connects.
>If your SQL Server is behind a firewall, the firewall

---

should be configured

quote:

---

>to only allow the tcp traffic for SQL. There's no

---

additional overhead on

quote:

---

>the server to listen on both netlibs.
>If you're using a SQL Cluster then you won't be able to

---

remove Named Pipes

quote:

---

>after applying sp3.
>831127 Named Pipes Support Cannot Be Removed on a Virtual

---

Server That Is

quote:

---

>http://support.microsoft.com/?id=831127
>
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and

---

confers no rights.

quote:

---

>
>.
>

---

Named Pipes

I have a SQL Server 2000 Enterprise Edition database with a Windows 2000
operating system. The Client Network Utility the protocols that are Enabled
are TCP/IP and Named Pipes.
TCP/IP is the first protocol in the list and second is Named Pipes.
Could Named Pipes in the Enable protocol list slow down the database or
connection performance?
Thank You,If it's just the fact that the Named Pipes protocol is enabled, there
shouldn't be any performance implication. If you are talking about the
performance implication of using named pipes vs. using TCP/IP, I'm not aware
of any significant difference as of late, although there were some reference
s
in the past (well, way back) about named pipes being less performant in some
cases (see http://support.microsoft.com/?kbid=156430 for an example. Note
that it's last reviewed in 2003)
In general, I prefer TCP/IP not because of any performance implication, but
for administrative convenience. For instance, names pipes depend on NetBIOS,
and require more ports through a firewall.
Linchi
"Joe K." wrote:

> I have a SQL Server 2000 Enterprise Edition database with a Windows 2000
> operating system. The Client Network Utility the protocols that are Enabl
ed
> are TCP/IP and Named Pipes.
> TCP/IP is the first protocol in the list and second is Named Pipes.
> Could Named Pipes in the Enable protocol list slow down the database or
> connection performance?
> Thank You,
>

Named Pipes

I have a SQL Server 2000 Enterprise Edition database with a Windows 2000
operating system. The Client Network Utility the protocols that are Enabled
are TCP/IP and Named Pipes.
TCP/IP is the first protocol in the list and second is Named Pipes.
Could Named Pipes in the Enable protocol list slow down the database or
connection performance?
Thank You,If it's just the fact that the Named Pipes protocol is enabled, there
shouldn't be any performance implication. If you are talking about the
performance implication of using named pipes vs. using TCP/IP, I'm not aware
of any significant difference as of late, although there were some references
in the past (well, way back) about named pipes being less performant in some
cases (see http://support.microsoft.com/?kbid=156430 for an example. Note
that it's last reviewed in 2003)
In general, I prefer TCP/IP not because of any performance implication, but
for administrative convenience. For instance, names pipes depend on NetBIOS,
and require more ports through a firewall.
Linchi
"Joe K." wrote:
> I have a SQL Server 2000 Enterprise Edition database with a Windows 2000
> operating system. The Client Network Utility the protocols that are Enabled
> are TCP/IP and Named Pipes.
> TCP/IP is the first protocol in the list and second is Named Pipes.
> Could Named Pipes in the Enable protocol list slow down the database or
> connection performance?
> Thank You,
>

Named Pipe Connection through ASP - HELP!

We have a problem with interfacing a dll which is called through an Active Server Page. Our network infrastructure uses Named Pipes on Windows 2000 with SQL Server 2000 IIS version 5.0 and MDAC 2.5.

When the ASP calls the dll which (should) insert a new record into a SQL table via a stored procedure call (wrapped as a COM object), we receive the following error:

80004005 SQL Server does not exist or access denied error.

We have tried running this from the Server Admin account, but makes no difference. If we use TCP/IP the mechanism works fine, unfortunately this is not a route we can utilse without significant overall network security implications.

Any advice much appreciated!As you probably know, that's a generic error code. It could be network problems (firewall etc), file permissions or location, or any number of other things. This link shows some of the possible causes (http://support.microsoft.com/support/kb/articles/Q169/3/77.ASP?LN=EN-US&SD=gn&FR=0&qry=80004005&rnk=1&src=DHCS_MSPSS_gn_SRCH&SPR=SQL).

naives bayes prediction

Hi,

I am trying to deploy a Naives bayes network.But in spite of I am getting an dependecy network that relates 3 variables,

I've got an classification Matrix where all the predicted values are the same.

Counts for nai 1 on [Cod Conceito]

Predicted

Missing (Actual)

0 (Actual)

1 (Actual)

2 (Actual)

3 (Actual)

4 (Actual)

5 (Actual)

6 (Actual)

7 (Actual)

8 (Actual)

9 (Actual)

Missing

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

1

2

0

57578

2499

11292

102

2374

317

80

271

989

2

0

0

0

0

0

0

0

0

0

0

0

3

0

0

0

0

0

0

0

0

0

0

0

4

0

0

0

0

0

0

0

0

0

0

0

5

0

0

0

0

0

0

0

0

0

0

0

6

0

0

0

0

0

0

0

0

0

0

0

7

0

0

0

0

0

0

0

0

0

0

0

8

0

0

0

0

0

0

0

0

0

0

0

9

0

0

0

0

0

0

0

0

0

0

0

I tried to deploy the same data on Tanagra's software and I've got predictions on the other values.

I tried to change all the parameters but the results are always the same

thanks in advance

Post This question in the data mining forum: http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=81&SiteID=1|||

What happens when you try to use decision trees?

One clarification - our Naive Bayes algorithm is a Naive Bayes classifier, not a Naive Bayes network. This may be the difference between the packages, but I'm not familiar with the package you mentioned.

|||

with decision trees it appears with several nodes but the classification matrix have the same distribution. only value 1 has predicted values

|||

Is the target column modeled as Discrete or Discretized? If Discretized, could you try changing it to discrete?

naives bayes prediction

Hi,

I am trying to deploy a Naives bayes network.But in spite of I am getting an dependecy network that relates 3 variables,

I've got an classification Matrix where all the predicted values are the same.

Counts for nai 1 on [Cod Conceito]PredictedMissing (Actual)0 (Actual)1 (Actual)2 (Actual)3 (Actual)4 (Actual)5 (Actual)6 (Actual)7 (Actual)8 (Actual)9 (Actual)Missing0000000000000000000000012057578249911292102237431780271989200000000000300000000000400000000000500000000000600000000000700000000000800000000000900000000000

I tried to deploy the same data on Tanagra's software and I've got predictions on the other values.

I tried to change all the parameters but the results are always the same

thanks in advance

Post This question in the data mining forum: http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=81&SiteID=1|||

What happens when you try to use decision trees?

One clarification - our Naive Bayes algorithm is a Naive Bayes classifier, not a Naive Bayes network. This may be the difference between the packages, but I'm not familiar with the package you mentioned.

|||

with decision trees it appears with several nodes but the classification matrix have the same distribution. only value 1 has predicted values

|||

Is the target column modeled as Discrete or Discretized? If Discretized, could you try changing it to discrete?

naives bayes prediction

Hi,

I am trying to deploy a Naives bayes network.But in spite of I am getting an dependecy network that relates 3 variables,

I've got an classification Matrix where all the predicted values are the same.

Counts for nai 1 on [Cod Conceito]PredictedMissing (Actual)0 (Actual)1 (Actual)2 (Actual)3 (Actual)4 (Actual)5 (Actual)6 (Actual)7 (Actual)8 (Actual)9 (Actual)Missing0000000000000000000000012057578249911292102237431780271989200000000000300000000000400000000000500000000000600000000000700000000000800000000000900000000000

I tried to deploy the same data on Tanagra's software and I've got predictions on the other values.

I tried to change all the parameters but the results are always the same

thanks in advance

Post This question in the data mining forum: http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=81&SiteID=1|||

What happens when you try to use decision trees?

One clarification - our Naive Bayes algorithm is a Naive Bayes classifier, not a Naive Bayes network. This may be the difference between the packages, but I'm not familiar with the package you mentioned.

|||

with decision trees it appears with several nodes but the classification matrix have the same distribution. only value 1 has predicted values

|||

Is the target column modeled as Discrete or Discretized? If Discretized, could you try changing it to discrete?

sql

naives bayes prediction

Hi,

I am trying to deploy a Naives bayes network.But in spite of I am getting an dependecy network that relates 3 variables,

I've got an classification Matrix where all the predicted values are the same.

Counts for nai 1 on [Cod Conceito]

Predicted

Missing (Actual)

0 (Actual)

1 (Actual)

2 (Actual)

3 (Actual)

4 (Actual)

5 (Actual)

6 (Actual)

7 (Actual)

8 (Actual)

9 (Actual)

Missing

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

0

1

2

0

57578

2499

11292

102

2374

317

80

271

989

2

0

0

0

0

0

0

0

0

0

0

0

3

0

0

0

0

0

0

0

0

0

0

0

4

0

0

0

0

0

0

0

0

0

0

0

5

0

0

0

0

0

0

0

0

0

0

0

6

0

0

0

0

0

0

0

0

0

0

0

7

0

0

0

0

0

0

0

0

0

0

0

8

0

0

0

0

0

0

0

0

0

0

0

9

0

0

0

0

0

0

0

0

0

0

0

I tried to deploy the same data on Tanagra's software and I've got predictions on the other values.

I tried to change all the parameters but the results are always the same

thanks in advance

Post This question in the data mining forum: http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=81&SiteID=1|||

What happens when you try to use decision trees?

One clarification - our Naive Bayes algorithm is a Naive Bayes classifier, not a Naive Bayes network. This may be the difference between the packages, but I'm not familiar with the package you mentioned.

|||

with decision trees it appears with several nodes but the classification matrix have the same distribution. only value 1 has predicted values

|||

Is the target column modeled as Discrete or Discretized? If Discretized, could you try changing it to discrete?

MySQL

Hello,
When I try to connect to my MySQL server (on my webserver) via my ODBC
connector, I receive a "general network error". Does anyone know what this
is or what is causing this so I can get around it?
Thanks,
Evan M.
evan AT radiologyonesource DOT com
Evan,
This is a Microsoft SQL Server group, you probably won't get a reply to
your MySQL question here. Try http://dev.mysql.com/support/
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Evan McCutchen wrote:
> Hello,
> When I try to connect to my MySQL server (on my webserver) via my ODBC
> connector, I receive a "general network error". Does anyone know what this
> is or what is causing this so I can get around it?
> Thanks,
> Evan M.
> evan AT radiologyonesource DOT com
>
|||Mark,
Thanks for the direction! It helped alot!!
Evan McCutchen
Evan AT radiologyonesource. DOT com
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:u6FYV57UEHA.2320@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Evan,
> This is a Microsoft SQL Server group, you probably won't get a reply to
> your MySQL question here. Try http://dev.mysql.com/support/
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Evan McCutchen wrote:
this[vbcol=seagreen]

MySQL

Hello,
When I try to connect to my mysql server (on my webserver) via my ODBC
connector, I receive a "general network error". Does anyone know what this
is or what is causing this so I can get around it?
Thanks,
Evan M.
evan AT radiologyonesource DOT comEvan,
This is a Microsoft SQL Server group, you probably won't get a reply to
your mysql question here. Try http://dev.mysql.com/support/
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Evan McCutchen wrote:
> Hello,
> When I try to connect to my mysql server (on my webserver) via my ODBC
> connector, I receive a "general network error". Does anyone know what this
> is or what is causing this so I can get around it?
> Thanks,
> Evan M.
> evan AT radiologyonesource DOT com
>|||Mark,
Thanks for the direction! It helped alot!!
Evan McCutchen
Evan AT radiologyonesource. DOT com
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:u6FYV57UEHA.2320@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Evan,
> This is a Microsoft SQL Server group, you probably won't get a reply to
> your mysql question here. Try http://dev.mysql.com/support/
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Evan McCutchen wrote:
this[vbcol=seagreen]

MySQL

Hello,
When I try to connect to my MySQL server (on my webserver) via my ODBC
connector, I receive a "general network error". Does anyone know what this
is or what is causing this so I can get around it?
Thanks,
Evan M.
evan AT radiologyonesource DOT comEvan,
This is a Microsoft SQL Server group, you probably won't get a reply to
your MySQL question here. Try http://dev.mysql.com/support/
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Evan McCutchen wrote:
> Hello,
> When I try to connect to my MySQL server (on my webserver) via my ODBC
> connector, I receive a "general network error". Does anyone know what this
> is or what is causing this so I can get around it?
> Thanks,
> Evan M.
> evan AT radiologyonesource DOT com
>|||Mark,
Thanks for the direction! It helped alot!! :)
Evan McCutchen
Evan AT radiologyonesource. DOT com
"Mark Allison" <marka@.no.tinned.meat.mvps.org> wrote in message
news:u6FYV57UEHA.2320@.TK2MSFTNGP10.phx.gbl...
> Evan,
> This is a Microsoft SQL Server group, you probably won't get a reply to
> your MySQL question here. Try http://dev.mysql.com/support/
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Evan McCutchen wrote:
> > Hello,
> >
> > When I try to connect to my MySQL server (on my webserver) via my ODBC
> > connector, I receive a "general network error". Does anyone know what
this
> > is or what is causing this so I can get around it?
> >
> > Thanks,
> > Evan M.
> > evan AT radiologyonesource DOT com
> >
> >

my sql server not listed in pull down list of 3rd party tool

hi there,
I am installing a network managing tool in a test environment that relies on
sql database. when opening the pull down list I can see all sql and msde
server from my colleagues but mine.
When introducing it manually with all credentials and domain info and hit
"test logon", it returns: "There was an error testing the windows logon
credentials. windows reports the error as Logon failure: uknown user name or
bad password. Latter are all correct.
- Why can I not see the server in the pull down menu?
- What could be the connection issue?
Dominique
1. It probably uses some flavor of SQLBrowseConnect and not
all servers are guaranteed to be listed due to network
issues, if services are running, protocols, etc. You can
find more information in the following article:
http://www.sqldev.net/misc/ListSQLSvr.htm
2. I'm not sure what tool you are using or what you mean
exactly by introducing it manually, but if windows gives you
an error of unknown user name or bad password, then you
likely have not used the correct user and password. You can
test by logging into the domain with the user name and
password. If it works and the tool doesn't, you should
contact the vendor of the network tool.
-Sue
On Mon, 31 Jan 2005 14:20:47 +0100, "ITspecialist"
<hotspare@.hotmail.com> wrote:

>hi there,
>I am installing a network managing tool in a test environment that relies on
>sql database. when opening the pull down list I can see all sql and msde
>server from my colleagues but mine.
>When introducing it manually with all credentials and domain info and hit
>"test logon", it returns: "There was an error testing the windows logon
>credentials. windows reports the error as Logon failure: uknown user name or
>bad password. Latter are all correct.
>- Why can I not see the server in the pull down menu?
>- What could be the connection issue?
>Dominique
>

my sql server not listed in pull down list of 3rd party tool

hi there,
I am installing a network managing tool in a test environment that relies on
sql database. when opening the pull down list I can see all sql and msde
server from my colleagues but mine.
When introducing it manually with all credentials and domain info and hit
"test logon", it returns: "There was an error testing the windows logon
credentials. windows reports the error as Logon failure: uknown user name or
bad password. Latter are all correct.
- Why can I not see the server in the pull down menu?
- What could be the connection issue?
Dominique1. It probably uses some flavor of SQLBrowseConnect and not
all servers are guaranteed to be listed due to network
issues, if services are running, protocols, etc. You can
find more information in the following article:
http://www.sqldev.net/misc/ListSQLSvr.htm
2. I'm not sure what tool you are using or what you mean
exactly by introducing it manually, but if windows gives you
an error of unknown user name or bad password, then you
likely have not used the correct user and password. You can
test by logging into the domain with the user name and
password. If it works and the tool doesn't, you should
contact the vendor of the network tool.
-Sue
On Mon, 31 Jan 2005 14:20:47 +0100, "ITspecialist"
<hotspare@.hotmail.com> wrote:

>hi there,
>I am installing a network managing tool in a test environment that relies o
n
>sql database. when opening the pull down list I can see all sql and msde
>server from my colleagues but mine.
>When introducing it manually with all credentials and domain info and hit
>"test logon", it returns: "There was an error testing the windows logon
>credentials. windows reports the error as Logon failure: uknown user name o
r
>bad password. Latter are all correct.
>- Why can I not see the server in the pull down menu?
>- What could be the connection issue?
>Dominique
>