Mapped server 2003 drives showing empty - help!

[howartp]

Hello,

 

I came in this morning to find a site-wide issues where two mapped drives from one DC were empty and showing in My Computer as 'NTFS' instead of '123GB of 456GB' or whatever it should be.

 

However looking on the server E: drive where these are located, the contents are exactly as they should be. The E: drive only holds four folders - two shared, two not. I tried sharing one of the non-shared folders then mapping this, which worked fine. There are other shares on D: and F: which are working fine.

 

Permissions look unaffected, and I'm a domain admin and thus local admin so in theory should have full access regardless.

 

The event log on the server is chock full of the usual RM garbage but I can't see anything relevant in there.

 

***Edit whilst still typing the original post***

Erm, for some reason one of the mapped drives (the main one I needed back, thankfully) has just started behaving itself again for no discernable reason?? However the other mapped drive is still empty, despite the content being there.

 

Anyone any ideas on what is causing/caused this?

 

I was going to reboot at breaktime (9.50 - 10.10) but as one drive has come back of its own accord I'd rather try and find what is causing it first?

 

Peter

[Firebeard]

Try looking at offline files synchronization?

 

If it doesnt do a full sync it plays havoc with network shares.

 

Look in the bottom right icon bar for a computer with an exclamation mark saying, computer need syning.

[howartp]

Thanks for the reply Firebeard, but unfortunately we don't use Offline Files so it is unlikely to be this

 

Any other thoughts?

 

Peter

[themightymrp]

Silly question but you dont have any USB drives or anything plugged in that are using those drive letters? Another thought, do you use DFS shares at all? I've had problems with those in the past where replication isn't working correctly

[Patrickv]

So you are you saying that your server lost it's physical drive letters? If so that can be easy fixed with Computer Management->Disk Management.

 

It could be some registry screw up or virus.