Accessing a local drive on Server 2003, error message "the network location cannot be reached" comes up.
Posted on 2008-11-13
This issue has me stumped, so i'm hoping one of the EE gurus here can help out.
I have a Windows Server 2003 Std install, acting as a file server. The disk system is setup in a RAID 5 and has been chopped up into the C:, D:, E: and F: drives. I'm getting ready to decommission this file server and I want to copy all of the data from the drives to another server, using robocopy.
Here's where i'm stumped... whenever I RDP into the file server, I open up windows explorer and browse the contents of each Drive (partition), as I would on any other server, desktop or laptop. Whenever I try to access random folders on the E: drive, I get the following message: "E:\Data\foldername is not accessible. The network location cannot be reached."
Now this problem is isolated to the E: drive, all other Drives allow me to access data without any problems.
What confuses me even more, is that I can go to a client XP Pro machine on the network, go to start > run > type in \\servername and access all the files and folders on the E: drive with no problems, but is the same server that won't let me access the same data locally. Very strange indeed.
I see that DFS is somewhat configured on this server, at least the name space is, but no replication partners are configured. Being that i'm not a master of DFS, I do have a hunch that DFS is causing me some grief here.
Anyone able to shed some light on this issue? Many thanks in advance!