Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Remote share access

Status
Not open for further replies.

rrdavis07

MIS
Jun 2, 2004
88
US
I'm sure this has been addressed somewhere, but I can't seem to find it...

When accessing a share from a login that does not have explicit access to that share, most of the time I get the usual message stating that I do not have access to that share. Sometimes, depending either upon the computer I accessing from, or the share I'm attempting to access, I get a login screen. Giving the proper credentials allows access.

I don't understand the difference. Why am I not allow access in some situations, while in others I am given the opportunity to login???

Randy Davis, MCP

Systems Administrator
The Independent School

 
Oops, I forgot to include some information: We are on a Domain with AD. All shares are on server computers attached to the domain. Trying to access the share while logged into the domain, but from profiles that do not have explicit access to the shares.

Randy Davis, MCP

Systems Administrator
The Independent School

 
Are you trying to write a file to the Share or just read from it. The Permissions of the Share might have a Users (general) item with Read Permissions. The NTFS Permissions might also be overriding any Share Permissions. Either might have an Everyone Permission set too.

So have a look at what Permissions are set for the Shares you can and can't access.

If your Login Credential is not saved and remembered by the Server, but you are allowed access to the file, you will perhaps see the Login Box in that instance.
 
I suspect that it is related to wether or not the particular server/partition that contains the share has an administrative share (C$, D$ or whatever). Way back when, I recall reading something that is tickling my memory. As I recall (which might not be quite right), when a Windows client first connects to a remote host, it actually tries to access the Administrative Share first, before the share that was actually requested. I suspect that the different behavior might be related to wether or not the Administrative Share actually exists for that particular partion.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top