Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
12-23-2005, 12:08 AM
|
#1
|
Senior Member
Registered: Jan 2005
Distribution: Slackware, BackTrack, Windows XP
Posts: 1,020
Rep:
|
what settings should i make in SWAT ???
Hello all,
i've two machines, one running Slackware 10.0 and the second one running Windows XP professional SP2.
No hub or router. They are connected through simple lan.
Linux machine: has two lan cards, one for Ethernet modem and second for local lan. Shorewall is running on it.
Windows machine: simple accessing internet as Linux machine the Gateway.
i've made changes in /etc/services and /etc/inetd.conf.
now http://localhost:901/ is bringing the swat.
But now i'm not getting the way that what setting should i make in order to share resources of linux machine and windows.
Trying and reading tutorial for last 2-3 days but still nowhere.
Could anyone please help me out ???
regards
|
|
|
12-24-2005, 06:22 PM
|
#2
|
Member
Registered: Jan 2004
Location: Los Angeles
Distribution: Slack64 14.1
Posts: 581
Rep:
|
Quote:
share resources of linux machine and windows
|
What do you want to share. Printers, Disks, what. And who owns the resources.
Cheers,
Eddie
|
|
|
12-24-2005, 10:51 PM
|
#3
|
Senior Member
Registered: Jan 2005
Distribution: Slackware, BackTrack, Windows XP
Posts: 1,020
Original Poster
Rep:
|
Quote:
Originally Posted by MQMan
What do you want to share. Printers, Disks, what. And who owns the resources.
Cheers,
Eddie
|
Hi MQMan,
i would like to share disk only.
Now i've moved one step ahead. On windows machine i can see the Linux Machine's folder in "work group" computers.
but when i'm trying to open that its asking for password. Now i'm not getting the way. Should i make the same user on both linux or windows machine having same password or which user its asking for......I tried giving it the "root" and its password, but i didn't worked.
I'm trying and probably will configure it today.
Any suggestions are welcome.
regards
|
|
|
12-25-2005, 08:29 AM
|
#4
|
Senior Member
Registered: Jan 2005
Distribution: Slackware, BackTrack, Windows XP
Posts: 1,020
Original Poster
Rep:
|
Configured !!!
now i'm being able to access the linux machine from the windows machine.
But facing a problem that not being able to access "/root" from windows machine. The shared part is "/"
and the authentication is given to a user of linux machine.
So i think the problem is with the user account.
I'm cheking.......any suggestion will be appriciated.
Quote:
# Samba config file created using SWAT
# from 127.0.0.1 (127.0.0.1)
# Date: 2005/12/25 19:29:16
# Global parameters
[global]
workgroup = MSHOME
server string = Samba Server
log file = /var/log/samba.%m
max log size = 50
dns proxy = No
hosts allow = 192.168.0.2
[homes]
comment = Home Directories
read only = No
browseable = No
[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes
browseable = No
[MyRoot]
path = /
valid users = bond
|
note: bond is the normal user on linux machine. And i've set up it as the client for windows machine using the "password" option in SWAT.
regards
|
|
|
12-25-2005, 02:07 PM
|
#5
|
Senior Member
Registered: Dec 2005
Location: Brisbane, Australia
Distribution: Slackware64 14.0
Posts: 4,141
Rep: 
|
It sounds like you're saying the bond user cannot access the root user's home directory - that's normal behaviour and Samba won't be able to override it. Samba can provide access up to the level provided by the OS but no more. So you also won't be able to do anything via Samba that you can't do as the bond user on the Linux box.
|
|
|
12-26-2005, 11:02 AM
|
#6
|
Senior Member
Registered: Jan 2005
Distribution: Slackware, BackTrack, Windows XP
Posts: 1,020
Original Poster
Rep:
|
Quote:
Originally Posted by gilead
It sounds like you're saying the bond user cannot access the root user's home directory - that's normal behaviour and Samba won't be able to override it. Samba can provide access up to the level provided by the OS but no more. So you also won't be able to do anything via Samba that you can't do as the bond user on the Linux box.
|
Ya u seems to be right.
But how should i overcome this problem ???
Should i make a "smbpasswd" for "root" and then try accessing the 'root' from samba as 'root' the user.
will it work ???
regards
|
|
|
12-26-2005, 03:03 PM
|
#7
|
Senior Member
Registered: Dec 2005
Location: Brisbane, Australia
Distribution: Slackware64 14.0
Posts: 4,141
Rep: 
|
AFAIK you could run `smbpasswd -a root` and make sure that root is not listed in any 'invalid users' clauses in /etc/samba/smb.conf to give the root user access via samba. It is also possible to use the 'admin users' directive for a share in /etc/samba/smb.conf and have those users able to act as the root user for that share.
Both of these methods have security risks - once you have remote root access to a box, not only are you open to vulnerabilities on the main box, but the vulnerabilities of the remote boxes as well. If you were setting up these boxes in a work environment I'd say DON'T DO THIS!!!! If these are boxes in your home and you decide that the convenience of browsing your Linux box as root from other boxes outweighs the risks I'll just mind my own business... :-)
|
|
|
12-26-2005, 08:10 PM
|
#8
|
Senior Member
Registered: Jan 2005
Distribution: Slackware, BackTrack, Windows XP
Posts: 1,020
Original Poster
Rep:
|
Quote:
Originally Posted by gilead
If you were setting up these boxes in a work environment I'd say DON'T DO THIS!!!! If these are boxes in your home and you decide that the convenience of browsing your Linux box as root from other boxes outweighs the risks I'll just mind my own business... :-)
|
Hello gilead,
I'll definitely give it a try next week, since my friend has taken the laptop for a week.
And regarding the security...both of the systems will we with me only at the same place.
Thanx for being concerned.
regards
|
|
|
All times are GMT -5. The time now is 03:28 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|