Hi I’m a regular OpenSuse user, but recently I had to download Windows7 on my computer for work. Everything was fine for a while, but now when I switch to windows, the wireless doesn’t work sometimes (sometimes it works just fine). When this happens wireless is broken on the Linux side as well. The only way I know to fix it is to hard wire the laptop when booted into windows, and then everything is back to normal. It’s really starting to tick me off and I have no idea what may be causing it. I didn’t even know the two partitions can effect each other.
On 03/16/2011 09:36 PM, snowblind27 wrote:
> Hi I’m a regular OpenSuse user, but recently I had to download Windows7
> on my computer for work. Everything was fine for a while, but now when I
> switch to windows, the wireless doesn’t work sometimes (sometimes it
> works just fine). When this happens wireless is broken on the Linux side
> as well. The only way I know to fix it is to hard wire the laptop when
> booted into windows, and then everything is back to normal. It’s really
> starting to tick me off and I have no idea what may be causing it. I
> didn’t even know the two partitions can effect each other.
Windows sometimes messes up network devices by setting Wake-On-Lan. If that is
an option in the BIOS, disable it.
If I were to hazard a guess,
Your network is confused whenever you join the network using the same DHCP lease (because both OS use the same NIC) but with different Hostnames.
Simple solution is probably to refresh your DHCP lease
From openSUSE assuming you’re running Network Manager
Click on Network Manager tray icon
Click on your Network entry
When you’re in a Work Environment, there may be additional issues as well… like “proving” your machine is a valid host in the network authenticating to your network security (like Active Directory, possibly Internet Gateway, etc). Normally if DHCP, DNS and AD are all integrated (like in AD) recreating your DHCP lease ought to address everything but depending on actual network services, configuration and authentication/authorization YMMV.
If you have further issues, post again with detailed info(as much as can be shared in a public forum).
This thread vaguely reminds me of a situation many, many years ago but I can’t clearly remember what the cause was. Somewhere I seem to remember something about only being able to authenticate over one of the connections (wired in your case) which then permits “any” network traffic.
At the moment, I suspect either machine identity on your Network. Would need to know what type of Network Authentication is implemented (eg Active Directory, openLDAP, NIS, etc) and if/how your wireless router is configured to authenticate.
In other words, enterprise network security often authenticates not only the User (typically Username/password) but often the machine (certificate, MAC address, etc).
If this situation exists, you (more likely your network SysAdmin) either needs to select/configure an authentication method that’s common to both your OS or configure both machine accounts as valid (using the same NIC).