Re: Wireless network w/ SBS

Dave I was thinking along the same lines except that both workstations
actual do authenticate prior to log in but very late in the start up
process.

In any event I'm going to go through the process over again and see if there
are any mistakes in my config. If I find anything I'll report it back here.


--

Rob
"A disturbing new study finds that studies are disturbing"



"Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23yVdCA5$GHA.4496@xxxxxxxxxxxxxxxxxxxxxxx
A little out of my depth, half asleep and barely thinking, I'm wondering if
this is an issue with the certificate? I'm almost ruling out hardware as
authentication is happening once the user logs in. So is it possible that
the computer certificate is not installed properly, IAS is configured to
use the wrong cert, or something related? It can't authenticate with the
computer certificate for whatever reason, but can with the user?


"Owen Williams [SBS MVP]" <Owen@xxxxxxxxxxxxxxxxxx> wrote in message
news:MPG.1fb51d0586e05fe298994a@xxxxxxxxxxxxxxxxxxxxx
In article <uOcqSGw$GHA.2328@xxxxxxxxxxxxxxxxxxxx>,
rkircher@xxxxxxxxxxxxxxxx says...

I picked up a Linksys WAP54P and the results are exactly the same. I'm
going to go over you document (the new one) step by step again and see
if I
missed something. So far tonight, working on GPOs, I've only found one
setting that was computer level that may cause me trouble. Most of my
policies are user lever.

Good idea to carefully review your settings v. my docs. Since there was
no change with a totally different WAP, the problem is most likely with
the wireless NIC(s) [hardware, firmware, and/or drivers] and/or a
configuration error somewhere. Perhaps you can return the LinkSys for a
refund?

Over the past 18 months, the vast majority of problems getting the
methodology to work have been traced to an incorrect setup somewhere.
[I'm not immune - I had missed a few things with my own network at the
beginning!] The remainder - a distinct minority - have been caused by
wireless device issues (e.g., firmware or drivers) and, in one case that
I know of, a bug in ISA2004 that may manifest in a minority of SBS
installations.

RE: So far tonight, working on GPOs, I've only found one setting that
was computer level that may cause me trouble. Most of my policies are
user lever.

I presume you are talking about non-wireless policies that may be
causing you problems. Just to be clear ... ALL of the wireless policies
I document are in "Computer Configuration" and NONE of them are in "User
Configuration".

-- Owen Williams (SBS MVP)




.

Relevant Pages

  • Re: Basic Authentication + IIS 5 + Windows 2000 + Frontpage 2002 = failure?
    ... This posting is provided “AS IS” with no warranties, and confers no rights. ... |> In my setup, I cannot log in to the local computer, only the domain. ... |>> extra bit added to the configuration of this puzzle, ... |>> authenticate, and can use the local administrator account to ...
    (microsoft.public.inetserver.iis.security)
  • Re: Searching child OUs for authentication
    ... Having implemented a similar configuration, I have encountered the same limitation that you refer to. ... I am unable to authenticate users who are outside of a single top-level OU in AD. ... I have a quick question on apache configuration when attempting to ...
    (RedHat)
  • ssh from user to RBAC role
    ... viable configuration? ... the role yet ssh fails to authenticate using the keys ... Yet ssh fails from user to role, am I missing something here or is it ... Although we routinely screen for viruses, ...
    (SunManagers)
  • Authenticating using lower case domain/realm
    ... I have successfully configured ubuntu machines to authenticate to a active ... directory running windows 2k. ... The realm is ... krb5-config 1.19 Configuration files for Kerberos Version 5 ...
    (comp.protocols.kerberos)
  • security policy
    ... policy configured with some policies like the account ... I analized the policies with the Security Configuration ...
    (microsoft.public.win2000.security)