SQL Server 2000 and Visual Basic Question

[Eric Harris]

This question is probably more at home in the SQL Server newsgroup but as
I am using VB6, any responses are probably more relevant here. Anyway:

I am using VB6 and ADO (any of the latest 2.x versions) to connect to SQL
Server 2000 server on another domain. The problem lies in that the connection
attempt fails every time - even when using the IP address of the target server.
The only way I can get the connection to work is if I map a network drive
to a share on the target server. Once that network drive exists, the ADO
connection has no problems.

Right now I have the app programmatically create a network drive before attempting
the connection. This works some of the time, but is not the best way to
solve the problem. The other issue is that a Win98 client can't create a
network drive using a different username and password for the target share.

I was wondering if anyone had any experience with this, as I am completely
stumped. Also, if it helps, I am not using a DSN for the connection. (Though
I have tried it that way and I get the same result.)

Thanks in advance!
Eric Harris

[Chris Hylton]

My guess is that you've got something goofy going on w/ the network security
and the SQL security model that was chosen when SQL Server was installed...how
are you connecting the ADO connection object, are you using Authenticated
or SQL Server security, is the client machine logged into a domain and is
SQL Server on that domain and seen as a client on that domain as well...

Any number of issues here, but if you don't have all that working together...the
connection will require the client to be authenticated on that SQL box before
the connection will succeed...that's what mapping the drive does...

I wish I had a better 'definitive' answer because I've had this happen before
too...but if all the security is configured properly, the issue will resolve
itself.

But, you also indicated that you are using TCPIP to connect...rather than
names pipes...that should bypass all of that I thought...so I'm kinda confused...

Chris

"Eric Harris" <agentoz@comcast.net> wrote:
>
>This question is probably more at home in the SQL Server newsgroup but as
>I am using VB6, any responses are probably more relevant here. Anyway:
>
>I am using VB6 and ADO (any of the latest 2.x versions) to connect to SQL
>Server 2000 server on another domain. The problem lies in that the connection
>attempt fails every time - even when using the IP address of the target
server.
> The only way I can get the connection to work is if I map a network drive
>to a share on the target server. Once that network drive exists, the ADO
>connection has no problems.
>
>Right now I have the app programmatically create a network drive before
attempting
>the connection. This works some of the time, but is not the best way to
>solve the problem. The other issue is that a Win98 client can't create
a
>network drive using a different username and password for the target share.
>
>I was wondering if anyone had any experience with this, as I am completely
>stumped. Also, if it helps, I am not using a DSN for the connection. (Though
>I have tried it that way and I get the same result.)
>
>Thanks in advance!
>Eric Harris
>

[David Woodward]

Security issues are easy to fix - if you don't have the propper rights you
can request them. Sounds more like a driver problem. There is nothing wrong
with using a DSN so you may use this, making sure your systems are happy
with the driver versions.