Remote Debugging Issue

I'm writing an ASP.NET app, using Visual Studio 2003. VS is running locally on my laptop, but the web app is running on a remote server. My laptop is not in the domain. I do have a domain account. I had no issue creating the web app on the remote server after authenticating with the domain account, but I can't debug. It complains that I don't have rights. My domain account is in the administrators group on the remote machine. I also have a drive mapped to the remote machine under the domain credentials. Obviously, I'm logged into my machine with local credentials.

Is Visual Studio trying to debug with local credentials? I'm assuming I could create the app because of the file share connection and the authentication associated with that.

How do I get this to work? Thanks.

Jerry

[bruce barker \(sqlwork.com\)]

you have to enable remote debugging on the server, open up firewall ports, and configure dcom.

http://msdn2.microsoft.com/en-us/library/bt727f1t.aspx

-- bruce (sqlwork.com)
<rl*****@newsgr oups.nospamwrot e in message news:%2******** ********@TK2MSF TNGP06.phx.gbl. ..
I'm writing an ASP.NET app, using Visual Studio 2003. VS is running locally on my laptop, but the web app is running on a remote server. My laptop is not in the domain. I do have a domain account. I had no issue creating the web app on the remote server after authenticating with the domain account, but I can't debug. It complains that I don't have rights. My domain account is in the administrators group on the remote machine. I also have a drive mapped to the remote machine under the domain credentials. Obviously, I'm logged into my machine with local credentials.

Is Visual Studio trying to debug with local credentials? I'm assuming I could create the app because of the file share connection and the authentication associated with that.

How do I get this to work? Thanks.

Jerry

[Steven Cheng[MSFT]]

Hello Jerry,

As for the remote debugging ASP.NET issue, I think you could troubleshoot
through the following steps:

1. Ensure the required component has been installed correctly and machine's
network connection is ok. ASP.NET remote debugging in VS IDE require the
remote machine(host the ASP.NET application) has remote debugging component
installed. You can follow the below msdn referece on prepare remote ASP.NET
debugging:

#How to: Debug Web Applications on a Remote Server
http://msdn2.microsoft.com/en-us/library/233w9kd4.aspx

2. Make sure you can connect and open the web project correct from the
develop machine(with VS 2003 installed). and can run the applications
correctly.

3. After we exclude environment and component setup issue, we need to check
permission issue. since ASP.NET application will run under a service
account( machine\ASPNET for IIS5 and Networkservice for IIS6), when we
debugging the appliation from another logon user, you need to grant the
user account Administrative permission on the remote machine.

For your scenario, the remote machine is in a domain and your development
machine is not in the same domain, you can consider the following means:

**Create a duplicate local account (with the same username and password) on
both development machine and the host machine. And grant this account
administrative permission on the remote host machine.

** logon with the new created account on development machine and start VS
IDE to perform remote debugging against the remote ASP.NET application.

Hope this helps.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

=============== =============== =============== =====

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.

=============== =============== =============== =====

This posting is provided "AS IS" with no warranties, and confers no rights.

This seems to be focused on VS 2005. I'm using 2003 on XP SP2. And the server is running Windows 2000.
"bruce barker (sqlwork.com)" <b_************ *************@s qlwork.comwrote in message news:Ou******** ******@TK2MSFTN GP03.phx.gbl...
you have to enable remote debugging on the server, open up firewall ports, and configure dcom.

http://msdn2.microsoft.com/en-us/library/bt727f1t.aspx

-- bruce (sqlwork.com)
<rl*****@newsgr oups.nospamwrot e in message news:%2******** ********@TK2MSF TNGP06.phx.gbl. ..
I'm writing an ASP.NET app, using Visual Studio 2003. VS is running locally on my laptop, but the web app is running on a remote server. My laptop is not in the domain. I do have a domain account. I had no issue creating the web app on the remote server after authenticating with the domain account, but I can't debug. It complains that I don't have rights. My domain account is in the administrators group on the remote machine. I also have a drive mapped to the remote machine under the domain credentials. Obviously, I'm logged into my machine with local credentials.

Is Visual Studio trying to debug with local credentials? I'm assuming I could create the app because of the file share connection and the authentication associated with that.

How do I get this to work? Thanks.

Jerry

[Steven Cheng[MSFT]]

Hello Jerry,

As for the remote debugging setup requirement, it appiled to both VS 2003
and VS 2005 as mentioend in the reference I mentioned previously. here is a
further article which contains some other information specific to remote
debugging ASP application on remote machine(vs 2003).

#ASP Remote Debugging Setup
http://msdn.microsoft.com/library/en...emotedebugging
setup.asp?frame =true

Also, have you tried the security specific suggestion (create a duplicated
local account on both machine) to see whether it works? This is important
for security related issue when debugging against remote machine (need a
adminstrative account on remote machine).

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.

I did try everything that was suggested. Even a duplicate account. But I
still can't get anything to debug remotely.naythi nt o debug remotely. It's
a bit frustrating. Seems pretty straight foraward. I have an
administrative account. And that account is in the admins groups as well as
the debuggers group. But it staill says I don't have rights to degbug. I
did notice that the application name was blank in IIS, but when I gave it a
name, it didn't make any difference.

Kinda frustrating. I've been able to do this without a problem at other
clients. Just can't get it to function here. Thanks.

Jerry
"Steven Cheng[MSFT]" <st*****@online .microsoft.comw rote in message
news:sL******** *****@TK2MSFTNG XA01.phx.gbl...

Hello Jerry,

As for the remote debugging setup requirement, it appiled to both VS 2003
and VS 2005 as mentioend in the reference I mentioned previously. here is
a
further article which contains some other information specific to remote
debugging ASP application on remote machine(vs 2003).

#ASP Remote Debugging Setup
http://msdn.microsoft.com/library/en...emotedebugging
setup.asp?frame =true

Also, have you tried the security specific suggestion (create a duplicated
local account on both machine) to see whether it works? This is important
for security related issue when debugging against remote machine (need a
adminstrative account on remote machine).

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no
rights.

[Steven Cheng[MSFT]]

Thanks for your reply Jerry,

I'm sorry to hear that the problem remains.

Since you said the web application is created successfully and only at
debugging time it report the error, seems still related to permission issue
of the current account running vs IDE.

I've tried using a duplicated mapping local account on my local environment
and can successfully debugging an ASP.NET 1.1 web application remotly. My
test environment are two windows 2003 server machines(one host ASP.NET
application in IIS, both of them has VS 2003 installed)

Here is the steps I create the duplicated mapping acounts:

1. On host machine, create the account and then add it into
"Administrators " and "Debugger users" group.

2. On development machine(with VS 2003 installed), create the account (with
same username and password), and then add it into "Vs Developers" and
"Debugger users" group (any other powerful groups -- optional).

After that, you can try using the new account to logon (or runas the VS
2003 IDE under this account). And create web application remotly and debug
it.

BTW, if you make the changes on an existing account, you need to make it
logoff and relogon to have the changes take effect.

Please feel free to let me know if there is any other information you
wonder or we can help.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.

[Steven Cheng[MSFT]]

Hi Jerry,

Any progress on this issue? Please feel free to let me know if there is
anything we can help on ourside or any other information you wonder.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.