If Wireless AutoSwitch is not working as expected the first thing you should do is make sure you are using the latest version, this is downloadable below. Try downloading and installing the latest version of the product you are using (remember to enter your permanent license key, if you have one, during install). Also take a look at the "WrlsAutoSWLog.txt" file in the installation directory for any error messages.
If that doesn't work then you can try putting the application in debug mode:
Do the following to create a debug file, start while hard wired:
1. Go to the Services MMC (Start - Run - services.msc)
2. Stop the Wireless AutoSwitch service.
3. Go to c:\program files\wireless autoswitch (or c:\program files(x86)\wireless autoswitch)
4. Create an empty file called "debug.txt" (without the quotes)
5. Start the Wireless AutoSwitch service. The debug.txt file should disappear.
6. Wait 30 seconds - disconnect the wired cable - wait 30 seconds - reconnect the wired connection - wait 30 seconds.
7. Stop and restart the Wireless AutoSwitch service (this part is very important as it stops debug mode).
8. Find the c:\wrlsdebug.txt file and email it to email@example.com with a quick note about the issue. (Sometimes the file is in c:\program files\wireless autoswitch).
Repair WMI Issues
Recently we are having more and more cases where Wireless AutoSwitch is not working because WMI (Windows Management Instrument) is broken or corrupt on their machine. Wireless AutoSwitch will not work if WMI is not working (this is noted in the manual). (By the way Wireless AutoSwitch is not causing this issue.)
If you run the above debug procedure and in the log you see this line: "TERMINAL WIL ERROR=>3131 (OleExecute: Not a valid OLE object. Period may have been used in place of a comma.)" then WMI is broken and needs to be repaired.
On Windows XP:
To repair WMI: Google "Repair WMI" (without the quote marks). For an automated/scripted way Google "FixWMI.cmd".
On Windows 7:
To Repair WMI: Open an administrator's command prompt and run "net stop winmgmt", then run "winmgmt /resetrepository" then reboot.
You can call or email us anytime and we will help you resolve the issue as fast as possible.