RE: debugging ASP NET in a remote web server with remote file serv

Hi Steven,

thank you for all the information, but unfortunatly I am not able to solve
the problem. I will try to give you more information.

To your first question the answer is YES, but the SRV2 is an Windows 2000
server domain controller not another Windows 2003 Server.

The first thing I did was disabling the "Network Access: Restrict anonymous
access to named pipe and shares" on the Local sercurity policy of the Windows
2003 Server (SRV1) as you told me and then I did the following tests:

1. Define the Administrator domain account in the "Connect as" button of the
Home directory in the IIS. Then I tried to debug and I got the following
message:

Error while trying to run project: unable to start debugging on the web
server. Access denied.

2. I clicked again on the "Connect as" button and activated the "Always use
the authenticated user credentials when validating access to the network" (I
have translated this text from spanish and maybe is not accurated). The
user/password boxes were grayed and I tried again to debug and this time the
explorer was opened but with a message in "Spanish" telling me that a runtime
error occurred but it couldn't be showed because of web.config errors
configuration. The web.config is ok, and works ok when not debugging in this
UNC debugging.
If I try to manually navigate the web with this opened explorer, a
user/password dialog opens but it doesn't accept any valid account.

Any idea of how can I fix this?

By the way, the UNC is shared as full control to everyone and everyone have
NTFS permissions to read and write.


"Steven Cheng[MSFT]" wrote:

> Hi Ras26,
>
> From your further description, I think you've been able to get remote
> ASP.NET debuging working (between xp sp2 and w2k3server (SRV1)). The
> problem occurs when you change the web application(virtual dir)'s locatio
> from the local disk (on SRV1) to a UNC share on another win2k3
> server(SRV2), yes?
>
> Based on my experience, this is likely a typical remote access problem.
> There're two things we can check:
>
> 1. In IIS virtual dir's Home directory setting panel, when we specify UNC
> shared path as the HOME directory, there'll occur an "Connect As" button
> right to the UNC path's textbox. That is used to specify an account to
> connect to that UNC path from your local box(where the IIS located). Have
> you configured this one? If not, I suggest you configure an powerful
> account (valid on the remote machine , the SRV2 in your condition). Thus,
> when accessing the UNC path IIS will use this account rather than access as
> network anonymous.
>
> 2. If we don't specify the "ConnectAs" account, since the IIS's use the
> account from the client, since you're remotely debuging, your account from
> the develop machine( PC1) can't be double hopped to SRV2, so the SRV1 will
> access the SRV2's UNCshare as Network Anonymous account. Yes, we can
> grant everyone Full Control for that UNCshare on SRV2, however, as for
> WIN2003 server, there is another thing restrict the anonymous user's
> access. You can find the one in the server's Local Security Policy setting:
>
> Administrative tools -----> Local security policy
>
> Then, select the " Local Policies -----> security options" node in left
> view and you'll find the
>
> "Network Access: Restrict anonymous access to named pipe and shares"
>
> by default , this is enabled, so we need to also turn off it to enable
> anonymous access.
>
> Please have a look at the above things. Hope helps.
>
> Thanks,
>
> Steven Cheng
> Microsoft Online Support
>
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
>
>
.