Talk:Administrative share

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by Networking task force (assessed as Low-importance).

Microsoft: Windows Low‑importance

	This article is within the scope of WikiProject Microsoft, a collaborative effort to improve the coverage of articles relating to Microsoft on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.MicrosoftWikipedia:WikiProject MicrosoftTemplate:WikiProject MicrosoftMicrosoft articles
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by WikiProject Microsoft Windows (assessed as Low-importance).

The organization and visual appeal might be bad, please post any comments or edit the page to make it better.

Dang[edit]

Why did I have to post it without logging in? Doh! - mboverload

Security[edit]

This article does not mention security. Is it easy crackable? Bad security? worm spread this way?

... And what happens if the Admin password is blank? Everyone can read the whole C: drive???

--Yes this is the case.. if the adminstrator password is blank, all system drives are fully accessible with FULL admin rights.

--This is only true for Windows 2000. As of Windows XP Home edition and beyond, Windows implements the "ForceGuest" feature when the local Administrator account has a blank password. When a remote user authenticates to Windows XP (and later) as Administrator with a blank password, Windows will actually assign to their session a Guest access token, not an Administrator access token. This is arguably *more* secure against such remote attacks than assigning a weak or easily-guessed password to the local Administrator account.--ParanoidMike 18:29, 14 June 2007 (UTC)[reply]

Slashes or backslashes?[edit]

The Windows XP dialog box has Example: \\server\share Spalding 20:14, 27 June 2006 (UTC)[reply]

!!! Holy crap I can't believe I missed that. Thanks! --mboverload @ 21:41, 27 June 2006 (UTC)[reply]

Suggested merge from Ipc Share[edit]

I've suggested that the Ipc share article be merged into this, as I believe the IPC Shares are a subset/other name for of the Administrative shares M2Ys4U 13:45, 15 July 2007 (UTC)[reply]

I think that the IPC Share might also be better off as a subsection of the IPC page because the current IPC Share page just talks about it as a specific windows share for inter-proc communication. Veleek 08:07, 29 September 2007 (UTC)[reply]

I STRONGLY disagree. The administrative shares (C$,ADMIN$,etc) are actual SHARES that appear in the windows network. This really does not go along with the IPC$, as I would expect to access it as I would any other of the administrative share. It appears in the "Shares" under computer management - but then something like ".NET ASP Account" also appears under "User Accounts" in My Computer. My point is that $IPC doesn't behave completely like an administrative Share, because an Administrative Share was designed to host exactly that - a SHARE. $IPC is for queries and net view commands etc, and we can't browse it directly like C$ (i've got a nickel for whoever can do it :P). QED :) —Preceding unsigned comment added by 137.207.238.106 (talk) 15:22, 1 October 2007 (UTC)[reply]

Disagree. The IPC$ "share" is a misnomer, representing something that isn't well-described in Windows lore. While IPC$ is a resource accessible remotely via 139/tcp or 445/tcp, it's not a "share" because there are no files accessible to the remote client when connecting to the IPC$ resource. Better that IPC$/Admin$/C$ be represented under a subcategory of "hidden resources", or that they're represented among a set of "created-by-default resources on Windows computers". Either of those more accurately reflects the relationship between IPC$ and "administrative shares".ParanoidMike (talk) 20:59, 31 December 2007 (UTC)[reply]

User w/Local Admin rights has blocked access[edit]

For a variety of reasons, a user with local admin rights on his machine has inappropriately blocked remote access to his XP machine in a fit of pique (the machine is a corporate asset and has proprietary IP on it). I want to find the lowest stress way to unblock and regain access. I'll remove his local admin privileges if necessary, but I'd rather avoid this just by grabbing back access remotely. It's complicated. Using my account with Domain Admin rights, I can see the ADMIN$ drive, but not C$. Is there some way to find out what he has renamed this drive? (BTW - I normally post under another WP account but I choose to remain anonymous for this posting). GenMan2000 19:48, 11 October 2007 (UTC)[reply]

Command to delete all hidden shares and a preliminary .reg file[edit]

NET SHARE *$ /delete

It only works when the neccessary services are running

Plz. @somebody add them. —Preceding unsigned comment added by 93.220.34.29 (talk) 06:26, 27 January 2010 (UTC)[reply]

Access from Cygwin?[edit]

On Cygwin you can do 'cd //computer/share' and access normal shares just as if it was an ordinary directory/folder. But I have a hard time doing the same with the hidden and/or administrative shares. I guess Cygwin misinterprets the $, so 'cd //computer/c$' gives 'No such file or directory'. Does anyone know a way around this? --Gorm (talk) 12:19, 28 January 2011 (UTC)[reply]

Administrative shares for Wikipedia administrators and sysops and Wikia Staff, Admins, Bureaucrats, etc.[edit]

Can they have these? 112.209.65.184 (talk) 02:53, 19 December 2015 (UTC)[reply]