Sorry but you are wrong, It has nothing to do at all with network access:
1. The connection string specifies the credentials used to authenticate with
the DB server, no integrated security is used by the OP, that means that
process identity is (and cannot be) used here.
2. Sockets aren't "secured objects", that is, they aren't protected by the
OS through an ACL, that means an access token is not used, from the systems
point of view everyone can open a socket, so it has nothing to do with a
socket open either.
I have several applications running from asp.net accessing DB servers using
explicit credentials over sockets while ASPNET runs as 'aspnet' or "local
network".
Willy.
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote in
message news:%2****************@TK2MSFTNGP15.phx.gbl...
| Willy,
|
| It most certainly does have to do with network access. My response
| cited the specific case where it is an ASP.NET application where the
worker
| process runs under the ASPNET account. That account does not have network
| access.
|
| If the database driver is trying to open a socket, then it's going to
| fail. It has nothing to do with whether or not it is integrated security.
|
| --
| - Nicholas Paldino [.NET/C# MVP]
| -
mv*@spam.guard.caspershouse.com
|
| "Willy Denoyette [MVP]" <wi*************@telenet.be> wrote in message
| news:%2***************@TK2MSFTNGP09.phx.gbl...
| > This has nothing to do with network access, integrated security is not
| > used
| > here, the connection string contains explicit user credentials.
| >
| > Willy.
| >
| > "Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote
| > in
| > message news:O$**************@TK2MSFTNGP12.phx.gbl...
| > | Peter,
| > |
| > | By chance, are you running this in ASP.NET? If so, ASP.NET runs
| > under
| > a
| > | local user ASPNET by default that does not have network access. If
your
| > DB
| > | is on another machine, this could definitely be a problem.
| > |
| > | The same is true for a program you might have loaded from the
| > internet
| > | or your network (assuming it is not from the machine that the DB is
on).
| > |
| > | Can you give a little more information about the error?
| > |
| > | Hope this helps.
| > |
| > |
| > | --
| > | - Nicholas Paldino [.NET/C# MVP]
| > | -
mv*@spam.guard.caspershouse.com
| > |
| > | "Peter" <pc*****@nospam.nospam> wrote in message
| > | news:eo**************@TK2MSFTNGP14.phx.gbl...
| > | >I am trying to connect to a DB2 database with IBM.Data.DB2 provider
and
| > | >getting the following message
| > | >
| > | > ERROR [08001] [IBM] SQL30081N A communication error has been
| > detected.
| > | > Communication protocol being used: "TCP/IP". Communication API
being
| > | > used: "SOCKETS". Location where the error was detected:
| > "10.100.1.69".
| > | > Communication function detecting the error: "connect". Protocol
| > specific
| > | > error code(s): "10061", "*", "*". SQLSTATE=08001
| > | >
| > | > When I use DB2 control center or setup a ODBC connection it works
fine
| > | > Here is my connection string:
| > | >
| > | > Database=mydatabase;Server=db2server:6000;UID=test user;PWD=password
| > | >
| > | > Does anyone have a solution for this problem, or how to trouble
shoot
| > | > this?
| > | >
| > | >
| > | > Thank You
| > | >
| > | >
| > | > Peter
| > | >
| > | >
| > |
| > |
| >
| >
|
|
