Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Denied access to share

Posted on 2014-01-15
3
Medium Priority
?
40 Views
Last Modified: 2015-10-04
Hi All -

I have a terminal server (Server 2008 x64) that at times - can''t reach a share on an applciation server in teh background.

AppServerA is the applciation server with a share called ShareA with Everyone Full Permissions. On a domain (of course) and domain controllers are 2003.

Terminal Servers A-D all access ShareA on AppServerA for use in a third party program.

Occasionally the clients that connect to TerminalServerA will call stating they aregetting errors trying to access ShareA.

The third party program throws an error about not being able to access teh destination \\AppServerAIP\ShareA (So \\172.16.0.2\ShareA)

Next step is logging into TerminslServerA and clicking Start then RUn and doign a \\172.16.0.2 and clicking OK. It says it is unable to reach server. (Although you can ping it from that server and on TerminalServerB-D - they all can)

I'm used to seeing \\HOSTNAME not resolving - being a DNS issue but not \\IP

So far the only workaroudn we have found is to boot the offending TerminalServerA. When it comes back up - it can resolve \\172.16.0.2\ShareA.

Booting AppServerA does nothign to the scenario.

No errors in TerminalServerA Windows Error Log
Have tried removign server from domain (back to workgrouop) and putting it back on Domain
Have tried the same thing but also change the COMPUTERNAME but no help.

Any ideas guys?
0
Comment
Question by:vpnsol123
  • 2
3 Comments
 
LVL 20

Expert Comment

by:Peter Hutchison
ID: 39782799
You say that the the share permissions have Everyone with Full Access, but what about the other half of the permissions. The NTFS permissions will also have to be set to allow users to  read, list, write, delete etc to that share.
0
 

Accepted Solution

by:
vpnsol123 earned 0 total points
ID: 39784135
Hi Thanks -

Understood but these same users are fine once you boot the terminal server. So it it were the permissions on the share itself it would misbehave regardless of a boot.

Also - didn't mention - if you take a user who is getting denied and move him\her to TerminalServerB (where people are fine) that same user will then be able to access.

No roaming profiles or anything here

Also - while it can't resolve \\172.16.0.2 it can resolve \\hostname (of the 172.16.0.2)
0
 

Author Closing Comment

by:vpnsol123
ID: 41023496
done
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Ever notice how you can't use a new drive in Windows without having Windows assigning a Disk Signature?  Ever have a signature collision problem (especially with Virtual Machines?)  This article is intended to help you understand what's going on and…
Citrix XenApp, Internet Explorer 11 set to Enterprise Mode and using central hosted sites.xml file.
This video Micro Tutorial explains how to clone a hard drive using a commercial software product for Windows systems called Casper from Future Systems Solutions (FSS). Cloning makes an exact, complete copy of one hard disk drive (HDD) onto another d…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

972 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question