Ruth
Fri Mar 28 14:43:51 PDT 2008
Owen,
Thank you for your advice - indeed i am inclined to come to the same
conclusion - that or it's getting interference from somewhere - it's a
catering firm so could be anything. Most likely suspect is very old
cordless phones. Could also be the fact that it's a fairly old router ..
plastic and tacky!
The WAP is on top of the server, under a desk, however the laptops are both
within 10m of the WAP - literally just a desk or two apart - so I wouldn't
have thought it would be weak signal strength (they're both getting 5/5
bars).
I might try changing the wifi channel, and see if this makes any difference.
I know it's picking up the GPO's ok as I've checked in the event viewer and
I can see the certificate there. For now I've told them to use a wire when
in the office, as I am away for a week, but I will want to resolve this asap
on my return!
Many thanks to everyone for your help with these issues, it makes things so
much easier to have a pool of people who've been there and done that
numerous times before!
Kind Regards,
Ruth Cheesley
"Owen Williams [SBS MVP]" <Owen@NoSpam_CVTCLLC.com> wrote in message
news:MPG.225726088e72adcf9896b3@news.microsoft.com...
> In article <e7AiZwFkIHA.4536@TK2MSFTNGP06.phx.gbl>, "Ruth Cheesley"
> <newsgroup<at>suffolkcomputerservices<dot>co(dot)uk> says...
>
>> Many thanks for the information. I checked the logs and it is receiving
>> auto-enrollment successfully. I followed the instructions to the letter
>> (they were brilliant, very well written and covered every single check
>> box
>> unlike some tutorials/guides I've used in the past!). I have the laptop
>> wired at the moment. I've set it to WPA TKIP (the router/AP doesn't
>> support
>> AES).
>>
>> I am currently working back through the documentation to check that I did
>> not miss anything or incorrectly enter the info.
>
> Hello, Ruth. Thank you for the kind words.
>
> As Dave says, the most common problem when the configuration does not
> work is a wrong setting somewhere. As you know, there are a LOT of
> settings and they all have to be exactly right. It's easy to make a
> mistake - been there, done that! So that's the first thing to check.
>
> If you verify every setting and it still doesn't work ... I have on rare
> occasions seen cases where authentication failures occur when the
> wireless signal is not of sufficient strength or quality. For example, I
> had a client in an older building with many thick plaster walls, metal
> duct work, and similar. With the wireless computer in the same room as
> the WAP, it authenticated almost immediately. When I moved the computer
> a few offices down (separated by several walls/doors), I could not get
> the PC to authenticate to save my life. Long story short, the client
> ended up running an Ethernet cable.
>
> I had a similar situation in my own home (in which I run an SBS using
> the certificate-based security). My laptop worked fine in the house but
> was flakey outside on my deck. The house has aluminum siding and the
> signal strength was MUCH weaker outside. I had to fiddle with the WAP
> settings (mostly trying single-mode 802.11g rather than mixed g+n) to
> get that working.
>
> Signal strengths can vary greatly with only slight reorientations of the
> wireless computer and/or WAP. I was setting up an in-home wireless
> network for a client. Sitting in a swivel chair with the laptop in my
> lap, the signal strength was Very Good to Excellent ... until I swiveled
> 90 degrees, when it dropped to Poor!
>
> So, don't give up and don't be afraid to "tweak" things a bit.
>
> -- Owen Williams [SBS MVP]