SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Running a Slackware 9.0 system sharing a LAN with a Win2K machine.
SAMBA has been running and working perfectly for some time. Linux
shares are readily seen in Network Place on the Win2K machine and I
can mount the Win2K shares in Linux and view/transfer files between
the machines in File Manager.
Decided to give LISA a try on the Linux machine and after a bumpy start
finally got it to load at bootup. When I open Konqueror and enter
lan:/
I can see both machines but when I click on either of these entries and
then click on SMB, the return is blank. This happens even with Win2K shares
mounted with smbmount even though this should be unnecessary with LISA.
I also tried:
smb:/win2Kserver.workgroup.com
and the shares appeared (even the administrative shares).
However when I click on one of the shares i get:
Internal error
Please report bugs to ...
Server or workgroup could not be found.
Obviously the server can be found if the shares show up so I thought it
must be the workgroup. But the workgroup is correct and I have the
correct workgroup set in the Local Network Browsing KDE control module
even though this is supposedly for the Samba client only, not the server.
This is very puzzling to me since I see no one in the Forum reporting
this kind of problem.
That lets you mount SMB shares when you're NOT root. You should never run as root, EVER. But you're right, you don't need that when you're root. Perhaps samba is not set up quite right. Can you post your smb.conf
in konqueror, try each of the following separately and see what works best for you.
smb:/
smb:/<workgroupname>
smb:/<hostname>
ie: smb:/corvette (what's in your hosts file, or ip)
smb:/<hostname/sharename>
ie: smb:/corvette/me
Notice the / not a .
I had that error before, easy remedy, let me think what it was.
Be careful running as root. Isn't there a better way?
and if there was it would have an e after the t, you should use
guest ok = Yes
However that only applies for accessing the samba machine. Security = user means that every machine has to log in to access the network, and I'm not sure whether konqueror can do that. I use Security = share on my network.
"writable should be writeable" as I once pointed out in a Samba posting
some time ago, which was met by a number of different replies saying the
syntactically or proper spelling is 'writeable', but that Samba prefers,
nee needs to see 'writable'. I've seen more horseshit in these forums than
I could possibly dream up in a drug-induced haze; in this case, either spelling
seems to work properly.
You will also notice that the options, such as 'writable', only affect Linux shares
and have nothing to do with the Windows side of the aisle.
boxes are:
corvette: FreeBSD server
camaro: new Slackware just setup
mustang: Slackware laptop
nova: Windows, share is me and c:\temp
smbtree, smbclient, smbmount, and konqueror using the smb:/ in the location worked in < 2min. Using the smb:/ method shows the Workgroup, click on that shows all boxes. Or just smb:/nova works also.
If you are having problems, check over what you may have added or deleted recently.
It seems I may have something wrong but I am not quite sure what it is.
I went back to the recommended tests for a proper SAMBA installation and
I found one test that was not performing the way it should:
nmblookup -B win2k '*' which returned
querying * on 192.168.0.1
name_query failed to find name *
I have not removed any packages or changed anything other than configurations
since I set up this box about a year ago. I am glad this is not a critical problem
since I am completely stumped now.
Only other thing I know to check is your /etc/hosts and open your firewall for smb and netbios if you already haven't. If you are behind a router and don't have anything in the router open, turn off the firewalls if you have them. I say this because some have a hardware router/hub and also run a firewall on their computer.
Firewall is open, otherwise I couldn't do anything at all. As I mentioned
I can mount Win2k shares with smbmount and see them in file manager
(Konqueror). I can also use smbclient and view the contents of the shares
there. My Linux shares have always appeared in Network Places.
One last thing that I tried:
smbclient -L win2k which output:
Domain=[wg] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager]
Sharename Type Comment
--------- ---- -------
IPC$ IPC Remote IPC
print$ Disk Printer Drivers
EpsonSty Printer Epson Stylus COLOR 500 ESC/P 2
C Disk
ADMIN$ Disk Remote Admin
C$ Disk Default share
Server Comment
--------- -------
Workgroup Master
--------- -------
I would ordinarily expect to see the win2k machine listed under Server and the
wg listed under Workgroup. If this command is run with the Linux box host name
the output is:
Sharename Type Comment
--------- ---- -------
tmp Disk Temporary file space
pub Disk
IPC$ IPC IPC Service (Samba Server)
ADMIN$ Disk IPC Service (Samba Server)
Panasonic Printer PANASONIC KX-P4410 ljet2p
Server Comment
--------- -------
win2k
deep Samba Server
Workgroup Master
--------- -------
wg deep
There might be some kind of permission problem which only appears under LISA.
Everything seems to work well using just SAMBA. I'll play with it a little more.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.