head scratcher...

[Robert Megee]

My development platform is a widows2000 pro. I built a web app that
takes a file name and opens a file from an nfs mounted directory. The
files reside on a unix based server.
This works fine.
When I try to run this on my windows2003 server, it can't see the nfs
mounted directory.
When I check the windows identy on the 2000 machine, it says
compname\aspnet. On the 2003 machine, it says something like
NT AUTHORITY\NETWORK.
In the win.config file I turned on inpersonation and set it to
MYDOMAIN\MYUSER. Where MYUSER is the account (that has admin
privileges) that did the nfs mount. But this didn't make any
difference.
I tried this with a normal windows shared directory and got the same
results.
So any clues as to how I can make this work?

Thanks,

Robert

[Landi]

Actually when your web app runs it will run under ASPNET account so that's
the account that you need to give rights to for your web app to see
anything. Under 2000 server the rights are more relaxed, 2003 is more
secure when it comes to running these apps. Also look at the settings for
IUSR_MACHINENAME and give that account proper rights.

--
in**@dowhileloop.com
http://dowhileloop.com website development
http://publicjoe.dowhileloop.com -- C# Tutorials

"Robert Megee" <rm*****@comcast.net> wrote in message
news:hl********************************@4ax.com...

My development platform is a widows2000 pro. I built a web app that
takes a file name and opens a file from an nfs mounted directory. The
files reside on a unix based server.
This works fine.
When I try to run this on my windows2003 server, it can't see the nfs
mounted directory.
When I check the windows identy on the 2000 machine, it says
compname\aspnet. On the 2003 machine, it says something like
NT AUTHORITY\NETWORK.
In the win.config file I turned on inpersonation and set it to
MYDOMAIN\MYUSER. Where MYUSER is the account (that has admin
privileges) that did the nfs mount. But this didn't make any
difference.
I tried this with a normal windows shared directory and got the same
results.
So any clues as to how I can make this work?

Thanks,

Robert

[Landi]

Actually when your web app runs it will run under ASPNET account so that's
the account that you need to give rights to for your web app to see
anything. Under 2000 server the rights are more relaxed, 2003 is more
secure when it comes to running these apps. Also look at the settings for
IUSR_MACHINENAME and give that account proper rights.

--
in**@dowhileloop.com
http://dowhileloop.com website development
http://publicjoe.dowhileloop.com -- C# Tutorials

"Robert Megee" <rm*****@comcast.net> wrote in message
news:hl********************************@4ax.com...

My development platform is a widows2000 pro. I built a web app that
takes a file name and opens a file from an nfs mounted directory. The
files reside on a unix based server.
This works fine.
When I try to run this on my windows2003 server, it can't see the nfs
mounted directory.
When I check the windows identy on the 2000 machine, it says
compname\aspnet. On the 2003 machine, it says something like
NT AUTHORITY\NETWORK.
In the win.config file I turned on inpersonation and set it to
MYDOMAIN\MYUSER. Where MYUSER is the account (that has admin
privileges) that did the nfs mount. But this didn't make any
difference.
I tried this with a normal windows shared directory and got the same
results.
So any clues as to how I can make this work?

Thanks,

Robert

[Robert Megee]

I actually made those users admin's on the machine and it still didn't
work. I removed the Adhanced Internet Security, which supposedly
makes the web browser have the same security level as 2000, but that
too didn't help.
On Fri, 25 Mar 2005 22:13:54 -0500, "Landi" <in**@dowhileloop.com>
wrote:

Actually when your web app runs it will run under ASPNET account so that's
the account that you need to give rights to for your web app to see
anything. Under 2000 server the rights are more relaxed, 2003 is more
secure when it comes to running these apps. Also look at the settings for
IUSR_MACHINENAME and give that account proper rights.

[Robert Megee]

I actually made those users admin's on the machine and it still didn't
work. I removed the Adhanced Internet Security, which supposedly
makes the web browser have the same security level as 2000, but that
too didn't help.
On Fri, 25 Mar 2005 22:13:54 -0500, "Landi" <in**@dowhileloop.com>
wrote:

Actually when your web app runs it will run under ASPNET account so that's
the account that you need to give rights to for your web app to see
anything. Under 2000 server the rights are more relaxed, 2003 is more
secure when it comes to running these apps. Also look at the settings for
IUSR_MACHINENAME and give that account proper rights.

[Victor M. Font Jr.]

You may want to check out this knowledge base article. IIS under Windows
2003 converts file paths to uppercase before it calls CreateFileW. Your
problem could be related to Unix's case sensitivity.
http://support.microsoft.com/default...b;en-us;324232
"Robert Megee" <rm*****@comcast.net> wrote in message
news:hl********************************@4ax.com...

My development platform is a widows2000 pro. I built a web app that
takes a file name and opens a file from an nfs mounted directory. The
files reside on a unix based server.
This works fine.
When I try to run this on my windows2003 server, it can't see the nfs
mounted directory.
When I check the windows identy on the 2000 machine, it says
compname\aspnet. On the 2003 machine, it says something like
NT AUTHORITY\NETWORK.
In the win.config file I turned on inpersonation and set it to
MYDOMAIN\MYUSER. Where MYUSER is the account (that has admin
privileges) that did the nfs mount. But this didn't make any
difference.
I tried this with a normal windows shared directory and got the same
results.
So any clues as to how I can make this work?

Thanks,

Robert

[Victor M. Font Jr.]

You may want to check out this knowledge base article. IIS under Windows
2003 converts file paths to uppercase before it calls CreateFileW. Your
problem could be related to Unix's case sensitivity.
http://support.microsoft.com/default...b;en-us;324232
"Robert Megee" <rm*****@comcast.net> wrote in message
news:hl********************************@4ax.com...

My development platform is a widows2000 pro. I built a web app that
takes a file name and opens a file from an nfs mounted directory. The
files reside on a unix based server.
This works fine.
When I try to run this on my windows2003 server, it can't see the nfs
mounted directory.
When I check the windows identy on the 2000 machine, it says
compname\aspnet. On the 2003 machine, it says something like
NT AUTHORITY\NETWORK.
In the win.config file I turned on inpersonation and set it to
MYDOMAIN\MYUSER. Where MYUSER is the account (that has admin
privileges) that did the nfs mount. But this didn't make any
difference.
I tried this with a normal windows shared directory and got the same
results.
So any clues as to how I can make this work?

Thanks,

Robert

[Robert Megee]

I'll check it out.

Thanks,

Robert
On Sat, 26 Mar 2005 06:19:40 -0500, "Victor M. Font Jr."
<vi*****@optonline.net> wrote:

You may want to check out this knowledge base article. IIS under Windows
2003 converts file paths to uppercase before it calls CreateFileW. Your
problem could be related to Unix's case sensitivity.
http://support.microsoft.com/default...b;en-us;324232
"Robert Megee" <rm*****@comcast.net> wrote in message
news:hl********************************@4ax.com.. .

My development platform is a widows2000 pro. I built a web app that
takes a file name and opens a file from an nfs mounted directory. The
files reside on a unix based server.
This works fine.
When I try to run this on my windows2003 server, it can't see the nfs
mounted directory.
When I check the windows identy on the 2000 machine, it says
compname\aspnet. On the 2003 machine, it says something like
NT AUTHORITY\NETWORK.
In the win.config file I turned on inpersonation and set it to
MYDOMAIN\MYUSER. Where MYUSER is the account (that has admin
privileges) that did the nfs mount. But this didn't make any
difference.
I tried this with a normal windows shared directory and got the same
results.
So any clues as to how I can make this work?

Thanks,

Robert

[Robert Megee]

I'll check it out.

Thanks,

Robert
On Sat, 26 Mar 2005 06:19:40 -0500, "Victor M. Font Jr."
<vi*****@optonline.net> wrote:

You may want to check out this knowledge base article. IIS under Windows
2003 converts file paths to uppercase before it calls CreateFileW. Your
problem could be related to Unix's case sensitivity.
http://support.microsoft.com/default...b;en-us;324232
"Robert Megee" <rm*****@comcast.net> wrote in message
news:hl********************************@4ax.com.. .

My development platform is a widows2000 pro. I built a web app that
takes a file name and opens a file from an nfs mounted directory. The
files reside on a unix based server.
This works fine.
When I try to run this on my windows2003 server, it can't see the nfs
mounted directory.
When I check the windows identy on the 2000 machine, it says
compname\aspnet. On the 2003 machine, it says something like
NT AUTHORITY\NETWORK.
In the win.config file I turned on inpersonation and set it to
MYDOMAIN\MYUSER. Where MYUSER is the account (that has admin
privileges) that did the nfs mount. But this didn't make any
difference.
I tried this with a normal windows shared directory and got the same
results.
So any clues as to how I can make this work?

Thanks,

Robert

[Robert Megee]

For those that may be following this thread, I found this in
microsoft's knowledgebase:
http://support.microsoft.com/default...b;en-us;827421

It explains how to solve this problem. I'll try it tomorrow and post
my results.

Robert
On Fri, 25 Mar 2005 18:00:22 -0600, Robert Megee <rm*****@comcast.net>
wrote:

My development platform is a widows2000 pro. I built a web app that
takes a file name and opens a file from an nfs mounted directory. The
files reside on a unix based server.
This works fine.
When I try to run this on my windows2003 server, it can't see the nfs
mounted directory.
When I check the windows identy on the 2000 machine, it says
compname\aspnet. On the 2003 machine, it says something like
NT AUTHORITY\NETWORK.
In the win.config file I turned on inpersonation and set it to
MYDOMAIN\MYUSER. Where MYUSER is the account (that has admin
privileges) that did the nfs mount. But this didn't make any
difference.
I tried this with a normal windows shared directory and got the same
results.
So any clues as to how I can make this work?

Thanks,

Robert

[Robert Megee]

The work-around worked. It took a little experimentation to fill in
some of the blanks but it allowed me to open files contained in a
mounted directory.

Robert
On Sun, 27 Mar 2005 16:02:48 -0600, Robert Megee <rm*****@comcast.net>
wrote:

For those that may be following this thread, I found this in
microsoft's knowledgebase:
http://support.microsoft.com/default...b;en-us;827421

It explains how to solve this problem. I'll try it tomorrow and post
my results.

Robert
On Fri, 25 Mar 2005 18:00:22 -0600, Robert Megee <rm*****@comcast.net>
wrote:

My development platform is a widows2000 pro. I built a web app that
takes a file name and opens a file from an nfs mounted directory. The
files reside on a unix based server.
This works fine.
When I try to run this on my windows2003 server, it can't see the nfs
mounted directory.
When I check the windows identy on the 2000 machine, it says
compname\aspnet. On the 2003 machine, it says something like
NT AUTHORITY\NETWORK.
In the win.config file I turned on inpersonation and set it to
MYDOMAIN\MYUSER. Where MYUSER is the account (that has admin
privileges) that did the nfs mount. But this didn't make any
difference.
I tried this with a normal windows shared directory and got the same
results.
So any clues as to how I can make this work?

Thanks,

Robert