Re: [suse-kde] connect to windows file server
List, I solved this problem on a Windows domain based network. I have SLSS 8. My eventual solution was to mount the Windows network drives at boot time. I did the following: - Ensure your system partition is of type: reiserfs - Setup my machine with Samba. - Configured samba as follows: http://www.linuxquestions.org/questions/archive/2/2004/03/4/155887 to get it onto my domain as a Backup Domain Controller. This setup must work before moving on. - Create folder /mnt/winshare and ensure all Linux accounts that need access can access this share folder - Edit the /etc/fstab file and add the boot time mount point entry to the end of it as follows: //winsrvname/winsharename /mnt/winshare smbfs username=winusername,password=winpword,rw,umask=000 0 0 If all is setup correctly this should do the job. I am in a hurry so I may have left something out - I had to search around a bit as my server is off right now. Hope this helps - it worked fine for me. --------------------------------------------- Jonathan Hughes Technical Support Specialist Goodyear South Africa --------------------------------------------- MCSE / MCP Registered Linux User # 362669 ============================================================================== When my parents finally realised that I was kidnapped, they snapped into action immediately: they rented out my room. -Woody Allen ============================================================================== The information in this e-mail contains confidential and / or proprietary information and is intended solely for the addressee. Access to this e-mail by anyone else is unauthorised and may not be copied or disseminated without the express consent of The Goodyear Tire & Rubber Company or one of its subsidiaries. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted in reliance on this, is prohibited and may be unlawful. Whilst all reasonable steps are taken to ensure the accuracy and integrity of information and data transmitted electronically and to preserve the confidentiality thereof, no liability or responsibility whatsoever is accepted if information or data is, for whatever reason, corrupted or does not reach its intended destination. Daniel Eckl <daniel.eckl@gmx To: suse-kde@suse.com .de> cc: Subject: Re: [suse-kde] connect to windows file server 07/29/04 07:04 PM Hi Kardianto! I think he wants to have the other way. He don't want to serve files from a linux server. He wants to use linux as client to get files from a windows share. You just can use KDE's built in functions. Login to kde as user, use the control panel for configuring your network-browser settings and then open a konqueror window and type smb:/ or smb:/workgroup or smb:/hostname Daniel Am Donnerstag, 29. Juli 2004 21:20 schrieb carlos:
On Wed, 2004-07-28 at 22:50, Kardianto Cakra wrote:
Hi all,
Is anyone know what is the easiest wa to use linux suse as a client for windows file server and print server? Because I find linux is very suitable for a workstation until I can't print or share file or download a share file through windows file server. It's like I can't be free from windows bind. Please guide...
Hi, I can't help with file sharing ('cause I haven't really explored it yet, but that's supposed to be the easy part), but I just set up 2 W2K boxes to print to the HP DJ932c connected to my SuSE 9.1 box.
Do the following as root:
1) Make sure the Linux domain is the same as your W*ndows workgroup name (W*ndows: Control Panel > System > Network Identification)
Make sure Samba is running. You can use Yast2 for this.
2) Make sure to add the W*ndows users as regular Linux users on the SuSE box, with the same passwords they use on the W*ndows boxes. (again, Yast2)
3) Enable SWAT (for Samba administration through a browser). Open /etc/xinetd.d/swat with your editor, and change disabled = yes to disabled = no
4) Restart xinetd: >/etc/init.d/xinetd stop >/etc/init.d/xinetd start
5) Load SWAT (http://localhost:901)
6) Make sure the following lines are in the [globals] section of your Samba configuration:
encrypt passwords = yes use client driver = yes
If any W*ndows usernames are mixed-case, add this, too:
username level = 3
7) Add the W*ndows users to the Samba users. Click "Passwords" and add each user's name/pw.
Now, on each W*ndows box (I'm assuming TCP/IP is already loaded):
1) Start > Settings > Printers > Add Printer > Network printer 2) Browse the network to find the linux printer.
(you may need to load the printer drivers locally on the W*ndows boxes)
Go back to SWAT, where you should see the connections from the W*ndows boxes.
Try printing from W*ndows.
I don't think I missed any steps, but if you get error messages, Google them (search Google with the exact error message in double-quotes). That's how I got it to work.
Cheers,
Carlos
-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e
Hi Jonathan! Setting a linux client as backup domain controller just to mount the shares is unnesseccary and can be dangerous to the domain controller system if it's not correctly planned. You don't need such stuff to just be client and connect to windows shares. If you set up your network browser settings correctly in KDE control center, then you even don't have to mount a share directly, but you can use the smb:/ kio plugin which is much more flexible (nearly as flexible as in windows with network neighborhood). But if you want to use a permanent mount, then just do this: Edit your /etc/samba/smb.conf Correct the values: workgroup = <WORKGROUP> # In domains this is simply the domain name. encrypt passwords = yes # should be default, but to be sure local master = no # don't mess up with domain controllers name resolve order = wins,host,bcast # change to try wins first, if your \ network has one wins server = <ip-address1> <ip-address2> # ask this wins servers wins support = no # don't act as wins server by yourself!!! Edit your /etc/samba/smbfstab Enter something like this (in one line): //windows-server/sharename /local/mountpoint cifs username=<loginname>;password=<password> Now it will be mounted at boot. If you want to use kio_smb instead of mounting, then it's not bad to configure smb.conf as shown above, too. Then configure the settings in control center and then use smb:/ as your liking. You can even combine that and mount only some few shares you need every time and use temproary shares with smb:/ Daniel Am Freitag, 30. Juli 2004 08:46 schrieb jonathan_hughes@goodyear.co.za:
List,
I solved this problem on a Windows domain based network. I have SLSS 8. My eventual solution was to mount the Windows network drives at boot time. I did the following:
- Ensure your system partition is of type: reiserfs - Setup my machine with Samba. - Configured samba as follows: http://www.linuxquestions.org/questions/archive/2/2004/03/4/155887 to get it onto my domain as a Backup Domain Controller. This setup must work before moving on. - Create folder /mnt/winshare and ensure all Linux accounts that need access can access this share folder - Edit the /etc/fstab file and add the boot time mount point entry to the end of it as follows: //winsrvname/winsharename /mnt/winshare smbfs username=winusername,password=winpword,rw,umask=000 0 0
If all is setup correctly this should do the job. I am in a hurry so I may have left something out - I had to search around a bit as my server is off right now.
Hope this helps - it worked fine for me.
--------------------------------------------- Jonathan Hughes Technical Support Specialist Goodyear South Africa --------------------------------------------- MCSE / MCP Registered Linux User # 362669 =========================================================================== ===
When my parents finally realised that I was kidnapped, they snapped into action immediately: they rented out my room. -Woody Allen =========================================================================== ===
The information in this e-mail contains confidential and / or proprietary information and is intended solely for the addressee. Access to this e-mail by anyone else is unauthorised and may not be copied or disseminated without the express consent of The Goodyear Tire & Rubber Company or one of its subsidiaries. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted in reliance on this, is prohibited and may be unlawful. Whilst all reasonable steps are taken to ensure the accuracy and integrity of information and data transmitted electronically and to preserve the confidentiality thereof, no liability or responsibility whatsoever is accepted if information or data is, for whatever reason, corrupted or does not reach its intended destination.
Daniel Eckl <daniel.eckl@gmx To: suse-kde@suse.com .de> cc: Subject: Re: [suse-kde] connect to windows file server 07/29/04 07:04 PM
Hi Kardianto!
I think he wants to have the other way. He don't want to serve files from a linux server. He wants to use linux as client to get files from a windows share.
You just can use KDE's built in functions.
Login to kde as user, use the control panel for configuring your network-browser settings and then open a konqueror window and type smb:/ or smb:/workgroup or smb:/hostname
Daniel
Am Donnerstag, 29. Juli 2004 21:20 schrieb carlos:
On Wed, 2004-07-28 at 22:50, Kardianto Cakra wrote:
Hi all,
Is anyone know what is the easiest wa to use linux suse as a client for windows file server and print server? Because I find linux is very suitable for a workstation until I can't print or share file or
download
a share file through windows file server. It's like I can't be free
from
windows bind. Please guide...
Hi, I can't help with file sharing ('cause I haven't really explored it yet, but that's supposed to be the easy part), but I just set up 2 W2K boxes to print to the HP DJ932c connected to my SuSE 9.1 box.
Do the following as root:
1) Make sure the Linux domain is the same as your W*ndows workgroup name (W*ndows: Control Panel > System > Network Identification)
Make sure Samba is running. You can use Yast2 for this.
2) Make sure to add the W*ndows users as regular Linux users on the SuSE box, with the same passwords they use on the W*ndows boxes. (again, Yast2)
3) Enable SWAT (for Samba administration through a browser). Open /etc/xinetd.d/swat with your editor, and change disabled = yes to disabled = no
4) Restart xinetd: >/etc/init.d/xinetd stop >/etc/init.d/xinetd start
5) Load SWAT (http://localhost:901)
6) Make sure the following lines are in the [globals] section of your Samba configuration:
encrypt passwords = yes use client driver = yes
If any W*ndows usernames are mixed-case, add this, too:
username level = 3
7) Add the W*ndows users to the Samba users. Click "Passwords" and add each user's name/pw.
Now, on each W*ndows box (I'm assuming TCP/IP is already loaded):
1) Start > Settings > Printers > Add Printer > Network printer 2) Browse the network to find the linux printer.
(you may need to load the printer drivers locally on the W*ndows boxes)
Go back to SWAT, where you should see the connections from the W*ndows boxes.
Try printing from W*ndows.
I don't think I missed any steps, but if you get error messages, Google them (search Google with the exact error message in double-quotes). That's how I got it to work.
Cheers,
Carlos
-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e
participants (2)
-
Daniel Eckl -
jonathan_hughes＠goodyear.co.za