![](https://seccdn.libravatar.org/avatar/5a94d2f8a5845d5f1c1ea1556fc0cb72.jpg?s=120&d=mm&r=g)
Brian Durant wrote:
I am trying to connect to the Win boxes on my LAN. That is why I am trying to get the smb client working, preferably with LinNeighborhood as per the instructions in Art's e-mail Printing has become a topic because you stated as follows in a previous mail:
I am sorry, but the following has nothing to do with printing. It is to be able to browse or mount your Window's shared hard drive.
From what I have seen, LISa is to be used to browse network shares, not samba shares. Have you tried in Konquerer smb://"computername"/"share Try mount -t smbfs -o rw,user,username=(yourusername for the share), password=(passwd for that share) //"computername"/"sharename" mountpoint, or. i.e. mount -t smbfs -o rw,user,username=joe,password=xxxxx //jmorris/C /mnt/samba. If all you are going to do it read/write, I can do it with my Windows machine downstairs through Konq with smb:// as above.
This obviously does not help me much if I also need to print. Nor does it follow the instructions that were provided in Art's mail, which I am trying to follow as stringently as possible, so that I can get this issue solved as quickly as possible.
I'm sorry, I have long since deleted the original emails. I can't help you follow Art's instructions. But, you are not going to use smbclient to print, nor LinNeighborhood. They are programs to browse the shares on a network. If you want to see a Windows share from your Linux machine (see above subject :-) ), you can type on a command line (i.e. xterm) smbclient -L (computer name) -You fill in the name. If you want to print, you will use lprold, lprng, or cups. I would recommend CUPS to print to your Windows served printer, and your printing program will use samba_print to actually print through the network to your Windows printer. If this is different than Art's instructions, and that is what you are comfortable with, then just delete this email.
AFAIK, printer sharing is not one of the things that Konq can do.
This is another attempt to direct the issue at hand back to Art's original e-mail. I am simply pointing out (again) that your suggestion of using Konq will not help me, but is simply muddying the waters in relationship to Art's original e-mail instructions.
Sorry, can't help there.
Go to control panel, network, windows share. Enter the information there.
"Default user name" is this the "computer name" that I am working from or is it literally "user name"?
Where is this exactly. If you mean the Identification tab, it is the computer name.
Look above, it states KDE control center "panel", network, windows share. That is where it is necessary to fill out the "default user name". Now, does this literally mean "user name" or "computer name"?
Again, miscommunication. As you noted above, it is control center in KDE. I thought you were talking about the Windows machine, which does have control panel>network. The default user name is exactly that. If you set up your Windows (in Windows) to share based on password, then this setting would give it that username and password. If you set up your Windows HD for full access (meaning no password is needed), this is not even needed. BTW, user name is user name, not computer name. This is to authenticate your Linux machine (using Samba) to your password protected Windows shares. I hope that is now clear. ;-)
I ask, because as I see it, on a home LAN, it is more important to know which computer is connected than which user. Our family members sometimes switch computer if there are performance or technical problems with one or more of the computers.
If you are talking about a resource of a computer, such as a HD or printer, it is always referred to its source as the computer, not the user.
Exactly, which is why the requirement of filling out "user name" in KDE -> Control Center-> Network -> Windows Share is confusing for me. My conclusion is that "user name" means "user name" in this field, but as you rightly stated in one of your earlier e-mails:
What I mean is you don't 'have' to login (and at least with Windows can easily bypass any pseudo login). It really doesn't have a true concept of a user, such as NT, W2000, Linux, etc.
Therefore, I don't see the purpose except to hold the hand of former Win users.
See above.
I am part of the work group in the sense of that I created it, but the others on my LAN are only desktop users and do not use the work group for anything. It is there for my convenience. How do I "become" a member of the "work group" in SuSE?
If you are not sharing resources with Windows via Samba (which you would put it in smb.conf), then putting it in Control center for Windows shares will basically allow you to skip the workgroup level (since this would be done by the setting for workgroup) in (I believe) Konquerer (the KDE default file browser).
Then you go to Options, Browse entire network. You should be able to see all of the windows shares. You can then select the folder or drive and mount it. This should put it in your home directory. You can close LinNeighborhood, and then browse the share with Konqueror or other file manager.
What procedure do I need to go through to access a printer on the LAN with LinNeighborhood?
You don't. Use CUPS, configure with K>System>Tools>Cups administration tool.
Do you mean "print job administrator"? I haven't been able to set up a printer in YAST2. So I don't believe the KDE tool "print job administrator" will help.
No. Do you have Cups installed (it is several different rpms)? Kups is the program I was refering to, because on my network (Windows shared Canon Multipass c-5500), Yast2 could not set it up. Kups did it quite impressively, IMHO.
If you just want to see your Windows shares (HD or printer), type in the location field in Konq smb://(computer name of your windows machine). If that doesn't work, what does it give you?
smb://"computer name" gave me:
I'm sorry, I was not clear enough. You need to supply the names of your Windows computers, not use computername. Also, if your Windows machines are not in your /etc/hosts file or /etc/lmhosts, and you are not running DNS (which I believe you said), it still wouldn't work (you could enter them though :-) ). As a quick work around, just supply the IP address of your windows machine with the shared drive/printer, i.e. smb://192.168.1.2 {replace with the IP of one of YOUR machines). That should work.
-- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871