wireless network connection lost on samba connect

Bug #243338 reported by Romke Nijkamp
2
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: smbclient

Symptoms:
When you connect to a samba server over a wireless network the following happens:
1. The connection to the ap is disconnected.
2. You are not able to connect to the access point anymore.
3. Other access points work just like if nothing happened.
4. This is driver-independent

Steps to reproduce:
1. Connect to a samba share.
2. If i cannot successfully connect to a samba share then the bug does not occur.

Other Notes:
I am connecting with the connect to server option in gnome.
The server is running samba server on slugosbe 4.8 and is using versions:
samba - 3.0.23c-r1 from openslug/slugosbe feed.

The client is just running the default settings on ubuntu hardy 32-bit and is using versions:
libsmbclient: 3.0.28a-1ubuntu4
nautilus-share: 0.7.2-0ubuntu5
samba-common: 3.0.28a-1ubuntu4
smbclient: 3.0.28-1ubuntu4
ndiswrapper{
utils version: '1.9', utils version needed by module: '1.9'
module details:
filename: /lib/modules/2.6.24-16-generic/ubuntu/misc/ndiswrapper/ndiswrapper.ko
version: 1.52
vermagic: 2.6.24-16-generic SMP mod_unload
}
and of course a wireless-n network driver WUSB300N from linksys.
Note: i have this problem on many hardware configurations - all the systems with wi-fi
The ubuntu system does not have any extra repository's enabled except the defaults.

Expected:
I expected that when you connect to a samba share that wi-fi is unaffected.

Revision history for this message
Chuck Short (zulcss) wrote :

So you are saying when you connect to a samba share your network disconnects?

chuck

Changed in samba:
status: New → Incomplete
Revision history for this message
Romke Nijkamp (romkenijkamp) wrote :

Yes. I don't have any problems over a cable.
Note that when the connection is made the network is disconnected and the access point is blocked.
This problem exists a very long time and is maybe one of the causes of all the ndiswrapper and other wi-fi problems. No other protocol has the same.

Restarting the system/drivers/daemons does not work. Tried removing ap from keyring and any configuration file without success.

If you need more details then feel free to ask me.

Cheers, Romke.

Revision history for this message
Romke Nijkamp (romkenijkamp) wrote :

I found some related ndiswrapper bugs:

Ndiswrapper socket deadlock:
https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/227033
   Interesting comment:
      14. https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/227033/comments/14

This one is also related since it keeps asking for a security key repeatedly after the ap is blocked by the bug:
Authentication with AP does not work.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/182716

Not related to ndiswrapper because it happens on any wireless nic.

Cheers, Romke.

Revision history for this message
Michael Lustfield (michaellustfield) wrote :

Can you try this in Ubuntu 8.10 and tell us if the problem still occurs?

Revision history for this message
Michael Lustfield (michaellustfield) wrote :

Marking invalid due to inactivity.

Changed in samba:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.