Virtual Directory On UNC Share Not Writable

am 25.07.2006 20:55:52 von toniintc

Hi all,

I have an ASP page on a Win2003 IIS6 server attempting to write a
text file via a virtual directory setup to point to a UNC share on
another Win2003 server. When the code attempts to create the text
file, I get a 8007052e error - bad username or password essentially.
Both servers are in the same domain, and I'm using a user in the domain
with admin privileges for both the virtual directories Connect As
credentials and the anonymous access Directory Security credentials
(and Integrated Windows Auth is not checked). The share itself has
full perms granted to Everyone. The NTFS perms are also set for full
access by Everyone right now.
This started happening when I moved the website itself to an IIS6
Win2003 server from an IIS5 Win2000 server. It worked fine for a
couple years on the IIS5 server. If I point DNS for the site back to
the old Win2000 server with the virtual directory setup exactly the
same, it still works.
In an effort to troubleshoot, I pointed the virtual directory to a
Linux box running Samba so I could view Samba's logs in real time to
see if the share is accessed. I get the same error. When I created
the virtual directory or accessed it manually from within the IIS
snap-in, Samba writes the corresponding access to its log files.
However, when I run the script, Samba doesn't write anything. So, this
tells me it doesn't seem as if the share isn't even accessed, as if
there's something more basic happening.
The extremely simple code being used to test is below for reference
(the error occurs in the third line). Can anyone point me in the
correct direction?

Thanks!
Toni

<%
vendor_orders_dir = server.mappath("/vendor_orders")
Set XMLFSO = CreateObject("Scripting.FileSystemObject")
Set XMLFile = XMLFSO.CreateTextFile(vendor_orders_dir & "\test.xml",
True)
XMLFile.WriteLine("testing")

Re: Virtual Directory On UNC Share Not Writable

am 25.07.2006 21:20:13 von someone

The problem seems to be with your server's configuration. I think it
haphazardly worked earlier due to now invalid assumptions. We just have to
figure out where it is breaking down now.

Can you make sure to write the file correctly by closing with:
XMLFile.Close()

Use "On Error Resume Next" error handling in VB to recover and report the
error.

Since you are using Domains, can you make sure that you do not have domain
Group Policy that somehow restricts the authenticated user from logging
onto either system.

"Connect As" and Anonymous Authentication are two different things. IIS6 is
far better than IIS5 at correctly supporting the UNC behaviors you want --
see:
http://www.microsoft.com/technet/prodtechnol/windowsserver20 03/technologies/webapp/iis/remstorg.mspx

To diagnose on the UNC share - run FileMon (www.sysinternals.com) on the
server hosting the UNC share, and you should see what user tries to access
what file/directory... assuming the UNC request made it to the UNC server.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//

wrote in message
news:1153853751.906064.307370@b28g2000cwb.googlegroups.com.. .
> Hi all,
>
> I have an ASP page on a Win2003 IIS6 server attempting to write a
> text file via a virtual directory setup to point to a UNC share on
> another Win2003 server. When the code attempts to create the text
> file, I get a 8007052e error - bad username or password essentially.
> Both servers are in the same domain, and I'm using a user in the domain
> with admin privileges for both the virtual directories Connect As
> credentials and the anonymous access Directory Security credentials
> (and Integrated Windows Auth is not checked). The share itself has
> full perms granted to Everyone. The NTFS perms are also set for full
> access by Everyone right now.
> This started happening when I moved the website itself to an IIS6
> Win2003 server from an IIS5 Win2000 server. It worked fine for a
> couple years on the IIS5 server. If I point DNS for the site back to
> the old Win2000 server with the virtual directory setup exactly the
> same, it still works.
> In an effort to troubleshoot, I pointed the virtual directory to a
> Linux box running Samba so I could view Samba's logs in real time to
> see if the share is accessed. I get the same error. When I created
> the virtual directory or accessed it manually from within the IIS
> snap-in, Samba writes the corresponding access to its log files.
> However, when I run the script, Samba doesn't write anything. So, this
> tells me it doesn't seem as if the share isn't even accessed, as if
> there's something more basic happening.
> The extremely simple code being used to test is below for reference
> (the error occurs in the third line). Can anyone point me in the
> correct direction?
>
> Thanks!
> Toni
>
>
> <%
> vendor_orders_dir = server.mappath("/vendor_orders")
> Set XMLFSO = CreateObject("Scripting.FileSystemObject")
> Set XMLFile = XMLFSO.CreateTextFile(vendor_orders_dir & "\test.xml",
> True)
> XMLFile.WriteLine("testing")
>

Re: Virtual Directory On UNC Share Not Writable

am 25.07.2006 21:20:13 von someone

Re: Virtual Directory On UNC Share Not Writable

am 25.07.2006 23:14:28 von toniintc

Thanks for the response. I did in fact have the file closing in the
ASP code - I only posted a few lines for brevity. The full code is
below. If I add an On Error Resume Next, the page of course does not
throw an error, but neither is the file created. No applicable domain
group policy exists. Running filemon shows no attempt at an access to
the file. Interestingly however, if I allow Directory Browsing on the
virtual directory, and browse the files from a browser, it works just
fine (and I do see this access in filemon). However, if I change the
code to open a text file for reading that I put in the virtual
directory, I get the same error on the OpenTextFile line.

The link you provided was interesting. I enabled the delegation trust
to no avail.

Thanks,
Toni

<%

vendor_orders_dir = server.mappath("/vendor_orders")

' Setup object for file write.
Set XMLFSO = CreateObject("Scripting.FileSystemObject")
'Set XMLFile = XMLFSO.CreateTextFile("z:\test.xml", True)
Set XMLFile = XMLFSO.CreateTextFile(vendor_orders_dir & "\test.xml",
True)

' Write XML to file.
XMLFile.WriteLine("testing")

' Close file.
XMLFile.Close

' Null out the objects.
SET XMLFile = NOTHING
SET XMLFSO = NOTHING

%>

David Wang [Msft] wrote:
> The problem seems to be with your server's configuration. I think it
> haphazardly worked earlier due to now invalid assumptions. We just have to
> figure out where it is breaking down now.
>
> Can you make sure to write the file correctly by closing with:
> XMLFile.Close()
>
> Use "On Error Resume Next" error handling in VB to recover and report the
> error.
>
> Since you are using Domains, can you make sure that you do not have domain
> Group Policy that somehow restricts the authenticated user from logging
> onto either system.
>
> "Connect As" and Anonymous Authentication are two different things. IIS6 is
> far better than IIS5 at correctly supporting the UNC behaviors you want --
> see:
> http://www.microsoft.com/technet/prodtechnol/windowsserver20 03/technologies/webapp/iis/remstorg.mspx
>
> To diagnose on the UNC share - run FileMon (www.sysinternals.com) on the
> server hosting the UNC share, and you should see what user tries to access
> what file/directory... assuming the UNC request made it to the UNC server.
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
>
> wrote in message
> news:1153853751.906064.307370@b28g2000cwb.googlegroups.com.. .
> > Hi all,
> >
> > I have an ASP page on a Win2003 IIS6 server attempting to write a
> > text file via a virtual directory setup to point to a UNC share on
> > another Win2003 server. When the code attempts to create the text
> > file, I get a 8007052e error - bad username or password essentially.
> > Both servers are in the same domain, and I'm using a user in the domain
> > with admin privileges for both the virtual directories Connect As
> > credentials and the anonymous access Directory Security credentials
> > (and Integrated Windows Auth is not checked). The share itself has
> > full perms granted to Everyone. The NTFS perms are also set for full
> > access by Everyone right now.
> > This started happening when I moved the website itself to an IIS6
> > Win2003 server from an IIS5 Win2000 server. It worked fine for a
> > couple years on the IIS5 server. If I point DNS for the site back to
> > the old Win2000 server with the virtual directory setup exactly the
> > same, it still works.
> > In an effort to troubleshoot, I pointed the virtual directory to a
> > Linux box running Samba so I could view Samba's logs in real time to
> > see if the share is accessed. I get the same error. When I created
> > the virtual directory or accessed it manually from within the IIS
> > snap-in, Samba writes the corresponding access to its log files.
> > However, when I run the script, Samba doesn't write anything. So, this
> > tells me it doesn't seem as if the share isn't even accessed, as if
> > there's something more basic happening.
> > The extremely simple code being used to test is below for reference
> > (the error occurs in the third line). Can anyone point me in the
> > correct direction?
> >
> > Thanks!
> > Toni
> >
> >
> > <%
> > vendor_orders_dir = server.mappath("/vendor_orders")
> > Set XMLFSO = CreateObject("Scripting.FileSystemObject")
> > Set XMLFile = XMLFSO.CreateTextFile(vendor_orders_dir & "\test.xml",
> > True)
> > XMLFile.WriteLine("testing")
> >

Re: Virtual Directory On UNC Share Not Writable

am 25.07.2006 23:14:28 von toniintc

Re: Virtual Directory On UNC Share Not Writable

am 26.07.2006 06:48:46 von someone

I do not believe the problem is with IIS but rather something else specific
on your server. Are you running Personal Security software that prevents
various objects from working?

Reason I say this is because I have a very simple ASP application which
allows HTTP-based file management of the server - so I can set it up to
upload/download/delete files as well as dir-browse the configurable
directory root on the server - and I know it works on IIS6 with UNC. All I
did is use default configuration, set the Anonymous user to be the same user
allowed read/write access across the UNC on the UNC server, and then
configured my app to write across the UNC share, and it simply works.

So, I suggest paying attention to whatever is breaking that behavior on your
server. My machines are stand-alone so I know that they are pure default
configuration. The usual culprit is Group Policy, and since your machines
are in a domain as well as potentially running other security software,
that's where I would look. I'm simply saying that absent Group Policy and
security software, what you are trying to do simply works by default as it
should.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//

wrote in message
news:1153862067.975348.94860@m79g2000cwm.googlegroups.com...
> Thanks for the response. I did in fact have the file closing in the
> ASP code - I only posted a few lines for brevity. The full code is
> below. If I add an On Error Resume Next, the page of course does not
> throw an error, but neither is the file created. No applicable domain
> group policy exists. Running filemon shows no attempt at an access to
> the file. Interestingly however, if I allow Directory Browsing on the
> virtual directory, and browse the files from a browser, it works just
> fine (and I do see this access in filemon). However, if I change the
> code to open a text file for reading that I put in the virtual
> directory, I get the same error on the OpenTextFile line.
>
> The link you provided was interesting. I enabled the delegation trust
> to no avail.
>
> Thanks,
> Toni
>
>
> <%
>
> vendor_orders_dir = server.mappath("/vendor_orders")
>
> ' Setup object for file write.
> Set XMLFSO = CreateObject("Scripting.FileSystemObject")
> 'Set XMLFile = XMLFSO.CreateTextFile("z:\test.xml", True)
> Set XMLFile = XMLFSO.CreateTextFile(vendor_orders_dir & "\test.xml",
> True)
>
> ' Write XML to file.
> XMLFile.WriteLine("testing")
>
> ' Close file.
> XMLFile.Close
>
> ' Null out the objects.
> SET XMLFile = NOTHING
> SET XMLFSO = NOTHING
>
> %>
>
>
> David Wang [Msft] wrote:
>> The problem seems to be with your server's configuration. I think it
>> haphazardly worked earlier due to now invalid assumptions. We just have
>> to
>> figure out where it is breaking down now.
>>
>> Can you make sure to write the file correctly by closing with:
>> XMLFile.Close()
>>
>> Use "On Error Resume Next" error handling in VB to recover and report the
>> error.
>>
>> Since you are using Domains, can you make sure that you do not have
>> domain
>> Group Policy that somehow restricts the authenticated user from logging
>> onto either system.
>>
>> "Connect As" and Anonymous Authentication are two different things. IIS6
>> is
>> far better than IIS5 at correctly supporting the UNC behaviors you
>> want --
>> see:
>> http://www.microsoft.com/technet/prodtechnol/windowsserver20 03/technologies/webapp/iis/remstorg.mspx
>>
>> To diagnose on the UNC share - run FileMon (www.sysinternals.com) on the
>> server hosting the UNC share, and you should see what user tries to
>> access
>> what file/directory... assuming the UNC request made it to the UNC
>> server.
>>
>> --
>> //David
>> IIS
>> http://blogs.msdn.com/David.Wang
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> //
>>
>> wrote in message
>> news:1153853751.906064.307370@b28g2000cwb.googlegroups.com.. .
>> > Hi all,
>> >
>> > I have an ASP page on a Win2003 IIS6 server attempting to write a
>> > text file via a virtual directory setup to point to a UNC share on
>> > another Win2003 server. When the code attempts to create the text
>> > file, I get a 8007052e error - bad username or password essentially.
>> > Both servers are in the same domain, and I'm using a user in the domain
>> > with admin privileges for both the virtual directories Connect As
>> > credentials and the anonymous access Directory Security credentials
>> > (and Integrated Windows Auth is not checked). The share itself has
>> > full perms granted to Everyone. The NTFS perms are also set for full
>> > access by Everyone right now.
>> > This started happening when I moved the website itself to an IIS6
>> > Win2003 server from an IIS5 Win2000 server. It worked fine for a
>> > couple years on the IIS5 server. If I point DNS for the site back to
>> > the old Win2000 server with the virtual directory setup exactly the
>> > same, it still works.
>> > In an effort to troubleshoot, I pointed the virtual directory to a
>> > Linux box running Samba so I could view Samba's logs in real time to
>> > see if the share is accessed. I get the same error. When I created
>> > the virtual directory or accessed it manually from within the IIS
>> > snap-in, Samba writes the corresponding access to its log files.
>> > However, when I run the script, Samba doesn't write anything. So, this
>> > tells me it doesn't seem as if the share isn't even accessed, as if
>> > there's something more basic happening.
>> > The extremely simple code being used to test is below for reference
>> > (the error occurs in the third line). Can anyone point me in the
>> > correct direction?
>> >
>> > Thanks!
>> > Toni
>> >
>> >
>> > <%
>> > vendor_orders_dir = server.mappath("/vendor_orders")
>> > Set XMLFSO = CreateObject("Scripting.FileSystemObject")
>> > Set XMLFile = XMLFSO.CreateTextFile(vendor_orders_dir & "\test.xml",
>> > True)
>> > XMLFile.WriteLine("testing")
>> >
>

Re: Virtual Directory On UNC Share Not Writable

am 26.07.2006 06:48:46 von someone