Freedome problems conneting with WiFi and Mokkula
I am using both beta and the Licensed version.
How is the connection supposed to work?
I've set Freedome to start when the computer starts.
When I start the computer many times Freedome starts establishing the connection and keeps on and on.
While it is doing that the PC cannot connect to the (hotel) WiFi or my mokkula.
If Freedome is already on I cannot switch it off whilenybody else it is trying to establish the connection.
What I can do is change the setting Freedome not to start when the computer starts and reboot.
Just did it.
Some times it is the opposite: I start my PC (another PC) and Freedome is set Off. It won't make the connection to WiFi until I turn Freedome on. Then it goes OK.
No such problems when I am non LAN connection.
Too random yet to saz what the pattern is. As said I use both beta and the licensed product.
Anybody else similar connection problems?
Comments
-
I am using both beta and the Licensed version on Win 8.1 64 and 32 bit.
How is the connection supposed to work?
I've set Freedome to start when the computer starts.
When I start the computer many times Freedome starts establishing the connection and keeps on and on.
While it is doing that the PC cannot connect to the (hotel) WiFi or my mokkula.
If Freedome is already on I cannot switch it off whilenybody else it is trying to establish the connection.
What I can do is change the setting Freedome not to start when the computer starts and reboot.
Just did it.
Some times it is the opposite: I start my PC (another PC) and Freedome is set Off. It won't make the connection to WiFi until I turn Freedome on. Then it goes OK.
No such problems when I am non LAN connection.
Too random yet to saz what the pattern is. As said I use both beta and the licensed product.
Anybody else similar connection problems?
-
Hello Martink,
Do you have the same behavior on both Beta and latest production version?
Could give more information on that part:"I cannot switch it off whilenybody else it is trying to establish the connection"
Where are other establishing connection to? Who is "anybody else"?
From this part "It won't make the connection to WiFi until I turn Freedome on. ", it seems that you have issues even when Freedome is off. Could it be that there actually are some restrictions on the networks you try to connect to.
Please provide screenshots of the errors you encounter so that we can better understand the issues you are facing.
-
Thank you for you repsonse. I think I am getting to it. When I turn off the PC I use something called hybrid shut down which saves core system but not user session. That includes an IP given from the ISP. Typically I have my hw on for the whole day and only turn off them for the night. HW including the mokkula. The next day tunring the mokkula on makes it get a new dynamic address from the ISP. That is not likely to match the one saved with the hybrid shut down. Restart is one way to get a new from the mokkula.
Somehow I did not think that prbolem existed before installing Freeedome.
As said I have not yet established a pattern if it is the same on beta and the licensed product. Apparently it is not a mjor issue anyway, but I am not quite sure if it only occurs when Freedome is installed.
"I cannot switch it off whilenybody else it is trying to establish the connection"
Is my touchpad acting up while I type and putting text randomly where it sees fit and the cursor not satying where I am typing. that should be
"I cannot switch it off while it is trying to establish the connection"
That means the the message on Freedome is "Connecting" and I have not found a way to stop that other than reboot or kilng the task. Not that I know what is underlying I do not need to get into that state.
-
-
Not reallz, because what restart does is more close to shutdown than hybrid.
Secondlz on my Win 7 laptop where there is no hybrid shutdown I don't recal this problem.
Only with my Win 8.1 PC's
Therefore I mark mz reasoning aboe as the correct accepted answer.
That is the normal way Freedome behaves and is expected to behave (oither than not being able to stop the connecting attempt)