We started using the wireless network at our Company but users are unable to connect to network mapped drives when using wireless ,the Wired User can see and use map drive PLEASEI NEED HELP TO SOLVE THIS ISSUE
Wireless solution items:
20 WAP 1020 s
Security is WPA2 AES encryp. And TLS authentication
You gave us no details on how your clients are configured.
If you are runnning Windows clients, then you need to enable machine authentication ON THE WIRELESS CLIENT and on ACS. Since you are using TLS, you also need to have a machine certificate on the computer.
Machine authentication will allow the wireless computer to connect to the wireless network BEFORE the user logs on. In this way, login scripts and drive mappings will take place the same way they would with a wired connection.
I believe you can search Cisco.com for an article that talks about the ACS and client settings for machine auth.
Well the problem when using the wireless when booting up is that the wireless utilities don't start until windows boot up. So if you look at when you are wired and after you login, your network scripts runs. But on wireless, they scripts will run, but fail since there is no network connection.
There is a feature that waits for a wireless connection before it gives you the login prompt. Windows Zero does not have this in XP, but does in Vista. Intel ProSet and IBM's Access Connection along with other 3rd party (not free) utilities has this feature.
Windows XP SP2 (with the patch) and SP3 support computer authentication with WZC. There is a check box on the Authentication tab labeled "Authenticate as computer when computer information is available". This will do the trick. For this to work for the OP, they must have machine certs installed and the ACS must be configured to support Machine Authentication.
So you are saying with SP3 or the patch, Windows will aquire a network connection then proceed with the login? Scripts usually are set to run after the login is processed even though the user can't login into the domain since they have no network connection yet. If that does work with scripts then that is something good to know.
Actually, you don't even need the patch (but I recommend the patch for folks running SP2 - http://support.microsoft.com/kb/917021). I think you can even do this with out of the box XP (with no Service Pack).
With the proper configuration, the XP machine can, and will, connect to the wireless network at boot time (before the user logs on). With the connection present, the user is authenticated against AD (instead of using cached credentials), and login scripts will run.
Make sure you have broadcast forwarding enabled on the controller and that your clients are giving the IP address of the WINS server. If you don't use a WINS a PC could become the master browser and if that PC is a wireless client latency will become an issue.