BenShortland

I have ripped apart the netbook and sourced another mini pci-ex wireless/bluetooth for it. It is on order and we will wait and see what happens. Thank you all for your help. Ben

We have had a full site audit with regards to the wireless and yes it does show alot of areas for improvement. However a Lenovo R60 Laptop boots and goes striaght in, even with 30 netbooks also in the room trying to log in at the same time. There are no issues with any of the other laptops in the block. Everything else works like a dream (well as good as they can be being R60 Lenovo's and being old). The point i am trying to make is that if it was a problem with the infrastructure it would happen to all wireless hardware not just the netbook's. If it was a traffic issue a lenovo would have the same issue logging in if 30 netbooks beside it were also trying to log in (except if the other laptops were using A, becuase the netbook's wireless adapter doesnt support A however I have looked how many laptops are connecting using A and they are next to none).Thus eliminating infrastructure and pointing to only the netbook hardware. Updated drivers do not work, neither does a different os.No event log errors. To be honest I have been in Networking / Hardware for 12 years, and I would like to think I know what I am doing, I rule it down to the hardware not being adiquate for the domain ( as netbooks arnt made for an enterprise) but I am struggling to find the reason why and if it can be corrected.

Generally logon time is normally quicker ( on this instance I was using an account which hadn't logged onto the netbook before.Pupils have mandatory profiles. All I am saying is that via wireless they take a lot longer than wired.I have tried the netbooks in a different block and same issue. In reponce to the local option being a solution it isn't viable as whe have 1200 different users (pupils) using the netbooks all with their own logins.

All the laptops are in a lapsafe trolly aprox 60. I am 90% sure its the modules in the netbooks but bar from replacing all the modules in them I can't see where to go from here. The netbooks are pupil clients and when a class of 10 -30 boots them all attempt to log in it takes an extremely log time to log in. No unusal activity on the AP or switch either.

Ethernet is alot quicker (4 minutes) and when a single N150 Plus is attempting to authenticate it's fine, but any more than 10 and it causes the slow login. After looking further into this the Wireless Module doesn't support A (of which our switches are set to use A and G due to load). I am looking further into this. Samsung also recommend using the manufacturer software (atheros in this case) opposed to Zero Conf and the default Windows Wireless Manager due to issues. I am also going to try a Wireless G dongle in the netbook to see if that will cause the same results.

We currently have 30 Samsung N150 Plus Netbooks of which take 15 - 20 minutes to authenticate against the domain and log on. Currently running 802.11g on 3 channels. All other laptops log on instantly. There are no errors in the logs and we have tried the following to try and find the source of the issue... Checked Logs - No issues Booted them up in a different area of the site which is known working on wireless Cleared all profiles Changed o/s (from XP Pro to 7 Ent) Checked the managed wireless switch logs Next step is to look for updated drivers and try on ethernet. Will post results Anyone have any ideas on the matter?