Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1157
  • Last Modified:

Accessing a local drive on Server 2003, error message "the network location cannot be reached" comes up.

Howdy folks,

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!

Jim
0
neopumpkin
Asked:
neopumpkin
  • 3
  • 2
1 Solution
 
SysExpertCommented:
Does it work from the server console directly ( NOT VIA RDP ) VNC is an alternative .

RDP normally opens up a virtual desktop when you login , and that can cause issues.


I hope this helps !
0
 
neopumpkinAuthor Commented:
Nope, unable to access the data while at the console either.  Same error message..

This is absolutely nutty, i've never seen this before!
0
 
SysExpertCommented:
I would use the XP machine to copy the folders via robocopy in the meantime, and to verify that none of the folders have been missed.

Then see if you can take ownership of all of the E drive ( After a full backup or image )


I hope this helps !

0
 
neopumpkinAuthor Commented:
delayed update..

i'm still thinking a corrupt DFS root was somewhere in amongst the cause of my problem.  i took the roundabout way and used robocopy to copy all data to my new file server, which worked like a charm.  the data was being anyway, so the DFS root became obsolete.

thanks for your input SysExpert!
0
 
neopumpkinAuthor Commented:
I should also say that i've managed to work around my own problem by using robocopy, which was the plan if i couldn't fix the DFS issue(s).

0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now