Copy files on Network

[Markus Weber]

Hallo!

I have created an VB-ActiveX-Componente that copy files on network.
This works on one my development computer when I install application
on other IIS servers (files to copy on same server with same rights) I
get error message "Invalid filename or number". So what can cause this
problems?

Thnaks in advance!

[Ken Schaefer]

a) Are you using a UNC path?
b) What user context is the component running under?

Cheers
Ken
"Markus Weber (Megalith GmbH)" <m.*****@megalith-software.de> wrote in
message news:41****************@msnews.microsoft.com...

Hallo!

I have created an VB-ActiveX-Componente that copy files on network.
This works on one my development computer when I install application
on other IIS servers (files to copy on same server with same rights) I
get error message "Invalid filename or number". So what can cause this
problems?

Thnaks in advance!

[Markus Weber]

>a) Are you using a UNC path?
Yes, I already found out tha mapped drives aren't supported

b) What user context is the component running under?

As I know components are running under IIS always under the user
"IUSR_XXX" (XXX = machine name), this is a locale user so I set access
rights of files on network so that "Everyone" can read them.

[Bob Barrows [MVP]]

Markus Weber (Megalith GmbH) wrote:

a) Are you using a UNC path?

Yes, I already found out tha mapped drives aren't supported

b) What user context is the component running under?

As I know components are running under IIS always under the user
"IUSR_XXX" (XXX = machine name), this is a locale user so I set access
rights of files on network so that "Everyone" can read them.

But IUSR is a local account and will not be in the network server's Everyone
group.

You need to force ASP to run under a network account which has permissions
to te network resources needed. This can be done in the Directory Security
tab in IIS Manager.

Bob Barrows

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

[Ken Schaefer]

"Markus Weber (Megalith GmbH)" <m.*****@megalith-software.de> wrote in
message news:41****************@msnews.microsoft.com...

a) Are you using a UNC path?

Yes, I already found out tha mapped drives aren't supported

b) What user context is the component running under?

As I know components are running under IIS always under the user
"IUSR_XXX" (XXX = machine name), this is a locale user so I set access
rights of files on network so that "Everyone" can read them.

"Everyone" on server B only includes users who are valid on server B. Local
users on Server A are not valid on Server B (so they are not in the
"everyone" group on server B). The only ways to make it work is to either:
a) create a user on Server B called IUSR_ServerA, and give it the same
password as IUSR_ServerA on Server A (additionally, you will need to still
allow NTLM or LanMan access - Kerberos won't allow this type of
authentication)
-or-
b) (not 100% sure this will work) include the "anonymous" access token in
the "everyone" group on server B (NOT RECOMMENDED, since this means that any
anonymous access / null session can connect).

Cheers
Ken

[Ken Schaefer]

"Markus Weber (Megalith GmbH)" <m.*****@megalith-software.de> wrote in
message news:41****************@msnews.microsoft.com...

a) Are you using a UNC path?

Yes, I already found out tha mapped drives aren't supported

b) What user context is the component running under?

As I know components are running under IIS always under the user
"IUSR_XXX" (XXX = machine name), this is a locale user so I set access
rights of files on network so that "Everyone" can read them.

Sorry, should have added:

c) Do what Bob Barrows has suggested - use a domain account (if both
machines are in a domain)

Cheers
Ken

[Markus Weber]

>>> a) Are you using a UNC path?

Yes, I already found out tha mapped drives aren't supported

b) What user context is the component running under?

As I know components are running under IIS always under the user
"IUSR_XXX" (XXX = machine name), this is a locale user so I set access
rights of files on network so that "Everyone" can read them.

But IUSR is a local account and will not be in the network server's Everyone
group.

You need to force ASP to run under a network account which has permissions
to te network resources needed. This can be done in the Directory Security
tab in IIS Manager.

Thanks alot Bob, this solves the problem! I always thought that
"Everyone" means really everyone, all domain users as well as all
other users such as locole one.

[Markus Weber]

>> >a) Are you using a UNC path?

Yes, I already found out tha mapped drives aren't supported

b) What user context is the component running under?

As I know components are running under IIS always under the user
"IUSR_XXX" (XXX = machine name), this is a locale user so I set access
rights of files on network so that "Everyone" can read them.

Sorry, should have added:

c) Do what Bob Barrows has suggested - use a domain account (if both
machines are in a domain)

Thnaks alot, I solved th problem with Bobs tip.