Accessing network share - win serv. 2003 - IIS 6

[Adam McCormack]

Good morning, I hope I'm not repeating a post, but I did try to search for the topic before asking.

I am trying to resolve an issue that has come up as a result of planned migration from a single server solution to a distributed solution. A site (and interrelated batch processing scripts) has been running on a single server (IIS 6, win 2003) to two machines both are IIS 6, win 2003, the machines are as follows:

box1: Webserver
box2: MySQL & Files

scripts on box 1 need access to either a mapped drive and or a fully specified path (ie \\box2\intf or \\box2\d$)

I do not have control to set up the box myself (ahh the joys of the corporate world) so I need to be able to tell the admin team exactly what I need. I believe the following is correct:

1) Set up a Domain account for IIS to run under instead of the box1 local account
2) set IIS to use the above mentioned account on box1
3) grant full access to the needed directories on box2 to the domain account.

Impersonation should not be an issue since it is by default turned off and I have not ASP or ASP.NET on the box to turn it on in the config files.

I am already successfully accessing the MySQL data.

I believe that that should take care of everything, does it sound correct?

the following two lines are how we are accessing the files currently, and we would prefer to be able to use the files the same way if possible so as to avoid having to do more code tweaking than we currently have before us.

open(OUTFILE, '>' . $path . $seed_file) or die "Can't open output file. $@\n";
printf OUTFILE "$user_id,$dts\n";

Thanks!

[miller]

Greetings and welcome Adam,

If you are able to map a drive, then the change should be completely invisible to perl. I'm personally not familiar with the sysadm level issues that you're talking about though, so I'll see about bringing some additional attention to your question.

- Miller

[MMcCarthy]

Greetings and welcome Adam,

If you are able to map a drive, then the change should be completely invisible to perl. I'm personally not familiar with the sysadm level issues that you're talking about though, so I'll see about bringing some additional attention to your question.

- Miller

I'm going to move this to the IIS Forum. It can be redirected from there if necessary.

Adam if your question is not handled and you need assistance then you can post a reply here to get my attention.

ADMIN

[kenobewan]

In my opinion the IIS part of your migration looks. Anyone disagree? After that try and report on results. HTH.

[Adam McCormack]

To miller:

that was my expectation, that simply mapping a drive for the account that IIS runs as would take care of it, but the admin I have been working with on this claims it cant be done because the account is "non interactive" I believe is how he phrased it.

To mmccarthy & kenobewan:
Ill post the resolution as soon as I have it, I am now working with a different admin, so the responses I have previously received may be invalid, and while it has not been done yet, I think my 3 step list is going to be very close to what works.

Thanks again for the quick replies, and I apologize for placing it in the perl forum, I certainly agree it fits in IIS as I have looked at it more.

[Adam McCormack]

And the issue is now resolved.

the three steps I stated when I posted innitally:
1) Set up a Domain account for IIS to run under instead of the box1 local account
2) set IIS to use the above mentioned account on box1
3) grant full access to the needed directories on box2 to the domain account.

did the trick, with the second step specifying:
- the web site properties in the IIS manager
- under the directory security tab,
- Enable anonymous access using the domain account and password.

Thanks again for the help!

[MMcCarthy]

Happy to hear that you got it sorted Adam.

Mary