Hello, 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? --Nick Schmidt (By the way, Samba Server works just fine) Biggest computer statements ever: It said "Insert Disk 3" but only two will fit inside. Out of my mind, back in 5 minutes. No sense being pessimistic, It wouldn't work anyway... Half the people you know are below average intelligence. Nick Schmidt, KL0VJ, Ham radio operator for 5 years --------------------------------- Yahoo! Mail Use Photomail to share photos without annoying attachments.
On Thu, 2 Mar 2006 21:48:22 -0800 (PST), you wrote:
Hello,
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?
--Nick Schmidt
(By the way, Samba Server works just fine)
Biggest computer statements ever: It said "Insert Disk 3" but only two will fit inside. Out of my mind, back in 5 minutes. No sense being pessimistic, It wouldn't work anyway... Half the people you know are below average intelligence.
Nick Schmidt, KL0VJ, Ham radio operator for 5 years
--------------------------------- Yahoo! Mail Use Photomail to share photos without annoying attachments.
Please fix your sig! When you say "Ever since I have started using SuSE 10.0 I have had troubles with connecting to Windows PCs using samba." Could you provide at least SOME details? How are you connecting, what error messages are you seeing... things like that. I can make a decent guess what your problem is but from your email I'm thinking you won't understand the answer anyway... you don't even understand the problem - or how to ask a question on a mailing list. Mike- -- If you're not confused, you're not trying hard enough. -- Please note - Due to the intense volume of spam, we have installed site-wide spam filters at catherders.com. If email from you bounces, try non-HTML, non-encoded, non-attachments,
Nick Schmidt wrote:
Hello,
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?
Yes, you're apparently missing some description of the problems you're experiencing.
On 03/03/06, James Knott
Nick Schmidt wrote:
Hello,
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?
Yes, you're apparently missing some description of the problems you're experiencing.
--
The reason I replied off list :-) I've done this sort of thing in the past - quite possibly will again in the future. I think the problem is that in the heat of the moment it is all too easy to assume that everybody else on the list is either telepathic or has a crystal ball... So, Nick, we will certainly try to help with your problem. But we really do need more to go on :-) -- ============================================== I am only human, please forgive me if I make a mistake it is not deliberate. ============================================== Xmas may be over but, PLEASE DON'T drink and drive you'll make it to the next one that way. Kevan Farmer Linux user #373362 Cheslyn Hay Staffordshire WS6 7HR
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. 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. In general, I was pretty sure that this is something that everybody had to overcome in the first place, but apparently I was wrong --------------------------------- Yahoo! Mail Bring photos to life! New PhotoMail makes sharing a breeze.
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."
Well, here's the error sets if it helps any: Smbclient command results: linux:/home/NickS # smbclient -L 192.168.1.6 Password: Domain=[SONYVAIODOWSTAI] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Sharename Type Comment --------- ---- ------- IPC$ IPC Remote IPC print$ Disk Printer Drivers SHARE Disk ADMIN$ Disk Remote Admin DSLASERJET Printer hp LaserJet 1320 PCL 6 C$ Disk Default share session request to 192.168.1.6 failed (Called name not present) session request to 192 failed (Called name not present) Domain=[SONYVAIODOWSTAI] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Server Comment --------- ------- Workgroup Master --------- ------- The ports were opened at the firewall, does IPtables do the same thing? --------------------------------- Relax. Yahoo! Mail virus scanning helps detect nasty viruses!
On 04/03/06 00:00, Nick Schmidt wrote:
Well, here's the error sets if it helps any:
Smbclient command results:
linux:/home/NickS # smbclient -L 192.168.1.6 Password: Domain=[SONYVAIODOWSTAI] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
Sharename Type Comment --------- ---- ------- IPC$ IPC Remote IPC print$ Disk Printer Drivers SHARE Disk ADMIN$ Disk Remote Admin DSLASERJET Printer hp LaserJet 1320 PCL 6 C$ Disk Default share session request to 192.168.1.6 failed (Called name not present) session request to 192 failed (Called name not present) Domain=[SONYVAIODOWSTAI] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
Server Comment --------- -------
Workgroup Master --------- -------
The ports were opened at the firewall, does IPtables do the same thing? IPtables *is* the firewall.
I'm not certain about that smbclient commandline; AFAIK, -L should specify a netbios name (or maybe a hostname? The manpages aren't clear on that), not an IP. Use -I to specify an IP, but you may still need to specify a netbios name. Have you run testparm to verify the validity of your smb.conf file?
As to this, -L lists the shares available and the connectablility of the shares. the -I does not appear to work for this. As to testparm, yes, I have dealt with that, and it is just fine. The samba server, as I said, works without a hitch. By the way, in the last message I forgot to mention I am on a 7 PC network. I'm not certain about that smbclient commandline; AFAIK, -L should specify a netbios name (or maybe a hostname? The manpages aren't clear on that), not an IP. Use -I to specify an IP, but you may still need to specify a netbios name. Have you run testparm to verify the validity of your smb.conf file? --------------------------------- Brings words and photos together (easily) with PhotoMail - it's free and works with Yahoo! Mail.
Listers i have a hsp56 micromodem pcel 688t not respondng at opensuse 10.0 Help!!! log file trying to connect to smpppd connect to smpppd Status is: disconnected Status is: connecting pppd[0]: Plugin passwordfd.so loaded. pppd[0]: --> WvDial: Internet dialer version 1.54.0 pppd[0]: --> Initializing modem. pppd[0]: --> Sending: ATM1 pppd[0]: --> Sending: ATQ0 pppd[0]: --> Re-Sending: ATM1 pppd[0]: --> Modem not responding. pppd[0]: Connect script failed Status is: disconnecting Status is: disconnected pppd[0] died: Connect script failed (exit code 8)
On 04/03/06, x
Listers i have a hsp56 micromodem pcel 688t not respondng at opensuse 10.0 Help!!!
log file
trying to connect to smpppd connect to smpppd Status is: disconnected Status is: connecting pppd[0]: Plugin passwordfd.so loaded. pppd[0]: --> WvDial: Internet dialer version 1.54.0 pppd[0]: --> Initializing modem. pppd[0]: --> Sending: ATM1 pppd[0]: --> Sending: ATQ0 pppd[0]: --> Re-Sending: ATM1 pppd[0]: --> Modem not responding. pppd[0]: Connect script failed Status is: disconnecting Status is: disconnected pppd[0] died: Connect script failed (exit code 8)
--
I'm pretty sure the PcTel modems are all Winmodems - I could of course be wrong. You'll really need to check out a Winmodems site dedicated to getting them up and running under Linux. I do know that lot of the PcTel modems have drivers written for them. You could start your search with these sites: http://tinyurl.com/z2obp http://tinyurl.com/hds6g http://tinyurl.com/ezxrl If you do a specific Linux Google search (I have the Linux Google search added to my list on Firefox) then there are a few more avenues to try. -- ============================================== I am only human, please forgive me if I make a mistake it is not deliberate. ============================================== Xmas may be over but, PLEASE DON'T drink and drive you'll make it to the next one that way. Kevan Farmer Linux user #373362 Cheslyn Hay Staffordshire WS6 7HR
On 04/03/06 02:50, Nick Schmidt wrote:
As to this, -L lists the shares available and the connectablility of the shares. the -I does not appear to work for this. As to testparm, yes, I have dealt with that, and it is just fine. The samba server, as I said, works without a hitch. By the way, in the last message I forgot to mention I am on a 7 PC network.
I'm not certain about that smbclient commandline; AFAIK, -L should specify a netbios name (or maybe a hostname? The manpages aren't clear on that), not an IP. Use -I to specify an IP, but you may still need to specify a netbios name.
Have you run testparm to verify the validity of your smb.conf file?
I seem to have confused you; you cannot, as far as I know, give the IP as parameter to the -L option. It takes the server netbios name. If you give the IP instead, use the -I option in addition to the -L option. The manpages seem to imply this should work: "smbclient -I <ip> -L", but I can't verify this right now. And no, you did not say the samba server is working properly. You have said absolutely nothing about your network, its configuration, or its status. All I know is what is in the sbmclient message you posted, and that says that you cannot properly connect to a system running Win2K LAN Manager. I have found the "Using Samba" documention (html format) in /usr/share/doc/packages/samba/htmldocs/using_samba/ to be excellent. You might find the answer to your problem there. It is part of the samba-doc package. Unless you are a bit more forthcoming with the details of your configuration, no one here will be able to make any suggestions.
On Fri, 3 Mar 2006 19:40:48 -0800 (PST), you 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.
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.
In general, I was pretty sure that this is something that everybody had to overcome in the first place, but apparently I was wrong
Well, my guess about the cause of your problem would have been wrong. 8-)> The ports you'll need to open, depending on the exact versions of windows you're working wirh, are 137, 139, and 445. (137 and 139 are for pre-XP windows, including NT. 445 is for XP only, AFAIK. Mike- -- If you're not confused, you're not trying hard enough. -- Please note - Due to the intense volume of spam, we have installed site-wide spam filters at catherders.com. If email from you bounces, try non-HTML, non-encoded, non-attachments,
On Friday 03 March 2006 10:40 pm, 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.
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.
In general, I was pretty sure that this is something that everybody had to overcome in the first place, but apparently I was wrong
Easy solution TURN OFF THE FIRE WALL. Seriously if you have Samba running then the firewall should be on the whole network not just on one computer. So get your self an additional firewall which you place on the incoming line.
SOTL wrote:
On Friday 03 March 2006 10:40 pm, 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.
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.
In general, I was pretty sure that this is something that everybody had to overcome in the first place, but apparently I was wrong
Easy solution
TURN OFF THE FIRE WALL.
Seriously if you have Samba running then the firewall should be on the whole network not just on one computer. So get your self an additional firewall which you place on the incoming line.
There is no reason why a computer cannot have it's own firewall, in addition to a network firewall. In fact, in some situations it may be desirable to even necessary to do so. The SUSE firewall, like many others can be configured to allow access to any desired protocol. The SUSE firewall config already specifies several commonly used protocols, including Samba and if that isn't enough, you can even specify individual TCP & UDP ports. Rembember, security is a many layered thing. The more barriers you put up, the harder it is for an intruder to succeed.
participants (7)
-
Darryl Gregorash -
James Knott -
Kevanf1 -
Michael W Cocke -
Nick Schmidt -
SOTL -
x