Re: Wireless network w/ SBS
- From: "Robert R Kircher, Jr." <rkircher@xxxxxxxxxxxxxxxx>
- Date: Wed, 1 Nov 2006 10:06:52 -0500
"Owen Williams [SBS MVP]" <Owen@xxxxxxxxxxxxxxxxxx> wrote in message
news:MPG.1fb27b99a5c1b25f989946@xxxxxxxxxxxxxxxxxxxxx
In article <#2nspeY$GHA.1464@xxxxxxxxxxxxxxxxxxxx>,
rkircher@xxxxxxxxxxxxxxxx says...
That I can tell there are no server related errors. However, here is
what I
see on the client.
Are there entries in the IAS logs for SUCCESSFUL authentications? By
default the logs are in C:\Windows\System32\LogFiles. Please post some
samples (names changed to preserve the network's confidentiality).
I will look.
From this list, the most likely for your case seem to be:
* Wireless NIC driver (update or reinstall)
Updated
* Firewall - client (esp. if 3rd-party)
None installed, Fresh install using RIS.
* Firewall - server (reminder: Win Svr 2003 firewall must NOT be enabled
on SBS)
Not enabled and I've also temporarily disables the Firewall GPOs so the
client also has the MS FW disabled.
* Need to rejoin PC to domain [disjoin, delete computer account, add
computer account, rejoin to domain with /ConnectComputer using the WIRED
connection]
Will try this.
* Wireless PC BIOS (update to latest)
Will check
* "Wireless LAN doesn't support Zero Configuration and the NIC software
doesn't load until after logon so it cannot connect to the DC until
after the logon to the local workstation." [If this is the reason, it
could explain why you were having problems with WPA-PSK.]
I am about 99% certian it does. I recall reading something in the newest
driver down load about it. The trouble PC is using a Dell Truemobile 1450
USB NIC
There are many other possibilities in the list.
There is also a suggestion to enable this GPO setting:
Computer Configuration\Administrative Templates\System\Logon\
[Always wait for the network at computer startup and logon]
Already did that.
I _do_ enable this (in the "Small Business Server Client Computer" GPO)
on all the networks I manage - even when they do not use wireless -
because it makes GPO processing more reliable. You will need to use a
wired connection and you should restart the PC _twice_ to ensure the GPO
is applied. (After the setting has been applied, the double restarts
should not be required.)
Understood, and you will need to proceed as you need to given your
requirements. Meanwhile, I would like to confirm that you have
carefully verified all of your settings against those in my doc. And I
would still like to know the WAP vendor, model, and firmware level.
Ditto for the wireless NICs.
WAP vendor. Netgear WAG102 w/ latest firmware, 2.05
Again, thanks for all your help. I have a few other things I can do to the
system that are not dependent on this working, and frankly I may be able to
get away w/o having computer level policies but it would be nice to get this
working correctly.
Out of curiosity, what NICs do you use for PCs and laptops. I usualy use
Intel for laptops but haven't bought any nics for wireless PCs before.
Thanks again
--
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: Owen Williams [SBS MVP]
- Re: Wireless network w/ SBS
- From: Robert R Kircher, Jr.
- Re: Wireless network w/ SBS
- From: Dave Nickason [SBS MVP]
- Re: Wireless network w/ SBS
- From: Robert R Kircher, Jr.
- 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
- Prev by Date: Re: Possible to use another email address for replies?
- Next by Date: Re: ????SATA or SCSI????
- Previous by thread: Re: Wireless network w/ SBS
- Next by thread: Re: Wireless network w/ SBS
- Index(es):
Relevant Pages
|