Vista Home Network with Windows Millennium Edition

Jeffery - thanks for the reply

I don't get the option to enter a username from the original prompt -
PASSWORD only. Your suggestion prompted me to attempt
"\\COMPUTERNAME\USERNAME" from START\RUN command prompt. Vista prompted for
the USERNAME password, but it still did not accept it.

There are no issues between ME & XP, all is well between the two.

Here is a copy of the Vista Security Event log:
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 1/1/2008 5:55:14 PM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: Main-PC
Description:
An account failed to log on.

Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0

Logon Type: 3

Account For Which Logon Failed:
Security ID: NULL SID
Account Name: CRAIG
Account Domain: HOME

Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc000006a

Process Information:
Caller Process ID: 0x0
Caller Process Name: -

Network Information:
Workstation Name: \\WINME HALEYS
Source Network Address: xxx.xxx.x.xx
Source Port: xxxx

Detailed Authentication Information:
Logon Process: NtLmSsp
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): -
Key Length: 0

This event is generated when a logon request fails. It is generated on the
computer where access was attempted.

The Subject fields indicate the account on the local system which requested
the logon. This is most commonly a service such as the Server service, or a
local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The
most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the
system requested the logon.

The Network Information fields indicate where a remote logon request
originated. Workstation name is not always available and may be left blank in
some cases.

The authentication information fields provide detailed information about
this specific logon request.
- Transited services indicate which intermediate services have participated
in this logon request.
- Package name indicates which sub-protocol was used among the NTLM
protocols.
- Key length indicates the length of the generated session key. This will
be 0 if no session key was requested.




"Jeffrey Randow" wrote:

> Try entering the username as COMPUTERNAME\USERNAME
>
> Also, take a look at the Security Event Log on the Vista box to see
> what type of security error is logged...
>
> Arethere any issues between ME and XP?
> ---
> Jeffrey Randow
> jeffreycentex@gmail.com
> Windows Networking MVP 2001-2006
> http://www.networkblog.net
>
> On Tue, 1 Jan 2008 17:30:01 -0800, Craigstir
> <Craigstir@discussions.microsoft.com> wrote:
>

> >I am adding a new PC with Windows Vista to a home network via ethernet hub
> >consisting of 2 other PC's, one using XP, one using Windows Millennium
> >Edition.
> >
> >Access (sharing) with Vista & XP systems is working perfectly (in both
> >directions). Access from Vista to ME is working. Access from ME to Vista is
> >almost working.
> >From the ME PC I can find the Vista PC in the network.
> >
> >Public sharing on the Vista PC is is turned on, and Password protected
> >sharing is turned off, but when I attempt to access Vista PC from the Windows
> >Millennium PC, I get the window "ENTER NETWORK PASSWORD". I've tried using
> >Admin & various user passwords from both PC's but all are returned as
> >invalid. Anyone know how to get around this?

>

Try running the following:

net use x: \\computername\sharename password
/USER:computername\username

Replace x:,computername, sharename, password,and computername as
appropriate.

This will let us know if it is a security issue with your
username/password

Also, are all of the computers on the same Workgroup? ME is fairly
critical when it comes to having Workgroup names match.

---
Jeffrey Randow
jeffreycentex@gmail.com
Windows Networking MVP 2001-2006
http://www.networkblog.net

On Tue, 1 Jan 2008 18:23:00 -0800, Craigstir
<Craigstir@discussions.microsoft.com> wrote:

>Jeffery - thanks for the reply
>
>I don't get the option to enter a username from the original prompt -
>PASSWORD only. Your suggestion prompted me to attempt
>"\\COMPUTERNAME\USERNAME" from START\RUN command prompt. Vista prompted for
>the USERNAME password, but it still did not accept it.
>
>There are no issues between ME & XP, all is well between the two.
>
>Here is a copy of the Vista Security Event log:
>Log Name: Security
>Source: Microsoft-Windows-Security-Auditing
>Date: 1/1/2008 5:55:14 PM
>Event ID: 4625
>Task Category: Logon
>Level: Information
>Keywords: Audit Failure
>User: N/A
>Computer: Main-PC
>Description:
>An account failed to log on.
>
>Subject:
> Security ID: NULL SID
> Account Name: -
> Account Domain: -
> Logon ID: 0x0
>
>Logon Type: 3
>
>Account For Which Logon Failed:
> Security ID: NULL SID
> Account Name: CRAIG
> Account Domain: HOME
>
>Failure Information:
> Failure Reason: Unknown user name or bad password.
> Status: 0xc000006d
> Sub Status: 0xc000006a
>
>Process Information:
> Caller Process ID: 0x0
> Caller Process Name: -
>
>Network Information:
> Workstation Name: \\WINME HALEYS
> Source Network Address: xxx.xxx.x.xx
> Source Port: xxxx
>
>Detailed Authentication Information:
> Logon Process: NtLmSsp
> Authentication Package: NTLM
> Transited Services: -
> Package Name (NTLM only): -
> Key Length: 0
>
>This event is generated when a logon request fails. It is generated on the
>computer where access was attempted.
>
>The Subject fields indicate the account on the local system which requested
>the logon. This is most commonly a service such as the Server service, or a
>local process such as Winlogon.exe or Services.exe.
>
>The Logon Type field indicates the kind of logon that was requested. The
>most common types are 2 (interactive) and 3 (network).
>
>The Process Information fields indicate which account and process on the
>system requested the logon.
>
>The Network Information fields indicate where a remote logon request
>originated. Workstation name is not always available and may be left blank in
>some cases.
>
>The authentication information fields provide detailed information about
>this specific logon request.
> - Transited services indicate which intermediate services have participated
>in this logon request.
> - Package name indicates which sub-protocol was used among the NTLM
>protocols.
> - Key length indicates the length of the generated session key. This will
>be 0 if no session key was requested.

I wasn't clear as to which PC you wanted me to run the command on (presume
Vista), so tried it on both:

Vista returned "The command completed successfully" (I now have the shared
folder as drive M: as a Network Drive).
ME returned "The option USER not known"

And, yes, all PC's are on the same WORKGROUP

"Jeffrey Randow" wrote:

> Try running the following:
>
> net use x: \\computername\sharename password
> /USER:computername\username
>
> Replace x:,computername, sharename, password,and computername as
> appropriate.
>
> This will let us know if it is a security issue with your
> username/password
>
> Also, are all of the computers on the same Workgroup? ME is fairly
> critical when it comes to having Workgroup names match.
>
> ---
> Jeffrey Randow
> jeffreycentex@gmail.com
> Windows Networking MVP 2001-2006
> http://www.networkblog.net
>
> On Tue, 1 Jan 2008 18:23:00 -0800, Craigstir
> <Craigstir@discussions.microsoft.com> wrote:
>

> >Jeffery - thanks for the reply
> >
> >I don't get the option to enter a username from the original prompt -
> >PASSWORD only. Your suggestion prompted me to attempt
> >"\\COMPUTERNAME\USERNAME" from START\RUN command prompt. Vista prompted for
> >the USERNAME password, but it still did not accept it.
> >
> >There are no issues between ME & XP, all is well between the two.
> >
> >Here is a copy of the Vista Security Event log:
> >Log Name: Security
> >Source: Microsoft-Windows-Security-Auditing
> >Date: 1/1/2008 5:55:14 PM
> >Event ID: 4625
> >Task Category: Logon
> >Level: Information
> >Keywords: Audit Failure
> >User: N/A
> >Computer: Main-PC
> >Description:
> >An account failed to log on.
> >
> >Subject:
> > Security ID: NULL SID
> > Account Name: -
> > Account Domain: -
> > Logon ID: 0x0
> >
> >Logon Type: 3
> >
> >Account For Which Logon Failed:
> > Security ID: NULL SID
> > Account Name: CRAIG
> > Account Domain: HOME
> >
> >Failure Information:
> > Failure Reason: Unknown user name or bad password.
> > Status: 0xc000006d
> > Sub Status: 0xc000006a
> >
> >Process Information:
> > Caller Process ID: 0x0
> > Caller Process Name: -
> >
> >Network Information:
> > Workstation Name: \\WINME HALEYS
> > Source Network Address: xxx.xxx.x.xx
> > Source Port: xxxx
> >
> >Detailed Authentication Information:
> > Logon Process: NtLmSsp
> > Authentication Package: NTLM
> > Transited Services: -
> > Package Name (NTLM only): -
> > Key Length: 0
> >
> >This event is generated when a logon request fails. It is generated on the
> >computer where access was attempted.
> >
> >The Subject fields indicate the account on the local system which requested
> >the logon. This is most commonly a service such as the Server service, or a
> >local process such as Winlogon.exe or Services.exe.
> >
> >The Logon Type field indicates the kind of logon that was requested. The
> >most common types are 2 (interactive) and 3 (network).
> >
> >The Process Information fields indicate which account and process on the
> >system requested the logon.
> >
> >The Network Information fields indicate where a remote logon request
> >originated. Workstation name is not always available and may be left blank in
> >some cases.
> >
> >The authentication information fields provide detailed information about
> >this specific logon request.
> > - Transited services indicate which intermediate services have participated
> >in this logon request.
> > - Package name indicates which sub-protocol was used among the NTLM
> >protocols.
> > - Key length indicates the length of the generated session key. This will
> >be 0 if no session key was requested.

>

Oopss.. Sorry about that last one. I forgot the Win9X/Me NET USE
command...


---
Jeffrey Randow
jeffreycentex@gmail.com
Windows Networking MVP 2001-2006
http://www.networkblog.net



On Thu, 3 Jan 2008 00:05:01 -0800, Craigstir
<Craigstir@discussions.microsoft.com> wrote:

>I wasn't clear as to which PC you wanted me to run the command on (presume
>Vista), so tried it on both:
>
>Vista returned "The command completed successfully" (I now have the shared
>folder as drive M: as a Network Drive).
>ME returned "The option USER not known"
>
>And, yes, all PC's are on the same WORKGROUP
>
>"Jeffrey Randow" wrote:
>

>> Try running the following:
>>
>> net use x: \\computername\sharename password
>> /USER:computername\username
>>
>> Replace x:,computername, sharename, password,and computername as
>> appropriate.
>>
>> This will let us know if it is a security issue with your
>> username/password
>>
>> Also, are all of the computers on the same Workgroup? ME is fairly
>> critical when it comes to having Workgroup names match.
>>
>> ---
>> Jeffrey Randow
>> jeffreycentex@gmail.com
>> Windows Networking MVP 2001-2006
>> http://www.networkblog.net
>>
>> On Tue, 1 Jan 2008 18:23:00 -0800, Craigstir
>> <Craigstir@discussions.microsoft.com> wrote:
>>

>> >Jeffery - thanks for the reply
>> >
>> >I don't get the option to enter a username from the original prompt -
>> >PASSWORD only. Your suggestion prompted me to attempt
>> >"\\COMPUTERNAME\USERNAME" from START\RUN command prompt. Vista prompted for
>> >the USERNAME password, but it still did not accept it.
>> >
>> >There are no issues between ME & XP, all is well between the two.
>> >
>> >Here is a copy of the Vista Security Event log:
>> >Log Name: Security
>> >Source: Microsoft-Windows-Security-Auditing
>> >Date: 1/1/2008 5:55:14 PM
>> >Event ID: 4625
>> >Task Category: Logon
>> >Level: Information
>> >Keywords: Audit Failure
>> >User: N/A
>> >Computer: Main-PC
>> >Description:
>> >An account failed to log on.
>> >
>> >Subject:
>> > Security ID: NULL SID
>> > Account Name: -
>> > Account Domain: -
>> > Logon ID: 0x0
>> >
>> >Logon Type: 3
>> >
>> >Account For Which Logon Failed:
>> > Security ID: NULL SID
>> > Account Name: CRAIG
>> > Account Domain: HOME
>> >
>> >Failure Information:
>> > Failure Reason: Unknown user name or bad password.
>> > Status: 0xc000006d
>> > Sub Status: 0xc000006a
>> >
>> >Process Information:
>> > Caller Process ID: 0x0
>> > Caller Process Name: -
>> >
>> >Network Information:
>> > Workstation Name: \\WINME HALEYS
>> > Source Network Address: xxx.xxx.x.xx
>> > Source Port: xxxx
>> >
>> >Detailed Authentication Information:
>> > Logon Process: NtLmSsp
>> > Authentication Package: NTLM
>> > Transited Services: -
>> > Package Name (NTLM only): -
>> > Key Length: 0
>> >
>> >This event is generated when a logon request fails. It is generated on the
>> >computer where access was attempted.
>> >
>> >The Subject fields indicate the account on the local system which requested
>> >the logon. This is most commonly a service such as the Server service, or a
>> >local process such as Winlogon.exe or Services.exe.
>> >
>> >The Logon Type field indicates the kind of logon that was requested. The
>> >most common types are 2 (interactive) and 3 (network).
>> >
>> >The Process Information fields indicate which account and process on the
>> >system requested the logon.
>> >
>> >The Network Information fields indicate where a remote logon request
>> >originated. Workstation name is not always available and may be left blank in
>> >some cases.
>> >
>> >The authentication information fields provide detailed information about
>> >this specific logon request.
>> > - Transited services indicate which intermediate services have participated
>> >in this logon request.
>> > - Package name indicates which sub-protocol was used among the NTLM
>> >protocols.
>> > - Key length indicates the length of the generated session key. This will
>> >be 0 if no session key was requested.

>>

No problem, and completely understandable since most folks probably would not
have cause to use the ME command in the past 5 years or so. Any further
suggestions ... where do we go from here?

"Jeffrey Randow" wrote:

> Oopss.. Sorry about that last one. I forgot the Win9X/Me NET USE
> command...
>
>
> ---
> Jeffrey Randow
> jeffreycentex@gmail.com
> Windows Networking MVP 2001-2006
> http://www.networkblog.net
>
>
>
> On Thu, 3 Jan 2008 00:05:01 -0800, Craigstir
> <Craigstir@discussions.microsoft.com> wrote:
>

> >I wasn't clear as to which PC you wanted me to run the command on (presume
> >Vista), so tried it on both:
> >
> >Vista returned "The command completed successfully" (I now have the shared
> >folder as drive M: as a Network Drive).
> >ME returned "The option USER not known"
> >
> >And, yes, all PC's are on the same WORKGROUP
> >
> >"Jeffrey Randow" wrote:
> >

> >> Try running the following:
> >>
> >> net use x: \\computername\sharename password
> >> /USER:computername\username
> >>
> >> Replace x:,computername, sharename, password,and computername as
> >> appropriate.
> >>
> >> This will let us know if it is a security issue with your
> >> username/password
> >>
> >> Also, are all of the computers on the same Workgroup? ME is fairly
> >> critical when it comes to having Workgroup names match.
> >>
> >> ---
> >> Jeffrey Randow
> >> jeffreycentex@gmail.com
> >> Windows Networking MVP 2001-2006
> >> http://www.networkblog.net
> >>
> >> On Tue, 1 Jan 2008 18:23:00 -0800, Craigstir
> >> <Craigstir@discussions.microsoft.com> wrote:
> >>
> >> >Jeffery - thanks for the reply
> >> >
> >> >I don't get the option to enter a username from the original prompt -
> >> >PASSWORD only. Your suggestion prompted me to attempt
> >> >"\\COMPUTERNAME\USERNAME" from START\RUN command prompt. Vista prompted for
> >> >the USERNAME password, but it still did not accept it.
> >> >
> >> >There are no issues between ME & XP, all is well between the two.
> >> >
> >> >Here is a copy of the Vista Security Event log:
> >> >Log Name: Security
> >> >Source: Microsoft-Windows-Security-Auditing
> >> >Date: 1/1/2008 5:55:14 PM
> >> >Event ID: 4625
> >> >Task Category: Logon
> >> >Level: Information
> >> >Keywords: Audit Failure
> >> >User: N/A
> >> >Computer: Main-PC
> >> >Description:
> >> >An account failed to log on.
> >> >
> >> >Subject:
> >> > Security ID: NULL SID
> >> > Account Name: -
> >> > Account Domain: -
> >> > Logon ID: 0x0
> >> >
> >> >Logon Type: 3
> >> >
> >> >Account For Which Logon Failed:
> >> > Security ID: NULL SID
> >> > Account Name: CRAIG
> >> > Account Domain: HOME
> >> >
> >> >Failure Information:
> >> > Failure Reason: Unknown user name or bad password.
> >> > Status: 0xc000006d
> >> > Sub Status: 0xc000006a
> >> >
> >> >Process Information:
> >> > Caller Process ID: 0x0
> >> > Caller Process Name: -
> >> >
> >> >Network Information:
> >> > Workstation Name: \\WINME HALEYS
> >> > Source Network Address: xxx.xxx.x.xx
> >> > Source Port: xxxx
> >> >
> >> >Detailed Authentication Information:
> >> > Logon Process: NtLmSsp
> >> > Authentication Package: NTLM
> >> > Transited Services: -
> >> > Package Name (NTLM only): -
> >> > Key Length: 0
> >> >
> >> >This event is generated when a logon request fails. It is generated on the
> >> >computer where access was attempted.
> >> >
> >> >The Subject fields indicate the account on the local system which requested
> >> >the logon. This is most commonly a service such as the Server service, or a
> >> >local process such as Winlogon.exe or Services.exe.
> >> >
> >> >The Logon Type field indicates the kind of logon that was requested. The
> >> >most common types are 2 (interactive) and 3 (network).
> >> >
> >> >The Process Information fields indicate which account and process on the
> >> >system requested the logon.
> >> >
> >> >The Network Information fields indicate where a remote logon request
> >> >originated. Workstation name is not always available and may be left blank in
> >> >some cases.
> >> >
> >> >The authentication information fields provide detailed information about
> >> >this specific logon request.
> >> > - Transited services indicate which intermediate services have participated
> >> >in this logon request.
> >> > - Package name indicates which sub-protocol was used among the NTLM
> >> >protocols.
> >> > - Key length indicates the length of the generated session key. This will
> >> >be 0 if no session key was requested.
> >>

>

I'm trying to set up network with windowsME on one computer and Vista on the
other. Both computers are hardwired to wireless router and are both recieving
internet connections. But I cannot seem get them to see the other. I did ping
the vista computer from the ME computer and that came back well but vista
does not show up anywhere else. Also while trying to ping the ME from the
Vista, Me dos not show up at all. Workplace names are the same and computer
names are different. How did you get this to work? Any help would be much
appreciated

"Craigstir" wrote:

> I am adding a new PC with Windows Vista to a home network via ethernet hub
> consisting of 2 other PC's, one using XP, one using Windows Millennium
> Edition.
>
> Access (sharing) with Vista & XP systems is working perfectly (in both
> directions). Access from Vista to ME is working. Access from ME to Vista is
> almost working.
> From the ME PC I can find the Vista PC in the network.
>
> Public sharing on the Vista PC is is turned on, and Password protected
> sharing is turned off, but when I attempt to access Vista PC from the Windows
> Millennium PC, I get the window "ENTER NETWORK PASSWORD". I've tried using
> Admin & various user passwords from both PC's but all are returned as
> invalid. Anyone know how to get around this?