Hi Denny
I'm struggling with the following DFS scenario. We have a customer with a branch and head office. For redundancy and file access speed we've deployed DFS between the two sites, which has been working well. More and more staff have been travelling (and working) between sites and we've set-up their Network Drive mappings to company.local (DFS share name) to utilize the local LAN when travelling to their remote office.
When at the head office (whether via Terminal Services or LAN access) the drive mappings work as they should. However, when at the remote office the users can still browse the network drives (on the branch DFS), however cannot make any changes (so seem to be limited to read-only access) and receive the error 'access denied' when saving existing or creating new files
I've checked the permissions on both locations's DFS's and they are verbatim, and replicate well through DFS. For testing purposes I've even made changes to permissions, to the extent of allowing 'Full Control' on a test folder for a particular user or group but to no avail. The only changes to date that allow the user to make changes in their network drive (whilst working remotely) has been to make them an "Domain Admin" (off course this has been done strictly in a test environment). Once their user profile has been added as a Domain Admin they can work from either site without any problems (via their domain.local\share drive mappings)
Just to summarize then. Users working in HQ can access\change network resources via drive mappings to domain.local\share (DFS) name. As soon as they travel to their Branch office they receive an error accessing the same share (replicated between domain controllers via DFS) and are unable to change any content in their domain.local drive mapping
Any help or suggestions would be greatly appreciated.
Ian