Re: WNetGetConnection ERROR_NOT_CONNECTION in w2k, different logon session.
From: S E H M B (googlegroups_at_sebastienboving.com)
Date: 11/17/04
- Next message: NPR: "Re: Making a Bluetooth BNEP connection from Windows XP SP2"
- Previous message: Doc Eucorp: "RPC Connection Aborted"
- In reply to: Alexander Nickolov: "Re: WNetGetConnection ERROR_NOT_CONNECTION in w2k, different logon session."
- Messages sorted by: [ date ] [ thread ]
Date: 17 Nov 2004 13:41:31 -0800
Sure, but the whole question is *how* to do that... It sure is not
simple.
- what exact information does it need to get from the service?
- what does that app then exactly do with it, how does it map the
drive?
We already have the logon script map the drive letter (which fails, so
doesn't do anything when the service has started on that machine).
That is not the problem directly anyhow.
Once again, the problem is not to map the same drive letter and use
files on there with both logons, that already works just fine (a 'use'
exists machine-wide). We need however to have the specific API call
"WNetGetConnection", when run by an application in the interactive
user's context, return the proper UNC information (and not
ERROR_NOT_CONNECTED). For that, some data structure must be missing
in the user's logon session. I'd like to find a clear definition of
where that lives and how to fill it in.
If you have the answer, and it's simple, please explain ;) !
thanks,
-seb.
"Alexander Nickolov" <agnickolov@mvps.org> wrote in message news:<Ok7ELvBzEHA.3408@tk2msftngp13.phx.gbl>...
> I guess I overengineered it a lot. It may be as simple as an
> app that starts upon logon of an interactive user. It'll map
> the drive in the user's context after obtaining the information
> from your service. Your service has a completely different
> mapping unrelated to the one in the interactive user's context.
- Next message: NPR: "Re: Making a Bluetooth BNEP connection from Windows XP SP2"
- Previous message: Doc Eucorp: "RPC Connection Aborted"
- In reply to: Alexander Nickolov: "Re: WNetGetConnection ERROR_NOT_CONNECTION in w2k, different logon session."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|