On 03/03/06 21:40, Nick Schmidt wrote:
Hey,
The reason I sent this was because I thought this was more of a common issue than anything else, and, I have seemed to get a more effective response from "flamers" than any other way.
Take a good look at what you originally asked:
Ever since I have started using SuSE 10.0 I have had troubles with connecting to Windows PCs using samba. Is there something general that I am missing?
Hardly conducive to anyone understanding anything about the problem, is it?
Here is the issue:
YaST Firewall is blocking samba client. I need to know what settings/ports opened/other stuff that need to be changed in order to make this work, short of disabling the firewall.
If you are using samba on an "internal" interface, by default, nothing is blocked on that interface. I doubt it will do you any good to open some ports that are probably already open, but here they are: all netbios ports (137 to 139 incl.) and microsoft-ds (445). If you are using samba on an external interface instead (ie. one that is connected directly to the internet), I hope you have put some decent security into your samba configuration.
In general, I was pretty sure that this is something that everybody had to overcome in the first place, but apparently I was wrong
In general, you will find it difficult to get answers if all you say can be summed up with "It's broken."