Re: Wireless network w/ SBS

In article <OcfDgvT$GHA.1220@xxxxxxxxxxxxxxxxxxxx>,
gwdibble@xxxxxxxxxxxxxxxxxxxxxx says...

I set the Network Location Awareness service to Automatic startup and
rebooted the wireless PC. At that point, everything works including RDP and
remote management. This tells me that the laptop is applying group policy
before it knows it's connected to the domain. I suppose that could be
because it takes longer to establish the wireless connection, but I suspect
it's just that NLA isn't starting soon enough, and setting it to Automatic
remedies that. That's a problem I've seen on several desktops as well. If
you're interested in how this interesting technology works, see
http://www.microsoft.com/technet/community/columns/cableguy/cg0504.mspx

Well, Dave, this is a(nother) case where I learned something from you! I guess
I've been lucky with my own network and my clients that I've never had to set
NLA to Automatic. But if I run into a problem, now I know!

Unfortunately, that doesn't answer Robert's problem with DHCP. Owen?

Dave and I - along with many others - having been using this approach for a
long time now. We can assure you that once it is properly configured, it is
wired-equivalent. Failure to get DHCP until after a login sounds like a
wireless GPO misconfiguration -OR- the wireless GPO did not actually get
applied to the PC. Try this:

[1] Check the server event logs for IAS errors. Check the IAS logs for any
errors.

[2] On the server, verify "Computer Wireless LAN Policy" (or whatever you
called it) is linked and enabled at the proper place in AD. It should be
linked at MyBusiness\Computers -OR- at the domain.

[3] Edit "Computer Wireless LAN Policy" and navigate to Computer Configuration
| Windows Settings | Security Settings | Wireless Network (IEEE 802.11)
Policies. Open "801.1x Computer Certificate Wireless LAN Policy" (or the name
you used) properties. Please CAREFULLY compare ALL of the settings to what's
in my document. GPO configuration is the most complex part of the
configuration. There are a LOT of settings and it is easy to make a mistake or
miss something. Doing so has been the most common cause of problems with the
configuration. [In fact, it's a good idea to review all of your configuration
from start to finish.]

[4] When you have completed [2], go to the wireless PC and open the wireless
network properties. Verify that they are IDENTICAL to the GPO settings. If
not, the GPO was not properly applied during the wired connection. Disable the
wireless NIC, make a wired connection, and restart the PC. Ensure GPOs are
being applied (check the event logs). Then, disconnect wired, enable wireless,
and check the settings again. When you have confirmed the PC's wireless
settings match the GPO's (and my document's), restart the PC and see if the
problem is fixed, e.g., you can PING the wireless computer after it boots but
before someone logs in. [One way to verify the wireless GPO has been applied
is to try changing a setting for the secure SSID. If the settings are
controlled by GPO, you will get an error message when you try apply the
change.]

If it is still not working, please post back: [a] a simple network diagram and
[b] the make, model, and firmware revision of your WAP. I have talked to a
couple of people who have had problems with certain WAPs. Once the WAP was
replaced, their problems went away.

I also agree with Dave that you should check your firewall settings, especially
if you are using a 3rd-party firewall such as ZoneAlarm (which I do).
ZoneAlarm tries to prompt you when it encounters a "new" network and does not
assume the network is trusted. Prior to a login, it is not possible to see or
respond to such a prompt. I had to manually create a "placeholder" trusted
network matching my LAN addressing plan to get around this.

-- Owen Williams [SBS MVP]
.

Relevant Pages

  • Re: Wireless network w/ SBS
    ... Windows cannot obtain the domain controller name for your computer network. ... GPO items nor will it do computer lever installs from GPO. ... rebooted the wireless PC. ... Please CAREFULLY compare ALL of the settings to ...
    (microsoft.public.windows.server.sbs)
  • Where is my wireless network???
    ... Router without it's USB Adapter and Installation CD. ... Firewall Settings Enabled ... I've tried the "Setup a wireless network" wizzard ...
    (alt.internet.wireless)
  • Wireless EAP - GPO Problem
    ... I have configured the wireless GPO. ... 802.1x with IAS and using EAP for authentication. ... with a network cable attached. ...
    (microsoft.public.windows.server.networking)
  • Re: Wireless connection problem from XP Pro SP2 to SBS 2003
    ... As long as you're sure the certificate is properly installed on the PC, I guess the priority would be to get wireless working, then worry about the auto enrollment later. ... compare all the settings between the non-working PC and the one that works. ...
    (microsoft.public.windows.server.sbs)
  • Re: Wireless network w/ SBS
    ... Windows cannot obtain the domain controller name for your computer network. ... Wireless NIC driver ... There is also a suggestion to enable this GPO setting: ... Ditto for the wireless NICs. ...
    (microsoft.public.windows.server.sbs)
Loading