Re: [Cooker] Samba Problems in RC3
Robert J. Rossana wrote: I reported some problems with Samba in RC3. Basically it seems to die and I am unable to access shares from within a VMware virtual hard drive (I also tried from a WinXP machine on our net with the same result) using an smb.conf file that has been fine in the past. The suggestion was made to uninstall and then reinstall samba to see if that corrects the problem. I did that and it does not correct the problem. Suggestions appreciated. You missed the other reply. You don't mention if you are using the VMWare virtual network interfaces and various details regarding the setup (it's been a while since I've used vmware). I suspect you have VMware binding to some or all of the ports samba uses. Please just do: # service smb restart You should an error something like Error binding to port 137 or so. You may be able to fix this by adding: interfaces = eth0 bind interfaces only = yes Then try restart samba again: # service smb restart Alternatively, your VMWare configuration might be wrong. Is Mandrake the hosted or the hosting OS (please, you are giving way too few details about your setup for anyone to help you)? in the global section of your smb.conf. I am quite sure this is not a samba bug or a packaging problem, I am using the current package with no problems on a number of servers, including a domain controller running 9.0rc2 in production. Buchan -- |Registered Linux User #182071-| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
RE: [Cooker] Samba Problems in RC3
Actually I've been having problems with samba in the latest version of cooker as well (I'm not using vmware). Trying to connect to my linux machine using a windows machine and keep getting the error message: The network path was not found, tried restarting samba and re-running the samba configuration wizard but to no avail. -Original Message- From: Buchan Milne [mailto:[EMAIL PROTECTED]] Sent: 24 September 2002 14:09 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [Cooker] Samba Problems in RC3 Robert J. Rossana wrote: I reported some problems with Samba in RC3. Basically it seems to die and I am unable to access shares from within a VMware virtual hard drive (I also tried from a WinXP machine on our net with the same result) using an smb.conf file that has been fine in the past. The suggestion was made to uninstall and then reinstall samba to see if that corrects the problem. I did that and it does not correct the problem. Suggestions appreciated. You missed the other reply. You don't mention if you are using the VMWare virtual network interfaces and various details regarding the setup (it's been a while since I've used vmware). I suspect you have VMware binding to some or all of the ports samba uses. Please just do: # service smb restart You should an error something like Error binding to port 137 or so. You may be able to fix this by adding: interfaces = eth0 bind interfaces only = yes Then try restart samba again: # service smb restart Alternatively, your VMWare configuration might be wrong. Is Mandrake the hosted or the hosting OS (please, you are giving way too few details about your setup for anyone to help you)? in the global section of your smb.conf. I am quite sure this is not a samba bug or a packaging problem, I am using the current package with no problems on a number of servers, including a domain controller running 9.0rc2 in production. Buchan -- |Registered Linux User #182071-| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
Re: [Cooker] Samba Problems in RC3
From: O'Riordan, Kevin [EMAIL PROTECTED] Actually I've been having problems with samba in the latest version of cooker as well (I'm not using vmware). Trying to connect to my linux machine using a windows machine and keep getting the error message: The network path was not found, tried restarting samba and re-running the samba configuration wizard but to no avail. Are you running the firewall on the server? (It seems so, according to your error...) If so, take a look at: (assuming you installed the shorewall docs) /usr/share/doc/shorewall-doc-1.3.7c/samba.htm Thomas *** Tämä viesti on VirusTarkistettu INRITEL OY:n postipalvelimella!! ***
RE: [Cooker] Samba Problems in RC3
ah right, wasn't using firewall, but shorewall and iptables were running on startup for me - which shouldn't be happening, as I chose not to use a firewall during installation. Samba worked fine after I disabled both shorewall and iptables anyway. -Original Message- From: Thomas Backlund [mailto:[EMAIL PROTECTED]] Sent: 24 September 2002 14:30 To: [EMAIL PROTECTED] Subject: Re: [Cooker] Samba Problems in RC3 From: O'Riordan, Kevin [EMAIL PROTECTED] Actually I've been having problems with samba in the latest version of cooker as well (I'm not using vmware). Trying to connect to my linux machine using a windows machine and keep getting the error message: The network path was not found, tried restarting samba and re-running the samba configuration wizard but to no avail. Are you running the firewall on the server? (It seems so, according to your error...) If so, take a look at: (assuming you installed the shorewall docs) /usr/share/doc/shorewall-doc-1.3.7c/samba.htm Thomas *** Tämä viesti on VirusTarkistettu INRITEL OY:n postipalvelimella!! ***
Re: [Cooker] Samba Problems in RC3
On Tuesday 24 September 2002 15:14, O'Riordan, Kevin wrote: ah right, wasn't using firewall, but shorewall and iptables were running on startup for me - which shouldn't be happening, as I chose not to use a firewall during installation. Samba worked fine after I disabled both shorewall and iptables anyway. Shorewall uses iptables (which is the real firewall anyway), and the default Shorewall is really paranoid, cannot connect from any machine, not even the local subnet. I use firestarter, which I run from my /etc/ppp/ip-up.local, and then reset iptables in the ip-down.local. -- John Allen, Email: mailto:[EMAIL PROTECTED]
Re: [Cooker] Samba Problems in RC3
On Tuesday 24 September 2002 10:38 am, John Allen wrote: I installed iptables but don't use it in favor of using Shorewall. I opened the appropriate ports for Samba (137, 138, 139, and 445 both tcp and udp). I can't remember if I disabled Shorewall to see if Samba would work but I will try that when I get home. Samba does work properly on my work machine where I have set things up in a similar way. But you may be right to suggest that Shorewall is flakey. I'll disable it to see what happens. Bob On Tuesday 24 September 2002 15:14, O'Riordan, Kevin wrote: ah right, wasn't using firewall, but shorewall and iptables were running on startup for me - which shouldn't be happening, as I chose not to use a firewall during installation. Samba worked fine after I disabled both shorewall and iptables anyway. Shorewall uses iptables (which is the real firewall anyway), and the default Shorewall is really paranoid, cannot connect from any machine, not even the local subnet. I use firestarter, which I run from my /etc/ppp/ip-up.local, and then reset iptables in the ip-down.local. -- Robert J. Rossana E-Mail: [EMAIL PROTECTED] Department of Economics, 2074 F/AB, Wayne State University, Detroit MI 48202 Web Page: www.econ.wayne.edu/~rossana Telephone: (313) 577-3760 Fax: (313) 577-0149
