- Apr 20, 2009
- 3,793
- 1
- 81
So we're in the process of migrating from Domain 'domain.local' to Domain 'corp.net' (just example names for the purposes of explanation).
Trusts are in place, all is mostly fine. However, in the process of testing, I find that trying to access the UNC path of \\server.domain.local\privateshare$ results in an error of 'The system cannot find the file specified.' This also happens for public shares.
The strange thing is that I can access the share via PowerShell and peruse the directories. I can also map a drive and peruse the files that way. I simply cannot do start -> run -> \\server.domain.local\privateshare$\ from a corp.net computer and user account. What gives?
(As evidenced by the fact that mapped drives/Powershell works fine under the same set of credentials (from corp.net) you should be able to see that the server is pingable and there is no permission restricting access, so this seems to be something else. Just not when using UNC paths.)
Any ideas?
Trusts are in place, all is mostly fine. However, in the process of testing, I find that trying to access the UNC path of \\server.domain.local\privateshare$ results in an error of 'The system cannot find the file specified.' This also happens for public shares.
The strange thing is that I can access the share via PowerShell and peruse the directories. I can also map a drive and peruse the files that way. I simply cannot do start -> run -> \\server.domain.local\privateshare$\ from a corp.net computer and user account. What gives?
(As evidenced by the fact that mapped drives/Powershell works fine under the same set of credentials (from corp.net) you should be able to see that the server is pingable and there is no permission restricting access, so this seems to be something else. Just not when using UNC paths.)
Any ideas?
Last edited: