LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 04-19-2004, 05:47 PM   #1
chasn
LQ Newbie
 
Registered: Apr 2004
Distribution: Slackware 9.1
Posts: 24

Rep: Reputation: 15
Will I ever be able to see Linux from XP Home?


I'm going round in circles reading stuff on Samba. What I need to know is: am I wasting my time?

I have a simple little home network - 2 Windows XP Home PC's, connected to a router/switch/modem that gives me broadband internet. The Windows network was setup using the darn Network Wizard, so I have no idea what sort it is - just a normal one! I also intermittently connect my Win98 laptop to the network. I use it for file transfer, backup etc. I know the router does my DHCP stuff for me.

I have put Slackware on one of the 2 PC's, dual booting. Right from installation, Slackware found my router and I have internet access.

I have started to get a grip on the client end of Samba - I have used smbclient to list some files on the other XP PC, and will soon be able to do what I need.

To view Slackware from the XP machine, I suppose I have to come to grips with smb.conf, though it looks like it's going to need a 12 month Masters course to be able to transfer a file.

BUT, I keep coming across references like this one (which happens to be from the Samba 3 How To):
"Note - Windows XP Home edition cannot participate in Domain or LanManager network logons"

Is this the same as saying that my other Windows XP home machine will never be able to see the files on the Slackware machine?

If so, I'll stop trying to understand smb.conf.
 
Old 04-19-2004, 06:01 PM   #2
Muzzy
Member
 
Registered: Mar 2004
Location: Denmark
Distribution: Gentoo, Slackware
Posts: 333

Rep: Reputation: 30
Samba should work fine with XP, you just need to persist with samba.conf.
 
Old 04-19-2004, 06:03 PM   #3
Peacedog
LQ Guru
 
Registered: Sep 2003
Location: Danville, VA
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,296

Rep: Reputation: 168Reputation: 168
samba is not that bad for small home networks, it's highly configurable though, so it's easy to get lost in the all the muck. post your smb.conf and let's have a look.
 
Old 04-19-2004, 06:05 PM   #4
chasn
LQ Newbie
 
Registered: Apr 2004
Distribution: Slackware 9.1
Posts: 24

Original Poster
Rep: Reputation: 15
Thanks, Muzzy.

So you are saying that XP Home will be able to look at the Slackware machine even though it can't "participate in Domain or LanManager network logons"? i.e participating in Domain or Lan Manager logons is something more complicated than I will need?
 
Old 04-19-2004, 06:05 PM   #5
HadesThunder
Member
 
Registered: Mar 2004
Location: London
Distribution: Mandrake 9.1
Posts: 281

Rep: Reputation: 30
sounds more like a windows bug to me
 
Old 04-19-2004, 06:07 PM   #6
qwijibow
LQ Guru
 
Registered: Apr 2003
Location: nottingham england
Distribution: Gentoo
Posts: 2,672

Rep: Reputation: 47
And all that hastle JUST because microsoft felt like being different...
why cant MS Windows read NFS file system just like every other decent network operating system.

I also had a similar problem.
in the end i just gave up and used FTP and a web browser to move files.

maybe this is an acceptable sollution ?

it doesnt sound like you *need* a netowrk file system... you just want to move files around correct ?
 
Old 04-19-2004, 06:09 PM   #7
chasn
LQ Newbie
 
Registered: Apr 2004
Distribution: Slackware 9.1
Posts: 24

Original Poster
Rep: Reputation: 15
Quote:
Originally posted by PEACEDOG
post your smb.conf and let's have a look.
Thanks. Well, I will if you want, but I don't have one of my own yet - so all I would be posting is the sample one that comes with the install. And I guess you know what that looks like.
 
Old 04-19-2004, 06:16 PM   #8
Peacedog
LQ Guru
 
Registered: Sep 2003
Location: Danville, VA
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,296

Rep: Reputation: 168Reputation: 168
no need to post the sample file, it's a ton of stuff you probably will not need anyway. here, i'll post a simple starter for you

Code:
[global]

   workgroup = yourworkgroup
   netbios name = yournetbiosname
   server string = Samba Server %v
   security = SHARE
   encrypt passwords = Yes
   map to guest = Bad User
   log file = /var/log/samba/log.%m
   max log size = 50
   socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
   printcap name = cups
   dns proxy = No
   printer admin = @adm
   printing = cups

# to share a directory

[share]
   comment = shared directory
   path = /path/to/shared/directory
   public = yes
   browsable = yes
   writeable = yes
as long as you make provisions for your network w/your firewall, that should get you started.

Last edited by Peacedog; 04-19-2004 at 06:18 PM.
 
Old 04-19-2004, 06:18 PM   #9
chasn
LQ Newbie
 
Registered: Apr 2004
Distribution: Slackware 9.1
Posts: 24

Original Poster
Rep: Reputation: 15
Quote:
Originally posted by qwijibow
I also had a similar problem.
in the end i just gave up and used FTP and a web browser to move files.

maybe this is an acceptable sollution ?

it doesnt sound like you *need* a netowrk file system... you just want to move files around correct ?
Well I suppose I could use FTP. But then I could use my zip drive! Or transfer stuff from my ext3 drive to a FAT32 partition on the dual boot machine that I set up - then reboot to XP on the dual boot machine, and use the Windows network to transfer that way. But all of these are naff

And despite sounding pathetic, I actually do want to move over to Linux 100% at some point, once I've got it wife proof. And amongst the many things I hate about MS is its opacity - I really like the fact that with Linux, especially Slackware, there are no wizrds to conceal what's going on, so I stand a chance of understanding my own computer.

Also, currently I have one printer attached to the other machine, so it would be convenient to be able to print that way - I suppose I could attach the printer to the dual boot machine, but it seems like chickening out.

I'll put the effort in to master smb.conf, if people are sure that in the end it's possible to have a small home network consisting of one XP Hoem machine and one Linux machine
 
Old 04-19-2004, 06:24 PM   #10
qwijibow
LQ Guru
 
Registered: Apr 2003
Location: nottingham england
Distribution: Gentoo
Posts: 2,672

Rep: Reputation: 47
LOL.... Wife proof.

I heard a rumour that MS had sucessfully won the right to charge fees to any opensource program that uses the windows API's. aparently trying to kill Samba and Wine....

is this true ?
i heard it on slashdot... so u know. LOL.

Maybe you could put your printer on the linux machine.
in university, the print machines are all UNIX, and windows seems to handle them fine.
not sure if windows suports cups.
 
Old 04-19-2004, 06:27 PM   #11
mrcheeks
Senior Member
 
Registered: Mar 2004
Location: far enough
Distribution: OS X 10.6.7
Posts: 1,690

Rep: Reputation: 51
PEACEDOG i suppose you changed
workgroup=yourworkgroup by your windows workgroup and that both pcs are part of the same workgroup
same for other default values.
 
Old 04-19-2004, 06:29 PM   #12
Peacedog
LQ Guru
 
Registered: Sep 2003
Location: Danville, VA
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,296

Rep: Reputation: 168Reputation: 168
for the printer have a look here

http://www.faqs.org/docs/Linux-mini/...ing_to_windows

it's a debian howto, but, it's generic enough to use.
 
Old 04-19-2004, 06:38 PM   #13
mrcheeks
Senior Member
 
Registered: Mar 2004
Location: far enough
Distribution: OS X 10.6.7
Posts: 1,690

Rep: Reputation: 51
my bad i was confusing you PEACEDOG with the original poster , i hope he did change default values
 
Old 04-19-2004, 06:44 PM   #14
Peacedog
LQ Guru
 
Registered: Sep 2003
Location: Danville, VA
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,296

Rep: Reputation: 168Reputation: 168
Quote:
my bad i was confusing you PEACEDOG with the original poster , i hope he did change default values
actually, i have several workgroups, but, i run win 2k, not xphome. all of my workgroups show up fine, and all of them can share directories.
 
Old 04-20-2004, 06:46 AM   #15
chasn
LQ Newbie
 
Registered: Apr 2004
Distribution: Slackware 9.1
Posts: 24

Original Poster
Rep: Reputation: 15
OK, for other newbies who might end up finding this thread, here's something like closure.

Thanks Peacedog, your sample smb.conf given earlier in this thread works just fine. You may be interested to see the experiment I did with the most minimal smb.conf that I could get to work, at the end of this post - not that I'm recommending it, I'm sure it's insecure (at least) and I will be using yours, but it does show how little is necessary to get the machines talking to one another.

For other newbies with an existing simple Windows home network, with an XP Home PC and a Linux PC (see first post in this thread for my setup, which is dead simple):

This is what I did
----------------------
Slackware 9.1 comes with Samba installed, but not configured.

1. To see the XP machine from the Slackware machine.

There was no configuration required.

1.1 At the bash prompt, I type:
smbclient //XPcomputer/"XP My Docs"
There's a pause, then some messages about IP addresses, then a password prompt. I just hit return and am rewarded with a new prompt
smb: \>

In the command above, 'XPComputer' is what that machine is called by Windows; to find it, on that machine right-click on My Computer, Properties, Computer Name - it's what's shown as 'Full Computer Name'. It's the name you gave it during Windows installation, if you did your own installation - else your supplier chose it for you.

'XP My Docs' is the relevant folder's share name on the XP computer; to find it, right click on the folder in My Computer, Properties, Sharing, and it's shown towards the bottom of the tab. It's the name you gave when you set up sharing for this folder.

"XP My Docs" is in double quotes - that's how smbclient copes with the spaces in the folder name. This also works for file names of course.

1.2 At the smb prompt various commands work, they are in Man smbclient.
e.g. 'ls' works just like for bash, and 'get' copies a file from the XP computer to the Slackware one e.g.
get mytest.txt /tmp/mytestcopy.txt
First it gives me a message saying it is getting the file, then it returns me to the smbclient prompt - it has copied mytest.txt from the XP My Docs folder on the XP machine to the /tmp folder on the Slackware machine, as mytestcopy.txt

1.3 To return to the bash prompt, type exit

2. To see the Linux machine from the XP Home machine

2.1 I put Peacedog's sample smb.conf in /etc/samba
In this file I edited:
2.1.1 'yourworkgroup' to be the same as the workgroup for the existing Windows network; you can get it from My Network Places, Entire Network, Microsoft Windows Network; it's the name you gave when you used the network wizard to set up the Windows network.
2.1.2 'Yournetbiosname' to be the same as this Slackware computer is called when it's booted as XP (bear in mind, I have a dual boot setup, so this machine already has a name on my existing Windows network- but maybe I could put anything here, not sure yet, more experimentation required).
2.1.3 'path/to/shared/directory' to /tmp (because that's the directory on the Slackware machine I wanted to experimentally try and share)

2.2 Started samba:
- cd /etc/rc.d
- chmod 755 rc.samba (as installed by Slackware, this has restricted read permissions only)
- ./rc.samba start
This gives me a message that Samba has started.
After a few moments, on the XP machine I go into My Network places, Entire Network, Microsoft Windows Network, MyWorkgroup.
And, miracle of miracles, there's a folder called 'share', browseable just like any Windows network folder.

That's it - about 2 minutes work.

When playing around with different smb.conf files, I tended to do ./rc.samba stop, then do the editing, then do ./rc.samba start. But quite likely it's only necessary to do ./rc.samba restart, after the editing - more experimentation required.

Only the start
-----------------
Much left to do of course:
- Currently this works as root - I haven't tried it as a user, but on past experience everything on Linux has to be set up twice, once for root and once for a normal user - in this case I guess I may have trouble using smbclient as a user, but we'll see.
- Currently this is all at the command prompt. KDE Konqueror does offer navigation on the network, but at the moment it takes minutes to respond to each click on a folder - more investigation and setup required
- Currently I am starting Samba manually - I need to find the right place in the init scripts to start it at boot.
- I haven't yet tried to set up printing from the Slackware machine to the printer attached to the XP machine.

How minimal can smb.conf be?
---------------------------------------
The Samba site has a good Samba manual. The first page (http://samba.mirror.ac.uk/samba/docs/man/install.html)
shows a couple of minimal smb.conf files, one with 3 lines, one with 4. Neither of these worked for me (permission trouble). But by editing out lines of Peacedog's file, I did get this to work:
Code:
[global]
   workgroup = MYWORKGROUP
   netbios name = DUALBOOTCOMPUTER
   security = SHARE
[share]
   path = /tmp
   public = yes
I'm certainly not recommending this - I really don't know what I'm doing, and even though I don't understand all the lines in Peacedog's sample file, it's obvious that eliminating some of them jeopardises security, and who knows what else. But when you consider that the man page for smb.conf has 5638 lines, it's amazing how simple it actually is.

What about the supposed problem with XP Home?
----------------------------------------------------------------
The comment in the first post comes from the Samba site, and there are other authoritative sites that say the same. Clearly there are some limitations on what can be done with XP Home and Samba.

But I guess it's a limitation on the use of XP Home as the operating system on client workstations in some varieties of enterprise network, that perhaps have a central Linux file server and everybody has to log on to the network - or something like this anyway.

At any rate, getting XP Home to talk to Linux is perfectly possible
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Apache Root/Home Directory and setting up FTP for home directories? Mankind75 Linux - Newbie 6 07-23-2006 03:37 PM
want to ssh/ftp to home machine (Slack) from office through home router fincher69 Linux - Networking 2 09-21-2005 11:55 PM
Is it possible to log onto your home linux box from another machine running linux?! Gormless Linux - General 7 10-26-2004 11:27 PM
Suggestions for my home network - Linux, other (non-Linux) users, Games, etc. lrt2003 Linux - General 5 05-06-2004 10:11 PM
Linux @work cnx to linux @home - Options? zaks_zoo Linux - Networking 5 12-22-2003 08:38 AM


All times are GMT -5. The time now is 02:28 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration