[EMAIL PROTECTED] wrote: > This is anecdotal at this point, but I seem to be having problems with SAMBA > after upgrading to the Testing. I cannot see the local network, nor mount > network volumes. > > I am able to boot and access the WAN. I also submitted the inventory as > requested, but I did not notice anything suspicious in the files regarding > SAMBA. I have not changed the configuration file, or any other systems on > the network. Other Arch machines (upgraded to Current) are still OK. > > Is the a problem that anyone else has seen, or is it a knowing issue? > > Kind regards. > > _______________________________________________ > arch mailing list > [email protected] > http://www.archlinux.org/mailman/listinfo/arch > > I am still having problems. The madwifi drivers were downloaded again, and recompiled against the kernel from testing.
These were recompiled and installed, after stopping samba, cups and the network. I restarted the network with the new drivers, then restarted samba and cups. Samba says that it starts successfully (DONE), as does cups, but when I try to mount the network volume, it fails with :2966: Connection to host1 failed If I run smb4k, now local area network is found. I can ping google, and otherwise use the internet, so the basic network connection seems sound. Other Arch systems on the local network are able to connect to the samba server without difficulty. From systems within the recognized LAN, they can see each other but not the affected system. I've not changed the samba.conf file on this system, or any other. Prior to upgrade to Testing, the samba volumes mounted OK from this workstation. Does anyone have anything to suggest? _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
