Linux-Windows 2000

Samba is the answer. You need to have Windows and Linux have the same work group name and of course on the same subnet.

You may need to use LMHOSTS file. The lmhosts file will allow your Windows computer to locate other computers broadcasting SMB(Session Message Block protocol) without requiring a NetBios nameserver.

You can have linux as a server or a client and setup vary!

If you don't have documentation for setting up and configuring samba try:
http://www.linuxdoc.org/HOWTO/SMB-HOWTO.html

good luck.

I agree that Samba is the best answer (it's also the one I use in a mixed W2K/Linux network). However, you will need to make sure you obtain a recent release of Samba (I believe 2.0.7 is the current release) as there are some W2K issues with earlier versions.

paul

Note; you will need to put a registry patch on each of your Windows machines for a plain text password in order for them to integrate with the Samba machine.

I have integrated a Corel Linux server running Samba 2.0.7 with my office's Novell and Windows NT4 servers. The Linux server looks just like our other PDC (it is in it's own domain) to all the other machines. Several people authenticate from it for Windows networking, and overall it is a much better NT server than NT is, with the exception of running MS apps.
John Kozura IV
IS Manager
AICPA/PDI

Samba can be configured to use encrypted passwords such that you do not have to do the Windows registry editing stated in Answer #3 to send clear-text passwords, a potential security risk. Also, Samba can redirect user authentication to an NT/2000 domain controller so that a user database does not have to be configured and maintained on the Linux box. See the HOW-TO link from Answer #1 for details on these and other useful settings. I have integrated a RedHat Linux server into an NT enterprise using Samba, and as far as the network is concerned, it is just another Windows box.

Samba is probably the best answer but you can also use Services for Unix to make the interaction of linux with windows more easily managed from the windows side as opposed as configuring everything on the Linux side.

To share files on Linux machine you need to install Samba (www.samba.org). To mount Windows shares under Linux make sure that your Linux kernel is compiled with smbfs support (or insmod the appropriate module). Also I recomend you to install the latest Samba release (2.0.7 at the moment) because previous versions has some Win2K incompatibilities issues. Look at the Samba announce page (http://us1.samba.org/samba/whatsnew/samba-2.0.7.html):
--- from here ---
The Samba Team is pleased to announce Samba 2.0.7.

This is the latest stable release of Samba. This is the
version that all production Samba servers should be running
for all current bug-fixes. This version has been tested
against Windows 2000 and has no *known* issues with that
release of Windows.
...
Windows 2000 Issues
-------------------

This version of Samba has been tested with Windows 2000 and
the five known incompatibilities with Windows 2000 have been
fixed. See the "Changes in 2.0.7" list below for details.
--- to here ---

Check out the "windows services for unix" they are compatible with linux and very easy to configure

SAMBA is indeed the best, and correct answer.
IF Samba is not yet installed on your Linux system (it should be installed by default, unless you chose not to install it when you installed Linux).
At first, even before thinking of configuring Samba,you should be sure that your Linux kernel is compiled with support for the "smbfs" filesystem, otherwise you should do this at first.
Then afterwards you should edit the /etc/smb.conf file to configure Samba, and then restart the daemons.

The best place for the complete configuration is "http://www.samba.org".

Hope this helps.

Jacques

Samba is required to access Linux files from windows machine. But to access Windows files from Linux machine you have to configure NFS (Network File System). In this case you have to give share name (i.e. rights \\machine-name\sharename user) in export.cfg file.

I use ftp.

Samba is the right answer, it has everything you need to access data from windows network at your linux system.

I have set up an Linux Slackware 3.6 with samba as a BDC (Backup Domain Controller) so if Win2k is your PDC you will find in FAQ how to set it up.

Besides, samba come with an administration web interface which runs on a web port, so you can change the configuration very easyly and every parameter is documented via links to the help file.

Runs on a IDE software raid array as afile server for 35Gb of 10thousends of image file (TIF), and rocks over NT 4 in the same hardware configuration.

Go for it !

Since your Linux-mandrake system received IP via DHCP, I assumed that it was installed as a workstation. You are also running Windows 2000 advanced server, so I'm assuming that you want to centralize all files on the Windows 2000 server. If this is the case, you might want to look at Unix service that comes with Windows 2000. This configuration will allow you to share files to both the Windows Workstations (you didn't mention other systems, so I assume they are Windows base) and Linux Workstation. Unless you want to learn how to configure Samba to share files to other Windows Workstations as well, I suggest keeping all the shared files on the Windows 2000 server. The less complicated your network, the less headache you will have to deal with later.

Good luck,

Yes, Samba is the answer. You can configure a linux machine running samba to participate in a windows environment. To do this, you have to make sure the smb service is running at startup, then you have to correctly modify your samba configuration file (/etc/smb.conf) to suit your needs. The file usually has a number of commented lines which give basic instructions on how to configure the file. Also, there are a number of books on the subject. However, I have found that the best source of info on for this is the samba web site (http://www.samba.org). Follow the "documentation" link at that web site, and you will get detailed inormation on how to configure samba. When you have edited and saved the smb.conf file, you will want to test all of the parameters of the file, to make sure everything is correct. To do this, issue the command "testparm /etc/smb.conf" without the quotation marks. If you recieve no errors, then you are ready to re-start samba to initiate the changes. To do this, issue the command "samba restart" without the quotation marks. Once this is done, you should be able to create shares in the directories specified in the smb.conf file, and make them usable to windows computers on your network. Another thing you will have to watch out for is permissions. You can create public shares and give permissions to everyone, or you may want to create users on the linux system, and give permissions only to those users.

You have pick an excellent version of Linux
here is a copy of the file that i use for connection from NT4, 2000, 95/98 and linux workstations.

[global]
log file - /var/log/samba/log.%m
comment = server
default = share
netbios name = server
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
security = share
server string = Samba Server
unix password sync = no
encrypt passwords = no
map to guest = never
password level = 0
null passwords = no
os level = 0
preferred master= no
domain master = no
wins support = no
dead time = 0
debug level = 0
load printers = yes

[homes]
comment = Home Directories
read only = no
guest ok = yes
hosts allow = 192.168.0.*(depends on ip used)

[printers]
comment = All Printers
path = /var/spool/samba
print ok = yes
browseable = no
public = yes

[share]
path = /home/share
read only = no
guest ok = yes

please note the line with the comment, you may be using a different ip address, dont put in the bracketedcomment. copy the original smb.conf to a backup directory and start off with only the above text in the file, restart your system and you should be able to see the server in your network neighbour hood and the home directories

good luck

Samba is probally the best if not only way to go!

depending on your network, if security is not an issue..(not conected to the internet or have a good firewall). Why not just create a virtual directory in ftp? then any ftp client can access it. you can use which ever means of security you like under iis to control who can connect nd what they can do (read /read write/change). this is a lot easier than dealing with samba and has the same end result.

Yes, without a doubt, SAMBA is the answer. We have done something similar for a customer.

Good luck

No.

Samba is infact the answer but also
Try Windows services for Unix

Samba is the answer, what is the question? Do you want to share files FROM Win2k to Linux (use Samba client on Linux). Do you want to share files from Linux to just the server (use a variety of items - Samba on Linux, Unix services on Win2k, othernfs software on Win2k). Share Linux to all (use Samba on Linux) OR:
Share the info as above to the server only, then use the sharing capabilities of Windows2k to share out to you client machines. This is the approach of the Gateway services for Netware. This allows you to have only one server for people to connect to, then the server handles all connections to the Linux system.

HTH
-Aaron

Samba for sure - best solution for your setup.

Dear Montyo,

i think it is not necessary to mention that Samba is a quite good Way to access Linux Files via Windows Clients, because it has been mentioned very often here. It is very easy to configure. Just edit /etc/samba.conf and activate it in /etc/rc.config . Some Postings above, was a good sample of a Samba Config File.

Rovok

This question was closed by the author