Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 42
  • Last Modified:

Denied access to share

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
vpnsol123
Asked:
vpnsol123
  • 2
1 Solution
 
Peter HutchisonSenior Network Systems SpecialistCommented:
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
 
vpnsol123Author Commented:
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
 
vpnsol123Author Commented:
done
0

Featured Post

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now