NET USE IPC$ /u:

[Paul Wehland]

I have two XP machines both in Workgroups, neither in Domain. Machine A and
Machine B.
While working on Machine B, I discover I need a file off of a non-shared
resource on Machine A.
I issue:
NET USE \\A\IPC$ /u:A\Administrator PassWord

This always used to work in Win2k and before. Now I get Logon Failure.
Can we no longer connect to the IPC$ share to give us Admin access to
machine A?
If not, how do I get files off of another machine in a workgroup?

[Doug Knox MS-MVP]

You're not specifying the drive letter that you want to use.

NET USE X: \\Computername\Sharename /USER:A\Administrator password

--=20
In memory of Robert (aka Koldbear)
http://www.btinternet.com/~winnoel/winhelp.htm
--------------------------------
Doug Knox, MS-MVP Windows XP/ Windows Smart Display
Win 95/98/Me/XP Tweaks and Fixes
http://www.dougknox.com
--------------------------------
Per user Group Policy Restrictions for XP Home and XP Pro
http://www.dougknox.com/xp/utils/xp_securityconsole.htm
--------------------------------
Please reply only to the newsgroup so all may benefit.
Unsolicited e-mail is not answered.
=20
"Paul Wehland" > wrote in message =
...
> I have two XP machines both in Workgroups, neither in Domain. Machine =
A and
> Machine B.
> While working on Machine B, I discover I need a file off of a =
non-shared
> resource on Machine A.
> I issue:
> NET USE \\A\IPC$ /u:A\Administrator PassWord
>=20
> This always used to work in Win2k and before. Now I get Logon =
Failure.
> Can we no longer connect to the IPC$ share to give us Admin access to
> machine A?
> If not, how do I get files off of another machine in a workgroup?
>=20
>=20
>

[Torgeir Bakken (MVP)]

Paul Wehland wrote:

> I have two XP machines both in Workgroups, neither in Domain. Machine A and
> Machine B.
> While working on Machine B, I discover I need a file off of a non-shared
> resource on Machine A.
> I issue:
> NET USE \\A\IPC$ /u:A\Administrator PassWord
>
> This always used to work in Win2k and before. Now I get Logon Failure.
> Can we no longer connect to the IPC$ share to give us Admin access to
> machine A?

Hi

In addition to what Doug wrote:

As the WinXP computers are not in a domain, it can be a ForceGuest issue.

WinXP in a workgroup setting defaults to authenticate all connections coming
from "the network" as the Guest User (only possible to change on WinXP Pro).

More about this here:
http://groups.google.com/groups?selm=3E822EB9.C5D31E11%40hydro.com



--
torgeir
Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of the 1328 page
Scripting Guide: http://www.microsoft.com/technet/scriptcenter

[Paul Wehland]

I shouldn't have to. I am not connecting to a drive, only to a named pipe:
IPC$


"Doug Knox MS-MVP" > wrote in message
...
You're not specifying the drive letter that you want to use.

NET USE X: \\Computername\Sharename /USER:A\Administrator password


"Paul Wehland" > wrote in message
...
> I have two XP machines both in Workgroups, neither in Domain. Machine A
and
> Machine B.
> While working on Machine B, I discover I need a file off of a non-shared
> resource on Machine A.
> I issue:
> NET USE \\A\IPC$ /u:A\Administrator PassWord
>
> This always used to work in Win2k and before. Now I get Logon Failure.
> Can we no longer connect to the IPC$ share to give us Admin access to
> machine A?
> If not, how do I get files off of another machine in a workgroup?
>
>
>

[Paul Wehland]

"Torgeir Bakken (MVP)" > wrote in message
...
> Paul Wehland wrote:
>
> > I have two XP machines both in Workgroups, neither in Domain. Machine A
and
> > Machine B.
> > While working on Machine B, I discover I need a file off of a non-shared
> > resource on Machine A.
> > I issue:
> > NET USE \\A\IPC$ /u:A\Administrator PassWord
> >
> > This always used to work in Win2k and before. Now I get Logon Failure.
> > Can we no longer connect to the IPC$ share to give us Admin access to
> > machine A?
>
> Hi
>
> In addition to what Doug wrote:
>
> As the WinXP computers are not in a domain, it can be a ForceGuest issue.
>
> WinXP in a workgroup setting defaults to authenticate all connections
coming
> from "the network" as the Guest User (only possible to change on WinXP
Pro).
>
> More about this here:
> http://groups.google.com/groups?selm=3E822EB9.C5D31E11%40hydro.com
>
>
>

That was it!
Security Settings -> Local Policies -> Security Options -> Network Access:
Sharing and Security Model for Local Accounts -> "Classic"

Why did MS change behavior between releases? Seems to break backwards
compatibility.

Thanks Torgeir!

[Torgeir Bakken (MVP)]

Paul Wehland wrote:

> Torgeir Bakken (MVP) wrote:
> >
> > As the WinXP computers are not in a domain, it can be a ForceGuest issue.
> >
> > WinXP in a workgroup setting defaults to authenticate all connections
> > coming from "the network" as the Guest User (only possible to change
> > on WinXP Pro).
> >
> > More about this here:
> > http://groups.google.com/groups?selm=3E822EB9.C5D31E11%40hydro.com
> >
>
> That was it!
> Security Settings -> Local Policies -> Security Options -> Network Access:
> Sharing and Security Model for Local Accounts -> "Classic"
>
> Why did MS change behavior between releases? Seems to break backwards
> compatibility.

Hi

The word is "Security". Almost everyone have been screaming that MS Windows
OSes are so unsecure and asking why Microsoft don't do anything about it.
So, lately, Microsoft have started to let things be more secure and locked
down in a out of the box configuration, and rightfully so if you ask me.

This will of course mean that some thing will stop working for some until
they reconfigure (just wait to SP2 for Win XP is released ;-), but I think
it is worth it to have a more secure computer experience.



--
torgeir
Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of the 1328 page
Scripting Guide: http://www.microsoft.com/technet/scriptcenter