I've got DFS set up for one network share.
I randomly run into issues with terminal server users, who cannot map to that share.
I'm using S: as the mapped drive letter.
When investigating the problem, it appears the user's s: is not mapped to anything. From the command line, NET USE S: /DELETE yields "the network connection could not be found."
However, when trying to manually map, NET USE S: \\DOMAIN.EXT\SHARED I get "The local device name is already in use."
When atttempting to map through explorer using "Map network drive", S: appears to not be mapped to anything. When trying to map it to the DFS Share, I get "The devise S: has a remembered connection to . Do you wish to replace the current connection with \\domain.ext\shared?" That IS TYPED CORRECTLY, it state's there's a connection to " ". When I say "Yes" it fails.
The odd thing about it, is that I can map S: to ANY OTHER SHARE on the network, just not the one pointed to by DFS. If I try to bypass the DFS location and map to the actual server share that DFS points to, it still doesn't work. I can only map S: to another share.
If I try to map T: to the DFS share, it works without issue.
This is a very odd problem, and I've yet to find even a hint at a solution. I'm hoping someone can please help me with this.
I randomly run into issues with terminal server users, who cannot map to that share.
I'm using S: as the mapped drive letter.
When investigating the problem, it appears the user's s: is not mapped to anything. From the command line, NET USE S: /DELETE yields "the network connection could not be found."
However, when trying to manually map, NET USE S: \\DOMAIN.EXT\SHARED I get "The local device name is already in use."
When atttempting to map through explorer using "Map network drive", S: appears to not be mapped to anything. When trying to map it to the DFS Share, I get "The devise S: has a remembered connection to . Do you wish to replace the current connection with \\domain.ext\shared?" That IS TYPED CORRECTLY, it state's there's a connection to " ". When I say "Yes" it fails.
The odd thing about it, is that I can map S: to ANY OTHER SHARE on the network, just not the one pointed to by DFS. If I try to bypass the DFS location and map to the actual server share that DFS points to, it still doesn't work. I can only map S: to another share.
If I try to map T: to the DFS share, it works without issue.
This is a very odd problem, and I've yet to find even a hint at a solution. I'm hoping someone can please help me with this.
