OK, your Security setting in internet explorer will need to be set to
Automatically log you on with the current username and password. Now if this
doesent work, then it means that explorer is looking at the currently logged
on ID when connecting to remote sites rather than using Runas.
Try and take a look TOOLS | INTERNET OPTIONS | SECURITY | CHOOSE YOUR ZONE |
SCROLL DOWN TO USER LOGON SETTINGS
HTH
--
( OHM ) - One Handed Man
AKA Terry Burns -
http://TrainingOn.net
"Mr. Novice" <Mr******@discussions.microsoft.com> wrote in message
news:E9**********************************@microsof t.com...
Great idea. We tried it and no luck. Any other suggestions?
Chad
"OHM ( One Handed Man )" wrote:
Im taking a guess here; but it is possible that when you spawn another
process this way, that the spawned process picks up the current windows
principal not the Runas account used. You would be advised to attempt to
also spawn a Runas for the internet explorer being started.
process.start( "Runas explorer . . . . .
--
( OHM ) - One Handed Man
AKA Terry Burns - http://TrainingOn.net
"Mr. Novice" <Mr******@discussions.microsoft.com> wrote in message
news:08**********************************@microsof t.com... > Hello,
>
> I work for a company where the server administrators have two login
> ID's.
> One without admin right that we use to log into our workstations and
> one
> with
> admin rights that we use to for server administration. A co-worker and
> I
> put
> together an app in VB.Net that lets us click a button to do things that
> require admin rights like opening certain applications. We use runas to
> open
> the app with our admin id's and then any option we select opens using
> the
> admin credentials. Everything works fine with the exception of opening
> a
> UNC
> path.
>
> process.start(explorer, "\\server\share") 'does nothing
>
> process.start("\\server\share") 'will open the UNC path, but not
> with
> the administrative credentials that the app runs under. We are prompted
> for
> credentials and when we enter the id and password that the app runs
> under
> the
> path is opened no problem.
>
> Has anyone seen this problem before, or have any suggestions?
>
> Thanks!!
>
> Chad
>
>