Quantcast
Channel: West Wind Message Board Messages
Viewing all articles
Browse latest Browse all 10393

Re: UNC shares accessible, mapped drives not

$
0
0
Re: UNC shares accessible, mapped drives not
Web Connection
Re: UNC shares accessible, mapped drives not
04/28/2012
05:03:50 PM
3HN10KO4J Show this entire thread in new window
Gratar Image based on email address
From:
Rick Strahl
To:
Attachments:
None

Depends on your security environment - the impersonation that the COM server runs under which is determined by the impersonation set in DCOMCNFG. If that user has rights to access the drive it'll work and if the user is an admin he can map drives from within the app as well.

+++ Rick ---



"...there are windows APIs to do this easily - also wwAPI::MapDrive..."

I just ran into this issue where users have a hard-coded path to a file that is on their shared drive "Q:\". I need to swap out that Q:\ with the UNC. While in com mode can I find out what Q:\ is? .. or is that info not available in com mode. I can't seem to find wwAPI::MapDrive in the wwAPI class.

Kevin


How are you running your server? As COM application and using non-Interactive impersonation?

Drive mappings are Windows session specific and if you're running in anything but the interactive console the drive map isn't visible. This means you should map the drive using code (there are windows APIs to do this easily - also wwAPI::MapDrive) to ensure the drive is mapped in the active Windows session.

+++ Rick ---

Moving our WC server from Win 2000, IIS5 to Win 2003 IIS6. WC version 4.68. Path is set to series of folders on a mapped drive (S:\). Running on the Win 2000 server and in development mode, the website accesses fox tables, etc. with no problem. On Win 2003 server, receive message that fox table doesn't exist. Troubleshot pathing, permissions, etc. and finally found that if the table is explicitly referenced on the map drive (versus only referencing the table name and allowing Fox to use the configured path), we still receive the message that the table doesn't exist. Tested by explicitly referencing the table using the UNC share and it did find and use the table successfully.

I'm not aware of any setting in Fox that would prevent mapped drive access (all the Fox code is the same between both servers anyway). There must be something either in WC config, or COM permissions that is preventing this. Any ideas? I'd be happy to provide details on current COM configuration if useful.





Rick Strahl
West Wind Technologies

Making waves on the Web

from Maui, Hawaii

Viewing all articles
Browse latest Browse all 10393

Trending Articles