Archived from groups: microsoft.public.windowsxp.general (More info?)

Now I know you may think they do realize the issue because they have a
Knowledge Base article on the issue. But come'on how long has Windows XP
existed in the Market? And if you know anything about Knowledge Base
articles and statements such as this in them "Microsoft is researching this
problem and will post more information in this article when the information
becomes available," you'll know that the issue will never be addressed -
forever. Give me one example where a statement such as this in a Knowledge
Base article was EVER addressed afterwards. Just one. Here is the KB:

http://support.microsoft.com/defau [...] -us;884564

Now I can tell you the RPC error as they have written here is only half the
story. The other half they camouflage but if you read the article closely
you will see they say, "receive either of the following error messages..."
The important word here is "either." That means one or the other - maybe
both since that is not addressed. The old Aristotlean logic here.

Anyway reading further it says for cause, "because of a mismatch in the
computer name and the name that the RPC service expects." Now this
addresses one half of the Venn not the other. In fact the "either" has been
completely ignored. The cause addresses the RPC half of the either NOT the
other namely, "You do not have access rights to Logical Disk Manager on
computer name."

So let's assume the Cause preamble is not the whole story (they do say
"may" ) and jump into the various "methods" listed.

Notice the word "one" in the preamble and again "one" in the third "method."
It turns out the issue can arise when we "disconnect the network cable
during the Windows XP Out of Box Experience." Well that's all fine and
dandy. What if there is no Network connection during the OOBE? Hmmm...
Obviously this article implies that if we install Windows XP without a
Network Connection then we run the risk of at some time in the future, "You
do not have access rights to Logical Disk Manager on computer name." And
that is what has happened to me. I removed the system from the Network
Connection to do some work on it and guess what? I can no longer access
Disk Manager. Whether it is hooked up to the Domain or not from Windows XP.
Believe it or not I CAN access the Disk Manager from the Domain Controller
but no longer from Windows XP itself.

Hence I have to re-install because of this issue. And to make sure I don't
experience it again I have to make sure I do it while on the Network. Or
maybe not. The point is this issue has existed for three years now. And
what we have here is all that has been said about the matter and likely ever
will.

--
George Hester
_________________________________

Archived from groups: microsoft.public.windowsxp.general (More info?)

Did you expect anyone to read that?

--
--------------------------------------------------------------------------------------------------
http://webdiary.smh.com.au/archive [...] 01075.html
=================================================
"George Hester" <hesterloli@hotmail.com> wrote in message news:%23V5MvOpsFHA.3852@TK2MSFTNGP15.phx.gbl...
> Now I know you may think they do realize the issue because they have a
> Knowledge Base article on the issue. But come'on how long has Windows XP
> existed in the Market? And if you know anything about Knowledge Base
> articles and statements such as this in them "Microsoft is researching this
> problem and will post more information in this article when the information
> becomes available," you'll know that the issue will never be addressed -
> forever. Give me one example where a statement such as this in a Knowledge
> Base article was EVER addressed afterwards. Just one. Here is the KB:
>
> http://support.microsoft.com/defau [...] -us;884564
>
> Now I can tell you the RPC error as they have written here is only half the
> story. The other half they camouflage but if you read the article closely
> you will see they say, "receive either of the following error messages..."
> The important word here is "either." That means one or the other - maybe
> both since that is not addressed. The old Aristotlean logic here.
>
> Anyway reading further it says for cause, "because of a mismatch in the
> computer name and the name that the RPC service expects." Now this
> addresses one half of the Venn not the other. In fact the "either" has been
> completely ignored. The cause addresses the RPC half of the either NOT the
> other namely, "You do not have access rights to Logical Disk Manager on
> computer name."
>
> So let's assume the Cause preamble is not the whole story (they do say
> "may" ) and jump into the various "methods" listed.
>
> Notice the word "one" in the preamble and again "one" in the third "method."
> It turns out the issue can arise when we "disconnect the network cable
> during the Windows XP Out of Box Experience." Well that's all fine and
> dandy. What if there is no Network connection during the OOBE? Hmmm...
> Obviously this article implies that if we install Windows XP without a
> Network Connection then we run the risk of at some time in the future, "You
> do not have access rights to Logical Disk Manager on computer name." And
> that is what has happened to me. I removed the system from the Network
> Connection to do some work on it and guess what? I can no longer access
> Disk Manager. Whether it is hooked up to the Domain or not from Windows XP.
> Believe it or not I CAN access the Disk Manager from the Domain Controller
> but no longer from Windows XP itself.
>
> Hence I have to re-install because of this issue. And to make sure I don't
> experience it again I have to make sure I do it while on the Network. Or
> maybe not. The point is this issue has existed for three years now. And
> what we have here is all that has been said about the matter and likely ever
> will.
>
> --
> George Hester
> _________________________________
>

Archived from groups: microsoft.public.windowsxp.general (More info?)

I read it, and even glanced at the included MS link, and then wished I
hadn't ! :-)

regards, Richard


"David Candy" <.> wrote in message
newsOz4H$psFHA.416@TK2MSFTNGP10.phx.gbl...
Did you expect anyone to read that?

--
--------------------------------------------------------------------------------------------------
http://webdiary.smh.com.au/archive [...] 01075.html
=================================================
"George Hester" <hesterloli@hotmail.com> wrote in message
news:%23V5MvOpsFHA.3852@TK2MSFTNGP15.phx.gbl...
> Now I know you may think they do realize the issue because they have a
> Knowledge Base article on the issue. But come'on how long has Windows XP
> existed in the Market? And if you know anything about Knowledge Base
> articles and statements such as this in them "Microsoft is researching
> this
> problem and will post more information in this article when the
> information
> becomes available," you'll know that the issue will never be addressed -
> forever. Give me one example where a statement such as this in a
> Knowledge
> Base article was EVER addressed afterwards. Just one. Here is the KB:
>
> http://support.microsoft.com/defau [...] -us;884564
>
> Now I can tell you the RPC error as they have written here is only half
> the
> story. The other half they camouflage but if you read the article closely
> you will see they say, "receive either of the following error messages..."
> The important word here is "either." That means one or the other - maybe
> both since that is not addressed. The old Aristotlean logic here.
>
> Anyway reading further it says for cause, "because of a mismatch in the
> computer name and the name that the RPC service expects." Now this
> addresses one half of the Venn not the other. In fact the "either" has
> been
> completely ignored. The cause addresses the RPC half of the either NOT
> the
> other namely, "You do not have access rights to Logical Disk Manager on
> computer name."
>
> So let's assume the Cause preamble is not the whole story (they do say
> "may" ) and jump into the various "methods" listed.
>
> Notice the word "one" in the preamble and again "one" in the third
> "method."
> It turns out the issue can arise when we "disconnect the network cable
> during the Windows XP Out of Box Experience." Well that's all fine and
> dandy. What if there is no Network connection during the OOBE? Hmmm...
> Obviously this article implies that if we install Windows XP without a
> Network Connection then we run the risk of at some time in the future,
> "You
> do not have access rights to Logical Disk Manager on computer name." And
> that is what has happened to me. I removed the system from the Network
> Connection to do some work on it and guess what? I can no longer access
> Disk Manager. Whether it is hooked up to the Domain or not from Windows
> XP.
> Believe it or not I CAN access the Disk Manager from the Domain Controller
> but no longer from Windows XP itself.
>
> Hence I have to re-install because of this issue. And to make sure I
> don't
> experience it again I have to make sure I do it while on the Network. Or
> maybe not. The point is this issue has existed for three years now. And
> what we have here is all that has been said about the matter and likely
> ever
> will.
>
> --
> George Hester
> _________________________________
>

Archived from groups: microsoft.public.windowsxp.general (More info?)

Aye, Richard J Kranium.

--
--------------------------------------------------------------------------------------------------
http://webdiary.smh.com.au/archive [...] 01075.html
=================================================
"RJK" <notatospam@hotmail.com> wrote in message newslaeSDqsFHA.524@TK2MSFTNGP12.phx.gbl...
>I read it, and even glanced at the included MS link, and then wished I
> hadn't ! :-)
>
> regards, Richard
>
>
> "David Candy" <.> wrote in message
> newsOz4H$psFHA.416@TK2MSFTNGP10.phx.gbl...
> Did you expect anyone to read that?
>
> --
> --------------------------------------------------------------------------------------------------
> http://webdiary.smh.com.au/archive [...] 01075.html
> =================================================
> "George Hester" <hesterloli@hotmail.com> wrote in message
> news:%23V5MvOpsFHA.3852@TK2MSFTNGP15.phx.gbl...
>> Now I know you may think they do realize the issue because they have a
>> Knowledge Base article on the issue. But come'on how long has Windows XP
>> existed in the Market? And if you know anything about Knowledge Base
>> articles and statements such as this in them "Microsoft is researching
>> this
>> problem and will post more information in this article when the
>> information
>> becomes available," you'll know that the issue will never be addressed -
>> forever. Give me one example where a statement such as this in a
>> Knowledge
>> Base article was EVER addressed afterwards. Just one. Here is the KB:
>>
>> http://support.microsoft.com/defau [...] -us;884564
>>
>> Now I can tell you the RPC error as they have written here is only half
>> the
>> story. The other half they camouflage but if you read the article closely
>> you will see they say, "receive either of the following error messages..."
>> The important word here is "either." That means one or the other - maybe
>> both since that is not addressed. The old Aristotlean logic here.
>>
>> Anyway reading further it says for cause, "because of a mismatch in the
>> computer name and the name that the RPC service expects." Now this
>> addresses one half of the Venn not the other. In fact the "either" has
>> been
>> completely ignored. The cause addresses the RPC half of the either NOT
>> the
>> other namely, "You do not have access rights to Logical Disk Manager on
>> computer name."
>>
>> So let's assume the Cause preamble is not the whole story (they do say
>> "may" ) and jump into the various "methods" listed.
>>
>> Notice the word "one" in the preamble and again "one" in the third
>> "method."
>> It turns out the issue can arise when we "disconnect the network cable
>> during the Windows XP Out of Box Experience." Well that's all fine and
>> dandy. What if there is no Network connection during the OOBE? Hmmm...
>> Obviously this article implies that if we install Windows XP without a
>> Network Connection then we run the risk of at some time in the future,
>> "You
>> do not have access rights to Logical Disk Manager on computer name." And
>> that is what has happened to me. I removed the system from the Network
>> Connection to do some work on it and guess what? I can no longer access
>> Disk Manager. Whether it is hooked up to the Domain or not from Windows
>> XP.
>> Believe it or not I CAN access the Disk Manager from the Domain Controller
>> but no longer from Windows XP itself.
>>
>> Hence I have to re-install because of this issue. And to make sure I
>> don't
>> experience it again I have to make sure I do it while on the Network. Or
>> maybe not. The point is this issue has existed for three years now. And
>> what we have here is all that has been said about the matter and likely
>> ever
>> will.
>>
>> --
>> George Hester
>> _________________________________
>>
>
>

Archived from groups: microsoft.public.windowsxp.general (More info?)

The article was re-reviewed July 15 2005 (just a few weeks ago).
The problem (symptom, cause) is clearly stated and a workaround provided.

The problem itself is still under investigation and a fix may be forthcoming
in the future.

Beyond this I fail to see the point of your message. Is the workaround not
working for you or are you experiencing some other problem you think is
related to this one ?

--

Regards,

Mike
--
Mike Brannigan [Microsoft]

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

Please note I cannot respond to e-mailed questions, please use these
newsgroups

"George Hester" <hesterloli@hotmail.com> wrote in message
news:%23V5MvOpsFHA.3852@TK2MSFTNGP15.phx.gbl...
> Now I know you may think they do realize the issue because they have a
> Knowledge Base article on the issue. But come'on how long has Windows XP
> existed in the Market? And if you know anything about Knowledge Base
> articles and statements such as this in them "Microsoft is researching
> this
> problem and will post more information in this article when the
> information
> becomes available," you'll know that the issue will never be addressed -
> forever. Give me one example where a statement such as this in a
> Knowledge
> Base article was EVER addressed afterwards. Just one. Here is the KB:
>
> http://support.microsoft.com/defau [...] -us;884564
>
> Now I can tell you the RPC error as they have written here is only half
> the
> story. The other half they camouflage but if you read the article closely
> you will see they say, "receive either of the following error messages..."
> The important word here is "either." That means one or the other - maybe
> both since that is not addressed. The old Aristotlean logic here.
>
> Anyway reading further it says for cause, "because of a mismatch in the
> computer name and the name that the RPC service expects." Now this
> addresses one half of the Venn not the other. In fact the "either" has
> been
> completely ignored. The cause addresses the RPC half of the either NOT
> the
> other namely, "You do not have access rights to Logical Disk Manager on
> computer name."
>
> So let's assume the Cause preamble is not the whole story (they do say
> "may" ) and jump into the various "methods" listed.
>
> Notice the word "one" in the preamble and again "one" in the third
> "method."
> It turns out the issue can arise when we "disconnect the network cable
> during the Windows XP Out of Box Experience." Well that's all fine and
> dandy. What if there is no Network connection during the OOBE? Hmmm...
> Obviously this article implies that if we install Windows XP without a
> Network Connection then we run the risk of at some time in the future,
> "You
> do not have access rights to Logical Disk Manager on computer name." And
> that is what has happened to me. I removed the system from the Network
> Connection to do some work on it and guess what? I can no longer access
> Disk Manager. Whether it is hooked up to the Domain or not from Windows
> XP.
> Believe it or not I CAN access the Disk Manager from the Domain Controller
> but no longer from Windows XP itself.
>
> Hence I have to re-install because of this issue. And to make sure I
> don't
> experience it again I have to make sure I do it while on the Network. Or
> maybe not. The point is this issue has existed for three years now. And
> what we have here is all that has been said about the matter and likely
> ever
> will.
>
> --
> George Hester
> _________________________________
>

Archived from groups: microsoft.public.windowsxp.general (More info?)

The way I read it, that article refers to disconnecting the Network Cable
DURING the oobe, not before or after it.

A reinstall seems a bit drastic. Perhaps changing your computer name to a
temporary one and then back again might resolve the issue.

Otherwise Googling for that particular error message may turn up a
workaround.

http://tinyurl.com/7zjex


Jon




"George Hester" <hesterloli@hotmail.com> wrote in message
news:%23V5MvOpsFHA.3852@TK2MSFTNGP15.phx.gbl...
> Now I know you may think they do realize the issue because they have a
> Knowledge Base article on the issue. But come'on how long has Windows XP
> existed in the Market? And if you know anything about Knowledge Base
> articles and statements such as this in them "Microsoft is researching
> this
> problem and will post more information in this article when the
> information
> becomes available," you'll know that the issue will never be addressed -
> forever. Give me one example where a statement such as this in a
> Knowledge
> Base article was EVER addressed afterwards. Just one. Here is the KB:
>
> http://support.microsoft.com/defau [...] -us;884564
>
> Now I can tell you the RPC error as they have written here is only half
> the
> story. The other half they camouflage but if you read the article closely
> you will see they say, "receive either of the following error messages..."
> The important word here is "either." That means one or the other - maybe
> both since that is not addressed. The old Aristotlean logic here.
>
> Anyway reading further it says for cause, "because of a mismatch in the
> computer name and the name that the RPC service expects." Now this
> addresses one half of the Venn not the other. In fact the "either" has
> been
> completely ignored. The cause addresses the RPC half of the either NOT
> the
> other namely, "You do not have access rights to Logical Disk Manager on
> computer name."
>
> So let's assume the Cause preamble is not the whole story (they do say
> "may" ) and jump into the various "methods" listed.
>
> Notice the word "one" in the preamble and again "one" in the third
> "method."
> It turns out the issue can arise when we "disconnect the network cable
> during the Windows XP Out of Box Experience." Well that's all fine and
> dandy. What if there is no Network connection during the OOBE? Hmmm...
> Obviously this article implies that if we install Windows XP without a
> Network Connection then we run the risk of at some time in the future,
> "You
> do not have access rights to Logical Disk Manager on computer name." And
> that is what has happened to me. I removed the system from the Network
> Connection to do some work on it and guess what? I can no longer access
> Disk Manager. Whether it is hooked up to the Domain or not from Windows
> XP.
> Believe it or not I CAN access the Disk Manager from the Domain Controller
> but no longer from Windows XP itself.
>
> Hence I have to re-install because of this issue. And to make sure I
> don't
> experience it again I have to make sure I do it while on the Network. Or
> maybe not. The point is this issue has existed for three years now. And
> what we have here is all that has been said about the matter and likely
> ever
> will.
>
> --
> George Hester
> _________________________________
>

Archived from groups: microsoft.public.windowsxp.general (More info?)

Do you HAVE a life?

--
------------------------------------------------------------
Jayso

Please reply to this email so I know if i'm right

Good in Home Networking, XP Home based problems, and Pro based Problems
Add my email to MSN Messenger if u wish
jayso_chinnery@spamfreehotmail.com.au (remove spamfree)


"George Hester" <hesterloli@hotmail.com> wrote in message
news:%23V5MvOpsFHA.3852@TK2MSFTNGP15.phx.gbl...
> Now I know you may think they do realize the issue because they have a
> Knowledge Base article on the issue. But come'on how long has Windows XP
> existed in the Market? And if you know anything about Knowledge Base
> articles and statements such as this in them "Microsoft is researching
> this
> problem and will post more information in this article when the
> information
> becomes available," you'll know that the issue will never be addressed -
> forever. Give me one example where a statement such as this in a
> Knowledge
> Base article was EVER addressed afterwards. Just one. Here is the KB:
>
> http://support.microsoft.com/defau [...] -us;884564
>
> Now I can tell you the RPC error as they have written here is only half
> the
> story. The other half they camouflage but if you read the article closely
> you will see they say, "receive either of the following error messages..."
> The important word here is "either." That means one or the other - maybe
> both since that is not addressed. The old Aristotlean logic here.
>
> Anyway reading further it says for cause, "because of a mismatch in the
> computer name and the name that the RPC service expects." Now this
> addresses one half of the Venn not the other. In fact the "either" has
> been
> completely ignored. The cause addresses the RPC half of the either NOT
> the
> other namely, "You do not have access rights to Logical Disk Manager on
> computer name."
>
> So let's assume the Cause preamble is not the whole story (they do say
> "may" ) and jump into the various "methods" listed.
>
> Notice the word "one" in the preamble and again "one" in the third
> "method."
> It turns out the issue can arise when we "disconnect the network cable
> during the Windows XP Out of Box Experience." Well that's all fine and
> dandy. What if there is no Network connection during the OOBE? Hmmm...
> Obviously this article implies that if we install Windows XP without a
> Network Connection then we run the risk of at some time in the future,
> "You
> do not have access rights to Logical Disk Manager on computer name." And
> that is what has happened to me. I removed the system from the Network
> Connection to do some work on it and guess what? I can no longer access
> Disk Manager. Whether it is hooked up to the Domain or not from Windows
> XP.
> Believe it or not I CAN access the Disk Manager from the Domain Controller
> but no longer from Windows XP itself.
>
> Hence I have to re-install because of this issue. And to make sure I
> don't
> experience it again I have to make sure I do it while on the Network. Or
> maybe not. The point is this issue has existed for three years now. And
> what we have here is all that has been said about the matter and likely
> ever
> will.
>
> --
> George Hester
> _________________________________
>

Archived from groups: microsoft.public.windowsxp.general (More info?)

I never expect you Davd to do anything that takes a certain level of
intelligence. Move on.

--
George Hester
_________________________________
"David Candy" <.> wrote in message
newsOz4H$psFHA.416@TK2MSFTNGP10.phx.gbl...
Did you expect anyone to read that?

--
----------------------------------------------------------------------------
----------------------
http://webdiary.smh.com.au/archive [...] 01075.html
=================================================
"George Hester" <hesterloli@hotmail.com> wrote in message
news:%23V5MvOpsFHA.3852@TK2MSFTNGP15.phx.gbl...
> Now I know you may think they do realize the issue because they have a
> Knowledge Base article on the issue. But come'on how long has Windows XP
> existed in the Market? And if you know anything about Knowledge Base
> articles and statements such as this in them "Microsoft is researching
this
> problem and will post more information in this article when the
information
> becomes available," you'll know that the issue will never be addressed -
> forever. Give me one example where a statement such as this in a
Knowledge
> Base article was EVER addressed afterwards. Just one. Here is the KB:
>
> http://support.microsoft.com/defau [...] -us;884564
>
> Now I can tell you the RPC error as they have written here is only half
the
> story. The other half they camouflage but if you read the article closely
> you will see they say, "receive either of the following error messages..."
> The important word here is "either." That means one or the other - maybe
> both since that is not addressed. The old Aristotlean logic here.
>
> Anyway reading further it says for cause, "because of a mismatch in the
> computer name and the name that the RPC service expects." Now this
> addresses one half of the Venn not the other. In fact the "either" has
been
> completely ignored. The cause addresses the RPC half of the either NOT
the
> other namely, "You do not have access rights to Logical Disk Manager on
> computer name."
>
> So let's assume the Cause preamble is not the whole story (they do say
> "may" ) and jump into the various "methods" listed.
>
> Notice the word "one" in the preamble and again "one" in the third
"method."
> It turns out the issue can arise when we "disconnect the network cable
> during the Windows XP Out of Box Experience." Well that's all fine and
> dandy. What if there is no Network connection during the OOBE? Hmmm...
> Obviously this article implies that if we install Windows XP without a
> Network Connection then we run the risk of at some time in the future,
"You
> do not have access rights to Logical Disk Manager on computer name." And
> that is what has happened to me. I removed the system from the Network
> Connection to do some work on it and guess what? I can no longer access
> Disk Manager. Whether it is hooked up to the Domain or not from Windows
XP.
> Believe it or not I CAN access the Disk Manager from the Domain Controller
> but no longer from Windows XP itself.
>
> Hence I have to re-install because of this issue. And to make sure I
don't
> experience it again I have to make sure I do it while on the Network. Or
> maybe not. The point is this issue has existed for three years now. And
> what we have here is all that has been said about the matter and likely
ever
> will.
>
> --
> George Hester
> _________________________________
>

Archived from groups: microsoft.public.windowsxp.general (More info?)

Yes John that is what it says. But if you install without a Network
Connection then during the OOBE there is no Network connection. In other
words the cable is gone or what amounts to the same thing it has been
removed.

Now to tell you the truth trying to match up my situation with this OOBE
thing is probably stretching it. Here is MY cause. When we remove Windows
XP from a domain by removing the cable and then loging in with the
Administrator local account, we will find that Windows Disk Manager gives
the error as stated. Pretty simple.

But I am going to try your idea now. Off line. Thanks.

--
George Hester
_________________________________
"Jon" <Email_Address@SomewhereOrOther.com> wrote in message
newsTCl9drsFHA.3732@TK2MSFTNGP11.phx.gbl...
> The way I read it, that article refers to disconnecting the Network Cable
> DURING the oobe, not before or after it.
>
> A reinstall seems a bit drastic. Perhaps changing your computer name to a
> temporary one and then back again might resolve the issue.
>
> Otherwise Googling for that particular error message may turn up a
> workaround.
>
> http://tinyurl.com/7zjex
>
>
> Jon
>
>
>
>
> "George Hester" <hesterloli@hotmail.com> wrote in message
> news:%23V5MvOpsFHA.3852@TK2MSFTNGP15.phx.gbl...
> > Now I know you may think they do realize the issue because they have a
> > Knowledge Base article on the issue. But come'on how long has Windows
XP
> > existed in the Market? And if you know anything about Knowledge Base
> > articles and statements such as this in them "Microsoft is researching
> > this
> > problem and will post more information in this article when the
> > information
> > becomes available," you'll know that the issue will never be addressed -
> > forever. Give me one example where a statement such as this in a
> > Knowledge
> > Base article was EVER addressed afterwards. Just one. Here is the KB:
> >
> > http://support.microsoft.com/defau [...] -us;884564
> >
> > Now I can tell you the RPC error as they have written here is only half
> > the
> > story. The other half they camouflage but if you read the article
closely
> > you will see they say, "receive either of the following error
messages..."
> > The important word here is "either." That means one or the other -
maybe
> > both since that is not addressed. The old Aristotlean logic here.
> >
> > Anyway reading further it says for cause, "because of a mismatch in the
> > computer name and the name that the RPC service expects." Now this
> > addresses one half of the Venn not the other. In fact the "either" has
> > been
> > completely ignored. The cause addresses the RPC half of the either NOT
> > the
> > other namely, "You do not have access rights to Logical Disk Manager on
> > computer name."
> >
> > So let's assume the Cause preamble is not the whole story (they do say
> > "may" ) and jump into the various "methods" listed.
> >
> > Notice the word "one" in the preamble and again "one" in the third
> > "method."
> > It turns out the issue can arise when we "disconnect the network cable
> > during the Windows XP Out of Box Experience." Well that's all fine and
> > dandy. What if there is no Network connection during the OOBE? Hmmm...
> > Obviously this article implies that if we install Windows XP without a
> > Network Connection then we run the risk of at some time in the future,
> > "You
> > do not have access rights to Logical Disk Manager on computer name."
And
> > that is what has happened to me. I removed the system from the Network
> > Connection to do some work on it and guess what? I can no longer access
> > Disk Manager. Whether it is hooked up to the Domain or not from Windows
> > XP.
> > Believe it or not I CAN access the Disk Manager from the Domain
Controller
> > but no longer from Windows XP itself.
> >
> > Hence I have to re-install because of this issue. And to make sure I
> > don't
> > experience it again I have to make sure I do it while on the Network. O
r
> > maybe not. The point is this issue has existed for three years now.
And
> > what we have here is all that has been said about the matter and likely
> > ever
> > will.
> >
> > --
> > George Hester
> > _________________________________
> >
>
>

Archived from groups: microsoft.public.windowsxp.general (More info?)

Ah you know what Jon I think you got it. I remember once I read that when
we disconnect Windows XP from the domain to do something like what I want to
do I should remove it from the domain first. That is what I am going to
try. I'll hook it back up to the domain release it from the domain and try
again. We'll see how that goes. Thanks for the help.

--
George Hester
_________________________________
"Jon" <Email_Address@SomewhereOrOther.com> wrote in message
newsTCl9drsFHA.3732@TK2MSFTNGP11.phx.gbl...
> The way I read it, that article refers to disconnecting the Network Cable
> DURING the oobe, not before or after it.
>
> A reinstall seems a bit drastic. Perhaps changing your computer name to a
> temporary one and then back again might resolve the issue.
>
> Otherwise Googling for that particular error message may turn up a
> workaround.
>
> http://tinyurl.com/7zjex
>
>
> Jon
>
>
>
>