 MattAll noise, no signal.Premium join:2003-07-20 Jamestown, NC kudos:12 2 edits | [WIN7] Network Share Bug? Escalated Prompt |  Normal Prompt |
Can anyone check this for me and see if they notice the same behavior?
Map a drive via Windows Explorer to whatever drive letter you want. Open a command prompt as the Administrator (Start - cmd, press CTRL+SHIFT+ENTER), and type net use. Does your drive display as Unavailable? Mine do, yet I can access them perfectly fine from a non-escalated command prompt. I can't access them by changing drive letters from the escalated command prompt.
-- trafficcloak.com - pptp/sstp vpn services |
|
|
|
 ExitWoundPorsche Snob join:2001-12-13 State College, PA | I see the same thing. I can't access it from the escalated prompt either. -- »www.theexitwound.com |
|
 MattAll noise, no signal.Premium join:2003-07-20 Jamestown, NC kudos:12 | said by ExitWound:I see the same thing. I can't access it from the escalated prompt either. Thanks for verifying it for me. I've posted a question in the official MS Windows 7 Networking forum. Hopefully we'll get an official comment on it. I'm thinking that somehow UAC runs the command prompt as a different user, even though it shows the same user, thus causing the problem.
»social.technet.microsoft.com/For···0b7c8f21 -- trafficcloak.com - pptp/sstp vpn services |
|
 Wolfie00My dog is an elitistPremium join:2005-03-12 kudos:4 | reply to Matt Actually I get slightly different behavior. You're right that the network share is not accessible from an elevated command prompt, but instead of getting a list with a status of "unavailable", I just get the message "There are no entries in the list". Works fine with a normal command prompt. |
|
 davePremium,MVM join:2000-05-04 not in ohio kudos:7 Reviews:
·Verizon FiOS
·Verizon Online DSL
1 edit | reply to Matt Standard, not just Windows 7. Network connections and drive-letter mappings are specific to a logon session. And that particular jargon means "not shared between a regular command prompt and a run-as-admin one".
Vista's the same, but it has always(*) been thus. Though UAC makes it easier to bump into the issue, I suppose (who did 'run as' before UAC?)
(*) Well, at least since XP. Windows 2000 was more complicated in that drive letters were global, but there were still protection issues involved. Likely the admin could access the user's drive letters but not vice-versa. |
|