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.
I have two computers connected to a DSL router. One is windows XP Home & the other is my slackware 10.current(sort of) box.
I was messing with the SWAT interface attempting to set up a file server on my linux box that XP home would be able to find.
I am already able to use my linux box to find a shared folder on the windows machine, and we both connect to the internet just fine and dandy.
So as I was looking around the SWAT interface, I attempted to change a few settings. Then I restarted the computer. Suddenly my box wouldn't even connect to the router or anywhere else. The XP machine connected fine.
Since swat is only available via root, it can access or change any file on my computer. What files is it supposed to be able to change?
I know it can change smb.conf, but this can't be all, because just messing with that wouldn't take my connection down.
BTW (I did finally get it up again using DHCP. But I would rather go back to static routing)
Really the only error that came about was "network unreachable". I couldn't even ping my router.
Perhaps I messed it up trying to get swat to work. It doesn't work right out of the bag, I had to uncomment a line in /etc/inetd.conf I messed up the first time by putting it in /etc/indentd.conf. But then I took it back out again. Then I put it into rc.inet1.conf. Which wasn't right either, so I took it out. I finally found the right file. But I'm sure that I cleaned up what I put in.
(Regarding SAMBA), I really don't know much about samba, I don't know what options really do, I was just kind of reading suggestions on this or that website to get it set up, and nothing seemed to work to get XP HOME connected. there are a bunch of wesites all over that try to tell you how, but I really didn't get anything to work.
I actually destoryed the smb.conf (copied the sample file back over it) in an attempt to get my internet back up again. So really, I'm starting with nothing here. I'll probably play with it again later today though.
Questions:
Do I need wins ?
I don't even know you could specify user or share. (I think Xp home is not supposed to be able to handle share is it?)
I will look in the XP LAN properties to see if something is disabled that shouldn't be.
I've only used SWAT once, and ended it up breaking a working smb.conf. IIRC, one of the unofficial Samba FAQs actually called SWAT the "Single Worst Administration Tool," or something to that effect.
Personally, I just build it manually using a text editor, and if I have any questions I use a FAQ.
Anyway, WINS is only needed if you want to resolve NetBIOS names over IP. Since your network is relatively small, though, you can get along just fine without it.
With XP Home, I think you can access shares and map network drives, the only thing that (i think) it doesn't do is allow domain logins. Although XP Home should be fine if you're setting up simple shares.
You may also want to use the testparm utility. testparm basically scans your smb.conf file for errors, allowing you to make any corrections prior to launching the Samba daemons.
Alright, here is a copy of what testparm told me. And so far, windows hasn't found it yet
[global]
workgroup = MSHOME
security = SERVER
guest account = pcguest
log file = /var/log/samba.%m
max log size = 50
dns proxy = No
[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No
[tmp]
comment = Temporary file space
path = /tmp
read only = No
guest ok = Yes
I would simply like the /tmp directory to be able to be found via xp home. I don't want any fancy permissions, just enough so that it should be readable and writable by anyone from the internal network.
Well, after some fiddling around, I finally got it to work. I changed the server type to a user server type, and made sure the passwords were encrypted.
I then adduser'd the name of the machine with a $ after the name. And I adduser'd the name of the login user.
I then added the machine and user into the smbpasswd database, using no password (just pressed enter).
I gave everything a name, I'm not sure if I needed to though.
workgroup = mshome
netbios name = popeye
I also had to make sure everything was enabled in win XP home, I went to the
My Computer ->
View Network Places ->
View network connections ->
Then an advanced menu appears (Advanced Settings) ->
Proceeded to check everything under Microsoft Client. Specifically I enabled TCPIP, not just Microsoft TCPIP v6.
Wow, I can't believe I ever found that location. You can't get to it from the control panel. It's hidden away. Lucky me. So once I got ALL that taken care of, windows home suddenly saw all of its own shares AND my linux shares under the network neighborhood.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.