Thanks both for help.
@ rseiler: right now, we are using the 3com WLAN Manager, which is ok for our current setup. But I already tried to change 1 testing workstation settings to several types of encryption & PEAP authentication, without success. When the computer starts no IP is assigned by DHCP and users are able to initally work offline. After somebody with local/cached profile logs on, the 3Com WLan manager connects and after that everything works "fine". But this is not acceptable. The 3Com WLAN Manager has several setttings for pre-logon, after-machine-bootup options, but I didnt notice any change after trying all of them in several combinations. But this particular problem is probably better suited for 3Com forums/support.
I also tried Microsoft client, which has limited options. The problem with W2K is that no wireless settings can be changed within microsoft supplicant. What I achieved here is to first set 3Com WLAN Manager for correct encryption settings, SSID etc. then disabling it and using Microsoft's supplicant instead. This works really well, but I have tested it only with dynamic WEP + PEAP + IAS W2K as I read somewhere in Cisco documents that W2K has no direct support for higher encryption.
As for why still Windows 2000 in year 2007 - its company policy, which is set by central IT department and actually W2K is enough for almost everything we need. Some of the workstations we use for only 1 specific task which doesn't require much horsepower and the HW of these machines couldnt cope with XP's demands. Buying new machines for such task doesn't sound right. We will have to go with XP though, because new versions of applications we use are just plainly requesting XP during install.
Are there any 3rd party PEAP supplicants which also support machine auth for Windows platform, like Funk, Aegis(probably Cisco now :-) ) ?
Again thanks for your help.
