The settings on these Realteks is very sparse.
Got
802.11d - Disable/Enable - Disabled
Beacon Interval - 100
PSPXlinkMode - Disable/Enable - Disabled
Wireless Mode 802.11b/802.11b/g 802b/g/n - set to 80211b/g/n
and thats it
regards
Simon

The settings on these Realteks is very sparse.
Got
802.11d - Disable/Enable - Disabled
Beacon Interval - 100
PSPXlinkMode - Disable/Enable - Disabled
Wireless Mode 802.11b/802.11b/g 802b/g/n - set to 80211b/g/n
and thats it
regards
Simon

And although I've had the N130s out all this afternoon - I couldn't get them to fail
regards
Simon

The latest driver from the realtek site is downloading at 25KBS - its like the old days![]()

Well - that was a great experience - file eventually downloaded - ran the setup -rebooted and the driver is still showing its on version 1678.0.1019.2009 - which is what it was beforehand
So I tried just doing the Update Driver on the Driver tab and its said that I had the most up to date-
this is despite the download zip file having the version number 1085.23.1230.2009 in its name
Time to give up for today
Simon
Hi Simon, I came accross this forum and was very interested! I have just rolled out 30 N130's with Realteck Driver.
As you commented " you watched the wireless drop out " this happens to us all of the time.
We have several access points in the area Netgears 102's. We thought it would be that so we upgraded the AP's to Netgears 302's.
We then thought it was the cisco switches so we connected the server, internet and acces points onto a single Netgear switch bypassing the entire school infrustructure. Still failed! We have also tried updating to the latest wireless driver.
This is a standard Windows 2003 Network. The Netbooks just drop out willi nilly when they want to !
James

Sugar![]()
Do ypu still have your problems ? What AP where you using ? Also version of driver ?
Many thanks
James

Hi James
Just to save me some re-typing - check all the info on my setup versions in previous posts in this thread
Also got another thread
Anyone using Samsung N130s
which I started in case the problems were not just confined to Ruckus and N130s (Which is your case)
Could you post your realtek driver version over there please?
regards
Simon
BTW to get our Tosh with realtek adapters to work we did the following:
Roaming Aggression: Lowest
802.11d: Enabled
TX Power: Max
We also had to alter our APs with Channelization set to 20 and I have to manually set Power on some APs. Its kinda funny that i've had to setup each ap individually. We have a problem with here with something causing interference with some channels so i have to setup each ap on a specific channel manually.

I'm not getting anywhere wit hdriver update.
I uninstalled the wireless from device manager and re-installed using lastest package from realtek site which is called
RTL8191_8192_SE_WindowsDriver_1085.23.1230.2009.F0 049.P0406_ISS_1.00.0143.L
but when I look in driver details when I install it its shows
Driver Version: 1678.0.1019.2009
which is exactly the same as what they came with.
So not winning on that front
please let me know your driver versions
regards
Simon
Im sure we got our 'latest' drivers from somewhere else in the end.. I'll check with the other tech, maybe we can just send you the setup file if its different from the version you have.
Funnily enough we had an issue with the wireless today, with clients making bad choices for APs.. all of the laptops in an aread decided to go to just 1 AP. I had to manually fiddle with channels and powers to get the laptops to move to another AP and split the load.

I only have the 802.11d setting out of those availabel to me![]()

Well going to try to eliminate roaming as an issue this afternoon - 2 classes next to each other are running all 39 netbooks and I've switched off all APs except the one closest to them.
Ok i found out from the other tech that we got our wireless drivers from Tosh, after much complaining they produced another driver. The link takes you to the driver page:
Toshiba WLAN Driver Download
Apart from the driver configs, the other thing that got it vaguely working was setting channelization to 20 on all APs.
There are currently 1 users browsing this thread. (0 members and 1 guests)