Hi,
My client has the following network structure:
2 Windows 2003 servers :
Server 1 - Web server running IIS, ftp import and export folder,
ASP.NET SOAP web service and asp code on here.
Server 2 - SQL server with database on. Want to store images on here
accessed via a share.
Standalone servers, no active directory, so users need to be set up on
both servers.
Situation:
I have installed an ASP.NET SOAP web service tool on server 1. This
uses ASPNET account which is only a local account. Therefore, if I
want this process to write to the local machine, great it all works.
If I want to write to server 2, then I need to set up a domain account
for the ASPNET process to use. I have accomplished this in the past
and know it works (when the network structure uses active
directory/domain accounts).
The problem is that my client does not have domain accounts, so I
cannot get the ASPNET process to write to another PC. Worse still, I
can only get the ASPNET to write to the local server if the location is
on a physical drive (i.e. C:\ or D:\). If I map a drive letter (i.e.
G:\) to point to C:\Images, then the ASPNET process is unable to write
- despite the fact that C:\Images and G:\ are pointing to the local
server.
This is the same when I try to write to a local location when using UNC
path (i.e. \\localPC\Image s)
It seems as if mapped drives and UNC paths force ASPNET to be
validated/authenticated against domain accounts.
How can I get around this problem when the client does not have domain
accounts and active directory?
Many thanks.
Jimmy
