problem setting up samba on suse 9.3
Dear SUSE users: I would like to use samba on my suse 9.3 box. I have set up the samba shares through yast. I also cheked the 'open port in firewall' option. But when I want to browse the windows/samba network, clicking on the desktop icon 'Network Browsing', then on the 'SMB Shares' icon in the upcoming window, I get the following error message: "Unable to find any workgroups in your local network. This may be caused by an enabled firewall." I checked my firewall settings and made sure that Samba Server is allowed, furthermore UDP ports 138 and 139 are enabled. Still can't browse the samba network. I can't even see my own shares. If I turn off the firewall I can browse the samba ahares and the samba network with no hassle. So it seems that the culprit is the firewall but which setting? I had no this type of problem in 9.1 and 9.2 Please help! Thanks, IG _________________________________________________________________________ Töltsd le Caramel első saját szerzeményét, és nyerj egy közös vacsorát vagy VIP-jegyeket a lemezbemutató koncertre! http://zenearuhaz.t-online.hu/index.php?m=info&albumid=14517&sp=74&sty=78
On 10/20/05, Istvan Gabor
Dear SUSE users:
[snip]
If I turn off the firewall I can browse the samba ahares and the samba network with no hassle. So it seems that the culprit is the firewall but which setting? I had no this type of problem in 9.1 and 9.2
Samba (smbd/nmbd) uses the following ports: UDP/137 (nmbd) UDP/138 (nmbd) TCP/139 (smbd) TCP/445 (smbd) Adjust your firewall appropriately and everything should working as expected. Please let us know if you made progress. \Steve
Samba (smbd/nmbd) uses the following ports:
UDP/137 (nmbd) UDP/138 (nmbd) TCP/139 (smbd) TCP/445 (smbd)
Adjust your firewall appropriately and everything should working as expected. Please let us know if you made progress.
\Steve
Dear Steve: Thanks for your answer. If I try to enable UDP/137,138 and TCP/139,445 ports in Yast's Firewall setup when the Samba server is enabled in the allowed services window, the system does not accept 137, 139 and 445 ports. Only UDP/138 port is kept in the settings, the other 3 are always cleared. If I disable (ie delete) Samba server from the allowed services window, I can set permanently all the above 4 ports. In either case I can not browse the samba network. After each time I've changed firewall settings I restart the firewall clicking on the "Save settings and restart firewall now" button in the Firewall Configuration - Startup panel. Should I also restart samba server each time? Thanks, IG _________________________________________________________________________________________________ Hírkereső.hu - Mindig friss hírek, toplisták, sztárpletykák. A legfontosabb 80 hírforrás közel 3.000 cikke naponta! Ha egy lapon akarsz mindent áttekinteni KLIKK IDE: http://www.hirkereso.hu/a
Istvan Gabor
Dear SUSE users:
I would like to use samba on my suse 9.3 box. I have set up the samba shares through yast. I also cheked the 'open port in firewall' option. But when I want to browse the windows/samba network, clicking on the desktop icon 'Network Browsing', then on the 'SMB Shares' icon in the upcoming window, I get the following error message:
"Unable to find any workgroups in your local network. This may be caused by an enabled firewall."
Nobody has any idea how to solve this problem? IG _________________________________________________________________________________________________ Hírkereső.hu - Mindig friss hírek, toplisták, sztárpletykák. A legfontosabb 80 hírforrás közel 3.000 cikke naponta! Ha egy lapon akarsz mindent áttekinteni KLIKK IDE: http://www.hirkereso.hu/a
On Wednesday 26 October 2005 08:18, Istvan Gabor wrote:
Istvan Gabor
írta: Dear SUSE users:
I would like to use samba on my suse 9.3 box. I have set up the samba shares through yast. I also cheked the 'open port in firewall' option. But when I want to browse the windows/samba network, clicking on the desktop icon 'Network Browsing', then on the 'SMB Shares' icon in the upcoming window, I get the following error message:
"Unable to find any workgroups in your local network. This may be caused by an enabled firewall."
Nobody has any idea how to solve this problem?
I get the same response with my setup. I have found a workaround though: I have been able to see my shares by going to the machine directly instead of through the workgroup (i.e. smb://MACHINE/). After I have input this location into Konq, I get a dialog box asking for user name and password for the machine. Once input, I am able to see all the shares on that machine. Make note of the address line now; you'll see it as smb://USER@MACHINE/SHARE. I am not able to go to the share directly this way, but have to get the user name and password dialog box first. Remember you have to add the users and their passwords for the individual machines. Read the smb.conf man page to show you how. I think the problem lies in the fact that one of my windows machines is the PDC. I'm not sure how to change this yet, and not really concerned about that now that I have found the workaround. Good luck. Any further questions, ask away. Bernd
On Wednesday 26 October 2005 14:22, Bernd wrote: <snip>
I have found a workaround though:
Hi Bernd & List, Just want to report that I'm having success doing something similar under 10.0: Entering "smb://nnn.nnn.nnn.nnn/" (local machine's IP address) in Konqueror draws out the login dialog box. I gain access to the share after providing my username and password. It sure beats dropping the firewall! regards, - Carl
On Wednesday, October 26, 2005 @ 9:20 PM, Carl Hartung wrote:
On Wednesday 26 October 2005 14:22, Bernd wrote: <snip>
I have found a workaround though:
Hi Bernd & List,
Just want to report that I'm having success doing something similar under 10.0: Entering "smb://nnn.nnn.nnn.nnn/" (local machine's IP address) in Konqueror draws out the login dialog box. I gain access to the share after providing my username and password. It sure beats dropping the firewall!
regards,
- Carl
I have a shared folder on my Windows machine that I connect to from my Linux box without the need for the prompt. To do that, I added user ANONYMOUS LOGON to the folder that is being shared. There is nothing in the folder that is of a nature that I would worry about it being hacked, plus, both machines are behind a hardware firewall. I set up a desktop link to the Windows share on my Linux desktop and all I have to do is click it to get into the Windows folder. I also have a similar desktop link on my Windows machine to a shared folder on the Linux box. So, from either machine, I can drop a file into the shared folder on the other machine (or drop it into the one on the current machine and then go drag it out from the other side). Greg Wallace
On Thursday 27 October 2005 05:08, Greg Wallace wrote:
I have a shared folder on my Windows machine that I connect to from my Linux box without the need for the prompt. To do that, I added user ANONYMOUS LOGON to the folder that is being shared. There is nothing in the folder that is of a nature that I would worry about it being hacked, plus, both machines are behind a hardware firewall. I set up a desktop link to the Windows share on my Linux desktop and all I have to do is click it to get into the Windows folder. I also have a similar desktop link on my Windows machine to a shared folder on the Linux box. So, from either machine, I can drop a file into the shared folder on the other machine (or drop it into the one on the current machine and then go drag it out from the other side).
Hi Greg, For the record, if you share a directory on a M$ box and fail to protect it with both a password *and* a resident firewall, anyone who can "see" the share probably knows how to gain access to the contents of the entire drive. This is one of the built-in 'undocumented features' of that OS. regards, - Carl
On Thursday, October 27, 2005 @ 3:16 AM, Carl Hartung wrote:
On Thursday 27 October 2005 05:08, Greg Wallace wrote:
I have a shared folder on my Windows machine that I connect to from my Linux box without the need for the prompt. To do that, I added user ANONYMOUS LOGON to the folder that is being shared. There is nothing in the folder that is of a nature that I would worry about it being hacked, plus, both machines are behind a hardware firewall. I set up a desktop link to the Windows share on my Linux desktop and all I have to do is click it to get into the Windows folder. I also have a similar desktop link on my Windows machine to a shared folder on the Linux box. So, from either machine, I can drop a file into the shared folder on the other machine (or drop it into the one on the current machine and then go drag it out from the other side).
Hi Greg,
For the record, if you share a directory on a M$ box and fail to protect it
with both a password *and* a resident firewall, anyone who can "see" the share probably knows how to gain access to the contents of the entire drive. This is one of the built-in 'undocumented features' of that OS.
regards,
- Carl
I'm sure that's true. I'm just willing to take the risk. If my router's hardware firewall, Norton Firewall and Virus protection, McAfee Anti-Spyware, Ad-Watch, and Spybot aren't enough to protect me, then I'll just deal with the consequences when they happen. This is my personal home network and no one else works on it but me. Greg Wallace
I get the same response with my setup.
I have found a workaround though:
I have been able to see my shares by going to the machine directly instead of through the workgroup (i.e. smb://MACHINE/).
Bernd
Writing the machine's name directly in the address line helps opening the computer's shares. Thanks! IG _______________________________________________________________________ Képtipp! Játssz a T-Online képkeresőjével! Ha elég ügyes és gyors vagy, felkerülhetsz a dicsőségtáblára... www.t-online.hu
participants (5)
-
Bernd
-
Carl Hartung
-
Greg Wallace
-
Istvan Gabor
-
Steve Graegert