File IO issue on a network...how?

I have a piece of code that works great. Now, I want to move my path from c:\data to h:\data (a network drive). I googled around and figured out that the Directory object doesn't work on network drives and figured I had to change my code ... but, I am kind of stumped. (OLD CODE) string[] XMLList = Directory.GetFiles(Session["XMLPath"].ToString(), "*.xml"); ddCustomer.Items.Add(" "); ddOfficers.Items.Add(" "); ddAccount.Items.Add(" "); foreach (string XMLFile in XMLList) { ParseXML(XMLFile); ...ect... (NEW CODE) FileIOPermission FPerm; FPerm = new FileIOPermission(FileIOPermissionAccess.AllAccess, Session["XMLPath"].ToString()); string[] XMLList = fileIOPerm.GetPathList(FileIOPermissionAccess.Read); This "XMLList" is only a list files or folder to which I have assigned permissions. How do I get my directory list like in my old code? Thanks. William

Forget it. I got it. First, I used a UNC and it worked better than mapping a drive letter. Logged in as to domain admin, giving full control permission from the root of the server drive all the way down the path to EVERYONE--still did not work. Second, I was able to use the UNC path, if and only if, I shared the specific folder I was interested in. For example, on my test domain server I had \\dcfile\data shared with full access to EVERYONE: not good enough. The data was in \\dcfile\data\teststuff. Once shared "teststuff" and used the UNC path of "\\dcfile\teststuff" (with adequate access) it worked, but I got the "Logon failure: unknown user name or bad password" error. I solved this, with the continuing credit being passed on to, http://www.dotnet247.com/247reference/msgs/25/127951.aspx. Thanks anyway. William