ts as it doesn’t recognise the PDB’s.
>
>
>
> -
> Michael Lyons
>
>
>
> *From:* ozdotnet-boun...@ozdotnet.com [mailto:
> ozdotnet-boun...@ozdotnet.com] *On Behalf Of *mike smith
> *Sent:* Monday, 9 August 2010 1:26 PM
> *To:* ozDotNet
> *Subject:* Re: R
otnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Michael Lyons
Sent: Sunday, August 08, 2010 8:19 PM
To: 'ozDotNet'
Subject: RE: Remote debugging outside of domain
I have to say it would be really nice if it just worked similar to what you
were saying b
, 9 August 2010 1:26 PM
To: ozDotNet
Subject: Re: Remote debugging outside of domain
It's probably bad security, (but if you're inside a LAN or connecting via VPN
or SSH it likely doesn't matter) but have you tried going to the options dialog
(inside remote debugger stub) and tick
It's probably bad security, (but if you're inside a LAN or connecting via
VPN or SSH it likely doesn't matter) but have you tried going to the options
dialog (inside remote debugger stub) and tick allow any user to debug?
On 8 August 2010 20:02, Michael Lyons wrote:
> I'm needing to debug a Wind
[mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of Wallace Turner
Sent: Monday, 9 August 2010 11:52 AM
To: 'ozDotNet'
Subject: RE: Remote debugging outside of domain
Condolences++
Why do you make it so damn hard to debug a process on a remote machine
(listen up Microsoft)
As always, I&#x
and find the answer with some guess work.
-
Michael Lyons
-Original Message-
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of Maddin, Peter
Sent: Monday, 9 August 2010 11:25 AM
To: ozDotNet
Subject: RE: Remote debugging outside of doma
chine (yes
that would require some work)
-Original Message-
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of Greg Keogh
Sent: Monday, 9 August 2010 11:47 AM
To: 'ozDotNet'
Subject: RE: Remote debugging outside of domain
"Unable to connec
"Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor
names 'x'. The Visual Studio Remote Debugger on the target computer cannot
connect back to this computer. Authentication failed. Please see Help for
assistance."
Hi Michael, my condolences. I spent many solid hours of suffe
If I was in this position, I would install VS on a notebook (if you don't have
one spare, they are pretty cheap these days) and place it in the same network
environment as your server.
I would then use remote debugging to discover the issue and if necessary nuke
the notebook afterwards.
>From
gging outside of domain
Windows (or any other) firewall maybe?
David
"If we can hit that bullseye, the rest of the dominoes
will fall like a house of cards... checkmate!"
-Zapp Brannigan, Futurama
On Mon, Aug 9, 2010 at 10:50, Michael Lyons wrote:
> S close. I can see that it lo
VS on the machine itself and worry about
licensing issues.
-
Michael Lyons
-Original Message-
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of Wallace Turner
Sent: Monday, 9 August 2010 10:18 AM
To: 'ozDotNet'
Subject: RE: Remote
Windows (or any other) firewall maybe?
David
"If we can hit that bullseye, the rest of the dominoes
will fall like a house of cards... checkmate!"
-Zapp Brannigan, Futurama
On Mon, Aug 9, 2010 at 10:50, Michael Lyons wrote:
> S close. I can see that it logged on the remote host with the
ay
be getting confused by the domain but to no avail.
-
Michael Lyons
-Original Message-
From: Ken Schaefer [mailto:k...@adopenstatic.com]
Sent: Monday, 9 August 2010 9:13 AM
To: Michael Lyons
Subject: RE: Remote debugging outside of domain
Can you create a local user on th
Lyons
Sent: Monday, 9 August 2010 9:12 AM
To: ozdotnet@ozdotnet.com
Subject: RE: Remote debugging outside of domain
No luck. Same result.
Liked the idea though.
I also made sure that the user was in the VS remote debugger permissions and
they had debugging permissions under the local securit
]
Sent: Sunday, 8 August 2010 9:50 PM
To: Michael Lyons
Subject: RE: Remote debugging outside of domain
One option to try:
Connect to shared folder on the remote machine first (e.g. c$ admin share)
using Explorer
Then VS. NET might use your established credentials to attempt to connect to
the remote
me
though if I am wrong.
-
Michael Lyons
-Original Message-
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of David Richards
Sent: Monday, 9 August 2010 8:03 AM
To: ozDotNet
Subject: Re: Remote debugging
Have you tried logging on with credentials from the remote computer?
ie, create a local "testuser" account on the remote server and log on
with "remoteserver\testuser".
Is the trace option turned off in the app.config?
David
"If we can hit that bullseye, the rest of the dominoes
will fall like a
I'm needing to debug a Windows service to see why it is crashing after a few
minutes.
I've setup the remote debugger on the host machine, but I receive the error
message "Unable to connect to the Microsoft Visual Studio Remote Debugging
Monitor named 'x'. Logon Failure: unknown username or bad pass
18 matches
Mail list logo
