Cannot authenticate wireless

Please advise.
I have a wireless router connected to a 2003 server.
Only 1 of 3 wireless clients can authenticate to the
domain. When the other 2 log in locally, they have
wireless access. All three systems are using the same
wireless card and OS (Win XP Pro). As a test, I used my
roaming admin account on all three client systems with
the same results. This does not appear to be a profile,
router or even a server config issue. Rather, a setting
on the client OS. Any thoughts? Any suggestions would
be greatly appreciated. Please email me.

Thanks
Gary

Can these client PCs logon to the domain when wired to the LAN?
Make sure that you have a valid computer account for each PC under Active Directory Users and Computers.
--------------------
>From: "Gary" <(E-Mail Removed)>
>Sender: "Gary" <(E-Mail Removed)>
>Subject: Cannot authenticate wireless
>Date: Tue, 20 Apr 2004 12:11:36 -0700
>
>Please advise.
>I have a wireless router connected to a 2003 server.
>Only 1 of 3 wireless clients can authenticate to the
>domain. When the other 2 log in locally, they have
>wireless access. All three systems are using the same
>wireless card and OS (Win XP Pro). As a test, I used my
>roaming admin account on all three client systems with
>the same results. This does not appear to be a profile,
>router or even a server config issue. Rather, a setting
>on the client OS. Any thoughts? Any suggestions would
>be greatly appreciated. Please email me.
>
>Thanks
>Gary
>
>

--
Sergio Moreno
Microsoft Windows Networking

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.

I haven't tried them wired. They are some distance away;
hence their need for wireless. I could move one to the
router as a test but as previously noted, one of the
three client systems can authenticate using the same
account. For clarification, I'm only attempting to log
onto this particular user account one system at a time.
I.E. The client that does authenticate is logged off
when I attempt one of the other 2.

As for the "computer account", there are User accounts
but I'm not familiar with any need for an account for the
system itself. After all, I didn't create a computer
account for the one that does authenticate.

Am I missing some information on "computer accounts" in
order for them to authenticate?

An additional note, the client that does connect was
previously wired to the router when the server was
running Windows Advanced Server 2000. Not sure if this
helps or not.

Any suggestions would be greatly appreciated.

Thanks
Gary




>-----Original Message-----
>Can these client PCs logon to the domain when wired to
the LAN?
>Make sure that you have a valid computer account for
each PC under Active Directory Users and Computers.
>--------------------
>>From: "Gary" <(E-Mail Removed)>
>>Sender: "Gary" <(E-Mail Removed)>
>>Subject: Cannot authenticate wireless
>>Date: Tue, 20 Apr 2004 12:11:36 -0700
>>
>>Please advise.
>>I have a wireless router connected to a 2003 server.
>>Only 1 of 3 wireless clients can authenticate to the
>>domain. When the other 2 log in locally, they have
>>wireless access. All three systems are using the same
>>wireless card and OS (Win XP Pro). As a test, I used
my
>>roaming admin account on all three client systems with
>>the same results. This does not appear to be a
profile,
>>router or even a server config issue. Rather, a
setting
>>on the client OS. Any thoughts? Any suggestions would
>>be greatly appreciated. Please email me.
>>
>>Thanks
>>Gary
>>
>>
>
>--
>Sergio Moreno
>Microsoft Windows Networking
>
>This posting is provided "AS IS" with no warranties, and
confers no rights. Use of included script samples are
subject to the terms specified at
>http://www.microsoft.com/info/cpyright.htm
>
>Note: For the benefit of the community-at-large, all
responses to this message are best directed to the
newsgroup/thread from which they originated.
>
>.
>

Is your Windows 2003 AD domain an upgrade from a Windows 2000 AD?
A computer account is needed for Wireless connections in Windows 2000, check the next KB:
HOW TO: Support Wireless Connections in Windows 2000 WGID:476
ID: 318710
http://support.microsoft.com/?id=318710

The computer that works had an account created under Windows 2000 AD when it joined the domain.
Are the other two computers members of the Windows 2003 domain?
Check AD users and computers and make sure that Dial in Permission is enabled for each computer account if it exists.

Do you get any of the following errors when authentication fails?

"Windows was unable to log you on to the network"
OR
"Windows was unable to find a certificate to log you on to the network"

What is the Authmode key set to for the two PCs that your are having a problem with?
Check under HKLM\Software\Micorosoft\EAPOL\Parameters\General\ Global


--------------------
>From: "Gary" <(E-Mail Removed)>
>Subject: RE: Cannot authenticate wireless
>Date: Sun, 25 Apr 2004 23:33:11 -0700
>
>I haven't tried them wired. They are some distance away;
>hence their need for wireless. I could move one to the
>router as a test but as previously noted, one of the
>three client systems can authenticate using the same
>account. For clarification, I'm only attempting to log
>onto this particular user account one system at a time.
>I.E. The client that does authenticate is logged off
>when I attempt one of the other 2.
>
>As for the "computer account", there are User accounts
>but I'm not familiar with any need for an account for the
>system itself. After all, I didn't create a computer
>account for the one that does authenticate.
>
>Am I missing some information on "computer accounts" in
>order for them to authenticate?
>
>An additional note, the client that does connect was
>previously wired to the router when the server was
>running Windows Advanced Server 2000. Not sure if this
>helps or not.
>
>Any suggestions would be greatly appreciated.
>
>Thanks
>Gary
>
>
>
>
>>-----Original Message-----
>>Can these client PCs logon to the domain when wired to
>the LAN?
>>Make sure that you have a valid computer account for
>each PC under Active Directory Users and Computers.
>>--------------------
>>>From: "Gary" <(E-Mail Removed)>
>>>Sender: "Gary" <(E-Mail Removed)>
>>>Subject: Cannot authenticate wireless
>>>Date: Tue, 20 Apr 2004 12:11:36 -0700
>>>
>>>Please advise.
>>>I have a wireless router connected to a 2003 server.
>>>Only 1 of 3 wireless clients can authenticate to the
>>>domain. When the other 2 log in locally, they have
>>>wireless access. All three systems are using the same
>>>wireless card and OS (Win XP Pro). As a test, I used
>my
>>>roaming admin account on all three client systems with
>>>the same results. This does not appear to be a
>profile,
>>>router or even a server config issue. Rather, a
>setting
>>>on the client OS. Any thoughts? Any suggestions would
>>>be greatly appreciated. Please email me.
>>>
>>>Thanks
>>>Gary
>>>
>>>
>>
>>--
>>Sergio Moreno
>>Microsoft Windows Networking
>>
>>This posting is provided "AS IS" with no warranties, and
>confers no rights. Use of included script samples are
>subject to the terms specified at
>>http://www.microsoft.com/info/cpyright.htm
>>
>>Note: For the benefit of the community-at-large, all
>responses to this message are best directed to the
>newsgroup/thread from which they originated.
>>
>>.
>>
>

--
Sergio Moreno
Microsoft Windows Networking

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.

No. Server 2003 is a clean install.
AD does show all three computer accounts but for the 2
that have yet to authenticate, some of the information is
missing from their properties.

All 3 computer accounts (including the one that can
authenticate) have "Dial In" unchecked (disabled).

I receive no error at all on them when they try to
authenticate. It just seems to time out after a while
and then it goes back to the log in screen.

None of the 3 have an Authmode key in the registry.
Just "(Default)" with no value set.

Thank you for your continued help Sergio!
Gary


>-----Original Message-----
>Is your Windows 2003 AD domain an upgrade from a Windows
2000 AD?
>A computer account is needed for Wireless connections in
Windows 2000, check the next KB:
>HOW TO: Support Wireless Connections in Windows 2000
WGID:476
>ID: 318710
>http://support.microsoft.com/?id=318710
>
>The computer that works had an account created under
Windows 2000 AD when it joined the domain.
>Are the other two computers members of the Windows 2003
domain?
>Check AD users and computers and make sure that Dial in
Permission is enabled for each computer account if it
exists.
>
>Do you get any of the following errors when
authentication fails?
>
>"Windows was unable to log you on to the network"
>OR
>"Windows was unable to find a certificate to log you on
to the network"
>
>What is the Authmode key set to for the two PCs that
your are having a problem with?
>Check under
HKLM\Software\Micorosoft\EAPOL\Parameters\General\ Global
>
>
>--------------------
>>From: "Gary" <(E-Mail Removed)>
>>Subject: RE: Cannot authenticate wireless
>>Date: Sun, 25 Apr 2004 23:33:11 -0700
>>
>>I haven't tried them wired. They are some distance
away;
>>hence their need for wireless. I could move one to the
>>router as a test but as previously noted, one of the
>>three client systems can authenticate using the same
>>account. For clarification, I'm only attempting to log
>>onto this particular user account one system at a
time.
>>I.E. The client that does authenticate is logged off
>>when I attempt one of the other 2.
>>
>>As for the "computer account", there are User accounts
>>but I'm not familiar with any need for an account for
the
>>system itself. After all, I didn't create a computer
>>account for the one that does authenticate.
>>
>>Am I missing some information on "computer accounts" in
>>order for them to authenticate?
>>
>>An additional note, the client that does connect was
>>previously wired to the router when the server was
>>running Windows Advanced Server 2000. Not sure if this
>>helps or not.
>>
>>Any suggestions would be greatly appreciated.
>>
>>Thanks
>>Gary
>>
>>
>>
>>
>>>-----Original Message-----
>>>Can these client PCs logon to the domain when wired to
>>the LAN?
>>>Make sure that you have a valid computer account for
>>each PC under Active Directory Users and Computers.
>>>--------------------
>>>>From: "Gary" <(E-Mail Removed)>
>>>>Sender: "Gary" <(E-Mail Removed)>
>>>>Subject: Cannot authenticate wireless
>>>>Date: Tue, 20 Apr 2004 12:11:36 -0700
>>>>
>>>>Please advise.
>>>>I have a wireless router connected to a 2003 server.
>>>>Only 1 of 3 wireless clients can authenticate to the
>>>>domain. When the other 2 log in locally, they have
>>>>wireless access. All three systems are using the
same
>>>>wireless card and OS (Win XP Pro). As a test, I used
>>my
>>>>roaming admin account on all three client systems
with
>>>>the same results. This does not appear to be a
>>profile,
>>>>router or even a server config issue. Rather, a
>>setting
>>>>on the client OS. Any thoughts? Any suggestions
would
>>>>be greatly appreciated. Please email me.
>>>>
>>>>Thanks
>>>>Gary
>>>>
>>>>
>>>
>>>--
>>>Sergio Moreno
>>>Microsoft Windows Networking
>>>
>>>This posting is provided "AS IS" with no warranties,
and
>>confers no rights. Use of included script samples are
>>subject to the terms specified at
>>>http://www.microsoft.com/info/cpyright.htm
>>>
>>>Note: For the benefit of the community-at-large, all
>>responses to this message are best directed to the
>>newsgroup/thread from which they originated.
>>>
>>>.
>>>
>>
>
>--
>Sergio Moreno
>Microsoft Windows Networking
>
>This posting is provided "AS IS" with no warranties, and
confers no rights. Use of included script samples are
subject to the terms specified at
>http://www.microsoft.com/info/cpyright.htm
>
>Note: For the benefit of the community-at-large, all
responses to this message are best directed to the
newsgroup/thread from which they originated.
>
>.
>

Sergio, I moved one of the 2 systems to the server and
connected it to the router. It turns out that even when
wired, I get the exact same results. So this appears to
be a config issue with WinXP Pro. I don't know if you
can assist with this in this group or not. Please advise.

Thanks
Gary

>-----Original Message-----
>No. Server 2003 is a clean install.
>AD does show all three computer accounts but for the 2
>that have yet to authenticate, some of the information
is
>missing from their properties.
>
>All 3 computer accounts (including the one that can
>authenticate) have "Dial In" unchecked (disabled).
>
>I receive no error at all on them when they try to
>authenticate. It just seems to time out after a while
>and then it goes back to the log in screen.
>
>None of the 3 have an Authmode key in the registry.
>Just "(Default)" with no value set.
>
>Thank you for your continued help Sergio!
>Gary
>
>
>>-----Original Message-----
>>Is your Windows 2003 AD domain an upgrade from a
Windows
>2000 AD?
>>A computer account is needed for Wireless connections
in
>Windows 2000, check the next KB:
>>HOW TO: Support Wireless Connections in Windows 2000
>WGID:476
>>ID: 318710
>>http://support.microsoft.com/?id=318710
>>
>>The computer that works had an account created under
>Windows 2000 AD when it joined the domain.
>>Are the other two computers members of the Windows 2003
>domain?
>>Check AD users and computers and make sure that Dial in
>Permission is enabled for each computer account if it
>exists.
>>
>>Do you get any of the following errors when
>authentication fails?
>>
>>"Windows was unable to log you on to the network"
>>OR
>>"Windows was unable to find a certificate to log you on
>to the network"
>>
>>What is the Authmode key set to for the two PCs that
>your are having a problem with?
>>Check under
>HKLM\Software\Micorosoft\EAPOL\Parameters\General \Global
>>
>>
>>--------------------
>>>From: "Gary" <(E-Mail Removed)>
>>>Subject: RE: Cannot authenticate wireless
>>>Date: Sun, 25 Apr 2004 23:33:11 -0700
>>>
>>>I haven't tried them wired. They are some distance
>away;
>>>hence their need for wireless. I could move one to
the
>>>router as a test but as previously noted, one of the
>>>three client systems can authenticate using the same
>>>account. For clarification, I'm only attempting to
log
>>>onto this particular user account one system at a
>time.
>>>I.E. The client that does authenticate is logged off
>>>when I attempt one of the other 2.
>>>
>>>As for the "computer account", there are User accounts
>>>but I'm not familiar with any need for an account for
>the
>>>system itself. After all, I didn't create a computer
>>>account for the one that does authenticate.
>>>
>>>Am I missing some information on "computer accounts"
in
>>>order for them to authenticate?
>>>
>>>An additional note, the client that does connect was
>>>previously wired to the router when the server was
>>>running Windows Advanced Server 2000. Not sure if
this
>>>helps or not.
>>>
>>>Any suggestions would be greatly appreciated.
>>>
>>>Thanks
>>>Gary
>>>
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>Can these client PCs logon to the domain when wired
to
>>>the LAN?
>>>>Make sure that you have a valid computer account for
>>>each PC under Active Directory Users and Computers.
>>>>--------------------
>>>>>From: "Gary" <(E-Mail Removed)>
>>>>>Sender: "Gary" <(E-Mail Removed)>
>>>>>Subject: Cannot authenticate wireless
>>>>>Date: Tue, 20 Apr 2004 12:11:36 -0700
>>>>>
>>>>>Please advise.
>>>>>I have a wireless router connected to a 2003
server.
>>>>>Only 1 of 3 wireless clients can authenticate to the
>>>>>domain. When the other 2 log in locally, they have
>>>>>wireless access. All three systems are using the
>same
>>>>>wireless card and OS (Win XP Pro). As a test, I
used
>>>my
>>>>>roaming admin account on all three client systems
>with
>>>>>the same results. This does not appear to be a
>>>profile,
>>>>>router or even a server config issue. Rather, a
>>>setting
>>>>>on the client OS. Any thoughts? Any suggestions
>would
>>>>>be greatly appreciated. Please email me.
>>>>>
>>>>>Thanks
>>>>>Gary
>>>>>
>>>>>
>>>>
>>>>--
>>>>Sergio Moreno
>>>>Microsoft Windows Networking
>>>>
>>>>This posting is provided "AS IS" with no warranties,
>and
>>>confers no rights. Use of included script samples are
>>>subject to the terms specified at
>>>>http://www.microsoft.com/info/cpyright.htm
>>>>
>>>>Note: For the benefit of the community-at-large, all
>>>responses to this message are best directed to the
>>>newsgroup/thread from which they originated.
>>>>
>>>>.
>>>>
>>>
>>
>>--
>>Sergio Moreno
>>Microsoft Windows Networking
>>
>>This posting is provided "AS IS" with no warranties,
and
>confers no rights. Use of included script samples are
>subject to the terms specified at
>>http://www.microsoft.com/info/cpyright.htm
>>
>>Note: For the benefit of the community-at-large, all
>responses to this message are best directed to the
>newsgroup/thread from which they originated.
>>
>>.
>>
>.
>

if I suggested that you had installed the new server with the same domain
name (but having a different SID) as the old domain but hadn't swung the
client PC's back into a workgroup then back into the domain. Would I be
close?

"Gary" <(E-Mail Removed)> wrote in message
news:710201c43010$d20528e0$(E-Mail Removed)...
> Sergio, I moved one of the 2 systems to the server and
> connected it to the router. It turns out that even when
> wired, I get the exact same results. So this appears to
> be a config issue with WinXP Pro. I don't know if you
> can assist with this in this group or not. Please advise.
>
> Thanks
> Gary
>
> >-----Original Message-----
> >No. Server 2003 is a clean install.
> >AD does show all three computer accounts but for the 2
> >that have yet to authenticate, some of the information
> is
> >missing from their properties.
> >
> >All 3 computer accounts (including the one that can
> >authenticate) have "Dial In" unchecked (disabled).
> >
> >I receive no error at all on them when they try to
> >authenticate. It just seems to time out after a while
> >and then it goes back to the log in screen.
> >
> >None of the 3 have an Authmode key in the registry.
> >Just "(Default)" with no value set.
> >
> >Thank you for your continued help Sergio!
> >Gary
> >
> >
> >>-----Original Message-----
> >>Is your Windows 2003 AD domain an upgrade from a
> Windows
> >2000 AD?
> >>A computer account is needed for Wireless connections
> in
> >Windows 2000, check the next KB:
> >>HOW TO: Support Wireless Connections in Windows 2000
> >WGID:476
> >>ID: 318710
> >>http://support.microsoft.com/?id=318710
> >>
> >>The computer that works had an account created under
> >Windows 2000 AD when it joined the domain.
> >>Are the other two computers members of the Windows 2003
> >domain?
> >>Check AD users and computers and make sure that Dial in
> >Permission is enabled for each computer account if it
> >exists.
> >>
> >>Do you get any of the following errors when
> >authentication fails?
> >>
> >>"Windows was unable to log you on to the network"
> >>OR
> >>"Windows was unable to find a certificate to log you on
> >to the network"
> >>
> >>What is the Authmode key set to for the two PCs that
> >your are having a problem with?
> >>Check under
> >HKLM\Software\Micorosoft\EAPOL\Parameters\General \Global
> >>
> >>
> >>--------------------
> >>>From: "Gary" <(E-Mail Removed)>
> >>>Subject: RE: Cannot authenticate wireless
> >>>Date: Sun, 25 Apr 2004 23:33:11 -0700
> >>>
> >>>I haven't tried them wired. They are some distance
> >away;
> >>>hence their need for wireless. I could move one to
> the
> >>>router as a test but as previously noted, one of the
> >>>three client systems can authenticate using the same
> >>>account. For clarification, I'm only attempting to
> log
> >>>onto this particular user account one system at a
> >time.
> >>>I.E. The client that does authenticate is logged off
> >>>when I attempt one of the other 2.
> >>>
> >>>As for the "computer account", there are User accounts
> >>>but I'm not familiar with any need for an account for
> >the
> >>>system itself. After all, I didn't create a computer
> >>>account for the one that does authenticate.
> >>>
> >>>Am I missing some information on "computer accounts"
> in
> >>>order for them to authenticate?
> >>>
> >>>An additional note, the client that does connect was
> >>>previously wired to the router when the server was
> >>>running Windows Advanced Server 2000. Not sure if
> this
> >>>helps or not.
> >>>
> >>>Any suggestions would be greatly appreciated.
> >>>
> >>>Thanks
> >>>Gary
> >>>
> >>>
> >>>
> >>>
> >>>>-----Original Message-----
> >>>>Can these client PCs logon to the domain when wired
> to
> >>>the LAN?
> >>>>Make sure that you have a valid computer account for
> >>>each PC under Active Directory Users and Computers.
> >>>>--------------------
> >>>>>From: "Gary" <(E-Mail Removed)>
> >>>>>Sender: "Gary" <(E-Mail Removed)>
> >>>>>Subject: Cannot authenticate wireless
> >>>>>Date: Tue, 20 Apr 2004 12:11:36 -0700
> >>>>>
> >>>>>Please advise.
> >>>>>I have a wireless router connected to a 2003
> server.
> >>>>>Only 1 of 3 wireless clients can authenticate to the
> >>>>>domain. When the other 2 log in locally, they have
> >>>>>wireless access. All three systems are using the
> >same
> >>>>>wireless card and OS (Win XP Pro). As a test, I
> used
> >>>my
> >>>>>roaming admin account on all three client systems
> >with
> >>>>>the same results. This does not appear to be a
> >>>profile,
> >>>>>router or even a server config issue. Rather, a
> >>>setting
> >>>>>on the client OS. Any thoughts? Any suggestions
> >would
> >>>>>be greatly appreciated. Please email me.
> >>>>>
> >>>>>Thanks
> >>>>>Gary
> >>>>>
> >>>>>
> >>>>
> >>>>--
> >>>>Sergio Moreno
> >>>>Microsoft Windows Networking
> >>>>
> >>>>This posting is provided "AS IS" with no warranties,
> >and
> >>>confers no rights. Use of included script samples are
> >>>subject to the terms specified at
> >>>>http://www.microsoft.com/info/cpyright.htm
> >>>>
> >>>>Note: For the benefit of the community-at-large, all
> >>>responses to this message are best directed to the
> >>>newsgroup/thread from which they originated.
> >>>>
> >>>>.
> >>>>
> >>>
> >>
> >>--
> >>Sergio Moreno
> >>Microsoft Windows Networking
> >>
> >>This posting is provided "AS IS" with no warranties,
> and
> >confers no rights. Use of included script samples are
> >subject to the terms specified at
> >>http://www.microsoft.com/info/cpyright.htm
> >>
> >>Note: For the benefit of the community-at-large, all
> >responses to this message are best directed to the
> >newsgroup/thread from which they originated.
> >>
> >>.
> >>
> >.
> >

Quite possibly, yes.
What are you thinking?



>-----Original Message-----
>if I suggested that you had installed the new server
with the same domain
>name (but having a different SID) as the old domain but
hadn't swung the
>client PC's back into a workgroup then back into the
domain. Would I be
>close?
>
>"Gary" <(E-Mail Removed)> wrote in message
>news:710201c43010$d20528e0$(E-Mail Removed)...
>> Sergio, I moved one of the 2 systems to the server and
>> connected it to the router. It turns out that even
when
>> wired, I get the exact same results. So this appears
to
>> be a config issue with WinXP Pro. I don't know if you
>> can assist with this in this group or not. Please
advise.
>>
>> Thanks
>> Gary
>>
>> >-----Original Message-----
>> >No. Server 2003 is a clean install.
>> >AD does show all three computer accounts but for the 2
>> >that have yet to authenticate, some of the information
>> is
>> >missing from their properties.
>> >
>> >All 3 computer accounts (including the one that can
>> >authenticate) have "Dial In" unchecked (disabled).
>> >
>> >I receive no error at all on them when they try to
>> >authenticate. It just seems to time out after a while
>> >and then it goes back to the log in screen.
>> >
>> >None of the 3 have an Authmode key in the registry.
>> >Just "(Default)" with no value set.
>> >
>> >Thank you for your continued help Sergio!
>> >Gary
>> >
>> >
>> >>-----Original Message-----
>> >>Is your Windows 2003 AD domain an upgrade from a
>> Windows
>> >2000 AD?
>> >>A computer account is needed for Wireless connections
>> in
>> >Windows 2000, check the next KB:
>> >>HOW TO: Support Wireless Connections in Windows 2000
>> >WGID:476
>> >>ID: 318710
>> >>http://support.microsoft.com/?id=318710
>> >>
>> >>The computer that works had an account created under
>> >Windows 2000 AD when it joined the domain.
>> >>Are the other two computers members of the Windows
2003
>> >domain?
>> >>Check AD users and computers and make sure that Dial
in
>> >Permission is enabled for each computer account if it
>> >exists.
>> >>
>> >>Do you get any of the following errors when
>> >authentication fails?
>> >>
>> >>"Windows was unable to log you on to the network"
>> >>OR
>> >>"Windows was unable to find a certificate to log you
on
>> >to the network"
>> >>
>> >>What is the Authmode key set to for the two PCs that
>> >your are having a problem with?
>> >>Check under
>>
>HKLM\Software\Micorosoft\EAPOL\Parameters\General \Global
>> >>
>> >>
>> >>--------------------
>> >>>From: "Gary" <(E-Mail Removed)>
>> >>>Subject: RE: Cannot authenticate wireless
>> >>>Date: Sun, 25 Apr 2004 23:33:11 -0700
>> >>>
>> >>>I haven't tried them wired. They are some distance
>> >away;
>> >>>hence their need for wireless. I could move one to
>> the
>> >>>router as a test but as previously noted, one of the
>> >>>three client systems can authenticate using the same
>> >>>account. For clarification, I'm only attempting to
>> log
>> >>>onto this particular user account one system at a
>> >time.
>> >>>I.E. The client that does authenticate is logged
off
>> >>>when I attempt one of the other 2.
>> >>>
>> >>>As for the "computer account", there are User
accounts
>> >>>but I'm not familiar with any need for an account
for
>> >the
>> >>>system itself. After all, I didn't create a
computer
>> >>>account for the one that does authenticate.
>> >>>
>> >>>Am I missing some information on "computer accounts"
>> in
>> >>>order for them to authenticate?
>> >>>
>> >>>An additional note, the client that does connect was
>> >>>previously wired to the router when the server was
>> >>>running Windows Advanced Server 2000. Not sure if
>> this
>> >>>helps or not.
>> >>>
>> >>>Any suggestions would be greatly appreciated.
>> >>>
>> >>>Thanks
>> >>>Gary
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>>-----Original Message-----
>> >>>>Can these client PCs logon to the domain when wired
>> to
>> >>>the LAN?
>> >>>>Make sure that you have a valid computer account
for
>> >>>each PC under Active Directory Users and Computers.
>> >>>>--------------------
>> >>>>>From: "Gary" <(E-Mail Removed)>
>> >>>>>Sender: "Gary" <(E-Mail Removed)>
>> >>>>>Subject: Cannot authenticate wireless
>> >>>>>Date: Tue, 20 Apr 2004 12:11:36 -0700
>> >>>>>
>> >>>>>Please advise.
>> >>>>>I have a wireless router connected to a 2003
>> server.
>> >>>>>Only 1 of 3 wireless clients can authenticate to
the
>> >>>>>domain. When the other 2 log in locally, they
have
>> >>>>>wireless access. All three systems are using the
>> >same
>> >>>>>wireless card and OS (Win XP Pro). As a test, I
>> used
>> >>>my
>> >>>>>roaming admin account on all three client systems
>> >with
>> >>>>>the same results. This does not appear to be a
>> >>>profile,
>> >>>>>router or even a server config issue. Rather, a
>> >>>setting
>> >>>>>on the client OS. Any thoughts? Any suggestions
>> >would
>> >>>>>be greatly appreciated. Please email me.
>> >>>>>
>> >>>>>Thanks
>> >>>>>Gary
>> >>>>>
>> >>>>>
>> >>>>
>> >>>>--
>> >>>>Sergio Moreno
>> >>>>Microsoft Windows Networking
>> >>>>
>> >>>>This posting is provided "AS IS" with no
warranties,
>> >and
>> >>>confers no rights. Use of included script samples
are
>> >>>subject to the terms specified at
>> >>>>http://www.microsoft.com/info/cpyright.htm
>> >>>>
>> >>>>Note: For the benefit of the community-at-large,
all
>> >>>responses to this message are best directed to the
>> >>>newsgroup/thread from which they originated.
>> >>>>
>> >>>>.
>> >>>>
>> >>>
>> >>
>> >>--
>> >>Sergio Moreno
>> >>Microsoft Windows Networking
>> >>
>> >>This posting is provided "AS IS" with no warranties,
>> and
>> >confers no rights. Use of included script samples are
>> >subject to the terms specified at
>> >>http://www.microsoft.com/info/cpyright.htm
>> >>
>> >>Note: For the benefit of the community-at-large, all
>> >responses to this message are best directed to the
>> >newsgroup/thread from which they originated.
>> >>
>> >>.
>> >>
>> >.
>> >
>
>
>.
>