Re: Wireless network w/ SBS
- From: "Robert R Kircher, Jr." <rkircher@xxxxxxxxxxxxxxxx>
- Date: Thu, 2 Nov 2006 23:36:02 -0500
"Owen Williams [SBS MVP]" <Owen@xxxxxxxxxxxxxxxxxx> wrote in message
news:MPG.1fb44c0ad14f12409896d6@xxxxxxxxxxxxxxxxxxxxx
In article <##tQyAs$GHA.1224@xxxxxxxxxxxxxxxxxxxx>,
rkircher@xxxxxxxxxxxxxxxx
says...
To be honest I'm not sure I'm following you w/ the log issues. Could be
that I'm just too fried. ;-) If it would be easier to review my log I
can
email it directly to you.
No, the log info you provided was fine.
My point was that comparing your log entries with those from two other
networks
which are working properly shows some significant differences which do not
appear to be explained by you using different hardware and IP addresses.
Frankly, I think the issue has something to do with initial communication
with the DC. Every indication is that the workstation can not get to the
DC
at startup. I tried setting a fixed IP to see if this would solve the
issue
but it didn't. I can ping the workstation much sooner in the startup
process but it still gives me the 1054 error. Most of what I read
regarding
the error seems to indicate a DNS issue but this only happens when the PC
is
connecting via wireless not hardwire. I'm wondering if this WAP somehow
isn't allowing the traffic at initial connection or if there is some sort
of
reg value that can make the client wait until it can communicate similar
to
the slow connection GPO settings.
Something is getting through since IAS is logging. But (as noted above)
what
is being logged is not typical for a working 802.1x/EAP-TLS wireless
network.
Out of curiosity, what WAPs are you using that support this config.
Although I'd rather not go out and buy another WAP I have a best buy just
up
the street and don't mind getting something else to see if I can make
this
work. In the mean time user lever GPOs work so I'm going to complete
that
side of the setup and deploy the system.
Your easy and fairly inexpensive choice for a test would be a LinkSys
WRT54g -
Best Buy should have plenty of those. It's a router but it's easy to
configure
as a WAP:
* Disable DHCP
* Plug the Ethernet cable into one of the LAN jacks, not the WAN/Internet
jack.
My slight caveat is that it will probably be a Version 5. Versions 1-4
were
Linux-based. Version 5 uses a different embedded OS. But it should be
functionally equivalent.
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.
--
Rob
"A disturbing new study finds that studies are disturbing"
.
- Follow-Ups:
- Re: Wireless network w/ SBS
- From: Owen Williams [SBS MVP]
- Re: Wireless network w/ SBS
- References:
- Re: Wireless network w/ SBS
- From: Dave Nickason [SBS MVP]
- Re: Wireless network w/ SBS
- From: Owen Williams [SBS MVP]
- Re: Wireless network w/ SBS
- From: Robert R Kircher, Jr.
- Re: Wireless network w/ SBS
- From: Owen Williams [SBS MVP]
- Re: Wireless network w/ SBS
- From: Robert R Kircher, Jr.
- Re: Wireless network w/ SBS
- From: Owen Williams [SBS MVP]
- Re: Wireless network w/ SBS
- From: Robert R Kircher, Jr.
- Re: Wireless network w/ SBS
- From: Owen Williams [SBS MVP]
- Re: Wireless network w/ SBS
- From: Robert R Kircher, Jr.
- Re: Wireless network w/ SBS
- From: Owen Williams [SBS MVP]
- Re: Wireless network w/ SBS
- From: Robert R Kircher, Jr.
- Re: Wireless network w/ SBS
- From: Owen Williams [SBS MVP]
- Re: Wireless network w/ SBS
- Prev by Date: Re: RWW - Application Server Disappears
- Next by Date: Re: RWW - Application Server Disappears
- Previous by thread: Re: Wireless network w/ SBS
- Next by thread: Re: Wireless network w/ SBS
- Index(es):
Relevant Pages
|
Loading