This may not be much help ... apologies in advance.
I have had this problem - or very similar - in the past but I can't really remember the details.
I think the problem was largely that windows and the configuration utility provided by the manufacturer kept battling to take control of configuring the connection, with each logon it would be 'flip a coin' to see who thinks they are controlling it today. In the end I have opted to automatically start the Ralink utility on login and that seems to persuade winodows that it should use that to control the profile. It still however does not connect first time every time and I have to disconect and reconnect on occasion.
The other side issue seemed to be that the connection would never connect properly until NIS had finished starting up - make a cup of tea time. That seems to be better now I have dumped norton and got zone alarm instead
Hope some of this helps...
I have had this problem - or very similar - in the past but I can't really remember the details.
I think the problem was largely that windows and the configuration utility provided by the manufacturer kept battling to take control of configuring the connection, with each logon it would be 'flip a coin' to see who thinks they are controlling it today. In the end I have opted to automatically start the Ralink utility on login and that seems to persuade winodows that it should use that to control the profile. It still however does not connect first time every time and I have to disconect and reconnect on occasion.
The other side issue seemed to be that the connection would never connect properly until NIS had finished starting up - make a cup of tea time. That seems to be better now I have dumped norton and got zone alarm instead
Hope some of this helps...