I'm thinking the next step is to try mapping the drive to the namespace over VPN using the newdomain\username credentials. They are using the olddomain\username to connect to the new domain share, which works OK in the office however i have not tried it over the VPN from their laptop. I'm thinking this may be something to do with the credentials used to map to the dfs namespace. They can browse the share location via any of the servers \\servername\shared data (and can access via \\servername\data\shared data), however it will not let them access via the namespace They can ping the namespace name and it resolves to the correct IP. ![]() However the issue is that when the user leaves the office, and uses a third party (forticlient) VPN, they can no longer access the namespace of the new domain. When they are in the office they can access the namespace OK i.e. ![]() The user is using windows 7 and has a mapped drive (Z:) that maps to a DFS namespace in the new domain. We have a DFS namespace root that is .uk\data, with \shared data set up as a folder under the namespace. We have 4 Server 2012 R2 servers that are DFS members and replication between each server. ![]() ![]() Users laptop is connected to old domain (migration in progress), however there is a two way trust between the domains. We have an issue that's the root of a bit of a strange setup! I'll explain the scenario first.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |