|
[WIN7] Windows Shared Drive versus Connecting to ComputerI have a Windows 7 desktop I use as a server. Currently, just one of the two partitions on the hard driver are set-up as a shared drive (lets call the two partitions C$ and E$ where E$ is set up to be shared). I am getting two different results though when accessing that server:
1. On a laptop, under Network, the server name comes up and when I double click it the windows explorer open the E$ drive by itself.
2. On my phone using ES Explorer or a linux device, when I enter the IP Address of the server I literally get both the C$ and the E$ and full access. Why is it when I use the IP Address for the computer and the username and password I am getting full computer access? Does this have something to do with workgroups? I'm also running Teamviewer on the server, but am unsure whether that has anything to do with it.
Thanks. |
|
KalfordSeems To Be An Rtfm Problem. MVM join:2001-03-20 Ontario |
I'm pretty sure it's simply because Windows Explorer doesn't show admin shares ($) , but it does show network shares Because Windows Explorer only presents one drive, it probably opens it as an automatic default. Yet You still have access to the C$ admin share. (user permissions permitting) ) For example if after you opened the E drive, you manually changed the address to point to the c$ drive, it would open on the condition that sufficient user permissions were met. ES Explorer, on the other hand, doesn't hide drive names ending in $ (admin shares). It seems to enumerate all (network) drives that are available be they regular network shares, or admin shares. (I could of course be wrong. . but I'm pretty sure it's something like that ) |
|
sivranVive Vivaldi Premium Member join:2003-09-15 Irving, TX |
sivran
Premium Member
2014-Sep-29 8:12 pm
said by Kalford:ES Explorer, on the other hand, doesn't hide drive names ending in $ (admin shares). It seems to enumerate all (network) drives that are available be they regular network shares, or admin shares. Yes. This is typical, so it's probably a default of the vanilla samba/cifs client. Naturally, permissions are still enforced: you will not be able to mount a share you do not have permission to. You can look, but not touch. |
|
|
So basically what you're saying, is that even though I can see my C$ drive, I shouldn't be able to read or write to it? I can definitely click on it and its subfolders. I just found it a little alarming that I can see my whole hard drive's partition structure from using ES Explorer or a Ubuntu connect to server program, but on a Windows laptop, it shows only the partition I actually have shared. |
|
sivranVive Vivaldi Premium Member join:2003-09-15 Irving, TX |
sivran
Premium Member
2014-Sep-30 6:03 pm
Permissions are still enforced, so you have at the very least, read access. You wouldn't be able to see the contents, otherwise. Windows clients should hide shares ending with $, regardless of the user's permissions. For example, by default my Win8 desktop won't even let me see the contents of the C$ admin share (or any admin share) with an administrative account. Windows XP on the other hand will--provided I use an admin account. My only Win7 machine is my work laptop, which I can't use for testing, but since you can read your admin share, 7's behavior is probably more like XP, less like 8. But, yes, like I said -- Linux implementations of Windows file sharing generally don't respect the dollar sign. Apropos I suppose since linux does not worship the almighty dollar. |
|
dave Premium Member join:2000-05-04 not in ohio |
dave
Premium Member
2014-Sep-30 6:08 pm
It's not actually the dollar sign, it's the "hidden" flag in the share properties. But on Windows the two go hand-in-hand.
("Hidden" is not a security option, it's a sign that the share is considered not ordinarily interesting - like the "hidden" file attribute on Windows, or dot-files on Unix). |
|
psloss Premium Member join:2002-02-24 |
to SteelersFan
The most popular Windows client -- Explorer -- hides shares with the $ suffix and administrative shares (which have the $ suffix, but are also typed as such -- STYPE_SPECIAL + STYPE_DISKTREE), but it will show the local ones if you plug one of the accepted variations of the UNC path into it (this screenshot shows File Explorer's redecorated version of "\\127.0.0.1\c$" from a x64 VM with a relatively virginal OS install). Over an uncomplicated network (such as found in many homes), the legacy LAN Manager/LanMan API functions still work fine (NetShareEnum, NetShareGetInfo, etc.) -- provided one has already established access. (Either "automatically" via the duplicate credentials, or manually via 'net use \\COMPUTER-NAME\ipc$ /u:User password' route.) An example hitting a separate Win8.1 VM (with wanton sharing enabled) from a Win7 machine: Running EnumerateShares (level 1)
Share information for \\SHELF-PC:
Number of shares = 4
Share 1 Name: ADMIN$
Type: 80000000
Remark: Remote Admin
Share 2 Name: C$
Type: 80000000
Remark: Default share
Share 3 Name: IPC$
Type: 80000003
Remark: Remote IPC
Share 4 Name: Users
Type: 00000000
Remark:
(Level 1 essentially grabbing these structures over the network: » msdn.microsoft.com/en-us ··· %29.aspx ) |
|
dave Premium Member join:2000-05-04 not in ohio |
dave
Premium Member
2014-Sep-30 8:18 pm
net view \\COMPUTER /all lists all shares; C:\users\dave>net view \\foo /all
Shared resources at \\foo
laptop
Share name Type Used as Comment
-----------------------------------------------
ADMIN$ Disk Remote Admin
C$ Disk Default share
IPC$ IPC Remote IPC
print$ Disk Printer Drivers
The command completed successfully.
|
|