I once used the mmc console to connect to the computer and turn on telnet.
Another person used the UBCD and had the user copy off the files.
A couple of times I used the UBCD, it automatically picked up the ip
address. If UBCD automatically picks up the ip address, you might be
able to remote t
On 14 May 2010 at 15:54, Peter van Houten wrote:
> Due to the change of government in the UK, the crisis has been averted and I
> have the luxury of inspecting the damage myself next week. I would, however
> still like to access the system remotely and since last night have Nessus
> trying to f
From: Tammy [mailto:copper...@personainternet.com]
Sent: Thursday, May 13, 2010 10:10 PM
To: NT System Admin Issues
Subject: re: XP Box inaccessible
Can you access the machine's registry from a machine on the network using
remote registry? It has worked for me a few times. (assuming us
On Thu, May 13, 2010 at 8:25 PM, Peter van Houten wrote:
> Good idea (KVM) but even that would floor them technically!
Going forward, then, you may want to equip the system with one when
you get hands-on to fix the current problem. That will at least make
things easier in the future. There's
precise
set of instructions on your behalf? E.g. insert XP Cd, turn on desktop,
open recovery console, read registry line, fix, reboot?
Mike
-Original Message-
From: Peter van Houten [mailto:peter...@gmail.com]
Sent: 14 May 2010 13:14
To: NT System Admin Issues
Subject: Re: XP Box inaccessible
Thanks
, reboot?
Mike
-Original Message-
From: Peter van Houten [mailto:peter...@gmail.com]
Sent: 14 May 2010 13:14
To: NT System Admin Issues
Subject: Re: XP Box inaccessible
Thanks Tammy; most of my attempts at remote access were fruitless.
Besides breaking the login process, the code *seems* to ha
-freight you the box and let YOU hack it so you
don't have to get on a plane?
-Original Message-
From: Peter van Houten [mailto:peter...@gmail.com]
Sent: Friday, May 14, 2010 8:14 AM
To: NT System Admin Issues
Subject: Re: XP Box inaccessible
Thanks Tammy; most of my attempts at r
Any chance they could air-freight you the box and let YOU hack it so you
don't have to get on a plane?
-Original Message-
From: Peter van Houten [mailto:peter...@gmail.com]
Sent: Friday, May 14, 2010 8:14 AM
To: NT System Admin Issues
Subject: Re: XP Box inaccessible
Thanks
Thanks Tammy; most of my attempts at remote access were fruitless.
Besides breaking the login process, the code *seems* to have disabled
all access vectors that I know of, with the exception of IPC$ (with null
credentials only) via which I have made a connect/disconnect but nothing
more and was ho
Can you access the machine's registry from a machine on the network using
remote registry? It has worked for me a few times. (assuming userinit.exe
exists & is intact)
Worth a look to see if the userinit value in registry is hosed.
Key:
BrokenMachine\HKEY_LOCAL_MACHINE\Software\Microsoft\Window
Good idea (KVM) but even that would floor them technically! It would
probably be easier to step them through an XP CD boot in recovery mode :-)
--
Peter van Houten
On the 14 May, 2010 02:08, Ben Scott wrote the following:
On Thu, May 13, 2010 at 7:43 PM, Jon Harris wrote:
It sounds like it is
k.har...@gmail.com>]
  *Sent:* Friday, 14 May 2010 9:40 AM
  *To:* NT System Admin Issues
  *Subject:* Re: XP Box inaccessible
  What about just mapping the drive's admin share and pulling what you
  need?
  Jon
  On Thu, May 13, 2010 at 7:34 PM, Peter van Houte
iday, 14 May 2010 9:40 AM
*To:* NT System Admin Issues
*Subject:* Re: XP Box inaccessible
What about just mapping the drive's admin share and pulling
what you
need?
Jon
On Thu, May 13, 2010 at 7:34 PM, P
On Thu, May 13, 2010 at 7:43 PM, Jon Harris wrote:
> It sounds like it is time to get a ticket and pack a bag ...
Might be easier/cheaper to put the computer in a box and air freight
it to where the clue is.
Or... hmm. How about an IP KVM? Tell the remote site to "go buy
one of these", and
What can't be done / makes no difference:
>>
>> 4) Map drives to *any* shares from another box
>>
>> *From:* Jon Harris [mailto:jk.har...@gmail.com
>> <mailto:jk.har...@gmail.com>]
>> *Sent:* Friday, 14 May 2010 9:40
gt;>What can't be done / makes no difference:
>>
>>4) Map drives to *any* shares from another box
>>
>>*From:* Jon Harris [mailto:jk.har...@gmail.com
>>
>><mailto:jk.har...@gmail.com>]
>>*Sent:* Friday,
What can't be done / makes no difference:
4) Map drives to *any* shares from another box
*From:* Jon Harris [mailto:jk.har...@gmail.com
<mailto:jk.har...@gmail.com>]
*Sent:* Friday, 14 May 2010 9:40 AM
*To:* NT System Admin Issues
*Subject:* R
Heh ~ first thing I tried. See #4 below.
--
Peter van Houten
On the 14 May, 2010 01:39, Jon Harris wrote the following:
What about just mapping the drive's admin share and pulling what you need?
Jon
On Thu, May 13, 2010 at 7:34 PM, Peter van Houten mailto:peter...@gmail.com>> wrote:
Well
makes no difference:
>
>4) Map drives to *any* shares from another box
>
>
>
>
>
> *From:* Jon Harris [mailto:jk.har...@gmail.com]
> *Sent:* Friday, 14 May 2010 9:40 AM
>
> *To:* NT System Admin Issues
> *Subject:* Re: XP Box inaccessible
>
>
&
He covered that one.
What can't be done / makes no difference:
4) Map drives to *any* shares from another box
From: Jon Harris [mailto:jk.har...@gmail.com]
Sent: Friday, 14 May 2010 9:40 AM
To: NT System Admin Issues
Subject: Re: XP Box inaccessible
What about
What about just mapping the drive's admin share and pulling what you need?
Jon
On Thu, May 13, 2010 at 7:34 PM, Peter van Houten wrote:
> Well ironically, it is far from "hung" but I know what you mean. There
> are a number of bugs that have this effect; the less elaborate just
> overwrite files
Well ironically, it is far from "hung" but I know what you mean. There
are a number of bugs that have this effect; the less elaborate just
overwrite files such as userinit.exe with their own code, make a few reg
changes and cause the login problem.
Type in the login and password, off it goes..."l
So what you have is a hung box some where between logon and logoff?
Jon
On Thu, May 13, 2010 at 7:09 PM, Peter van Houten wrote:
> Thanks Jon; I probably didn't lay out my explanation properly but I do
> have remote access; it simply goes through the same login-logoff routine
> as a local login.
Thanks Jon; I probably didn't lay out my explanation properly but I do
have remote access; it simply goes through the same login-logoff routine
as a local login.
--
Peter van Houten
On the 14 May, 2010 00:58, Jon Harris wrote the following:
Isn't there a GPO that would turn on remote access for
Isn't there a GPO that would turn on remote access for Domain Admins? If it
is part of a domain and you have access to the Domain Controller then just
have it restarted once or twice and you should be good to go.
Jon
On Thu, May 13, 2010 at 6:26 PM, Peter van Houten wrote:
> I have a XP Pro [fu
logon screen.
-Original Message-
From: Peter van Houten [mailto:peter...@gmail.com]
Sent: Friday, 14 May 2010 8:27 AM
To: NT System Admin Issues
Subject: XP Box inaccessible
I have a XP Pro [fully patched :-) ] box on a network that has been infected
(probably Virut). It is the classic
I have a XP Pro [fully patched :-) ] box on a network that has been
infected (probably Virut). It is the classic login...loading your
personal settings...logging off scenario.
Recovering the data and fixing the malware problem is easy. The real
problem is that the box is 300 miles away, so I am t
27 matches
Mail list logo
