Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I hope someone can help me with this. I am currently having problem getting my Windows machines (Windows 98 and 2000) to see my Samba server in Network Neighborhood or My Network Places. I have configured encrypted passwords on my Samba Server. I have configured my Samba server to be in the same workgroup as the Windows machines. The physical network connection is okay.
The name of the Samba server is linuxking and when I type "\\linuxking" on my Windows machines, I get the message "\\linuxking is not accessible
The account is not authorized to log in from this station". This should not be happening because I have the same account of "kingsley" on my Windows 2000 machine as well as in the Samba server, and the passwords are the same too.
I can use 'smbclient' to access shared folders on my Windows machines. On my Windows 2000 machine, I would type in 'smbclient //nb-kingsley/c -U kingsley' and then enter a password, I would able to access the C drive on my Windows 2000 machine.
So, if anyone can tell me or give me an idea why I can get my Windows machines to see my Samba server, I would appreciate that.
Thank you for the tips.I have made some progress, but not quite there yet.
By the way, my LAN of some 10 computers has the IP address of 192.168.10.
The workgroup names are exactly the same alright. The reason why my Samba server was not visible in 'My network places' was because I did not configure under the global settings, the "Configure remote browse list synchronisation here" and "Cause this host to announce itself to local subnets here". I have changed that and have restarted smbd and nmbd.
Okay, now I'm able to see the linuxking Samba server on 'My Network places'. However, I'm still not able to access the resources on the Samba server. I still get the message "\\Linuxking is not accessible. The account is not authorized to log in from this station".
And yes, I did use 'smbpasswd -a <username>' and made sure I added the same username that I used in my Windows machines.
And I did make sure that the hosts allow has 192.168.10.
This is how my /etc/smb.conf look like:
#======================= Global Settings =====================================
# workgroup = NT-Domain-Name or Workgroup-Name
workgroup = asdionsg
# server string is the equivalent of the NT Description field
server string = Samba Server
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
; hosts allow = 192.168.1. 192.168.2. 192.168.10. 192.168.11. 127.
# Security mode. Most people will want user level security. See
# security_level.txt for details.
security = user
# Use password server option only with security = server
; password server = <NT-Server-Name>
# Password Level allows matching of _n_ characters of the password for
# all combinations of upper and lower case.
; password level = 8
; username level = 8
# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
; encrypt passwords = yes
; smb passwd file = /home/smbpasswd
# The following are needed to allow password changing from Windows to
# update the Linux sytsem password also.
# NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
# NOTE2: You do NOT need these to allow workstations to change only
# the encrypted SMB passwords. They allow the Unix password
# to be kept in sync with the SMB password.
; unix password sync = Yes
; passwd program = /usr/bin/passwd %u
; passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
# Unix users can map to different SMB User names
; username map = /etc/smbusers
# Configure remote browse list synchronisation here
# request announcement to, or browse list sync from:
# a specific host or from / to a whole subnet (see below)
; remote browse sync = 192.168.3.25 192.168.10.255
# Cause this host to announce itself to local subnets here
; remote announce = 192.168.10.255 192.168.2.44
# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
; local master = no
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33
Okay, I have more or less solved the puzzle, mostly from reading the book 'Samba Unleashed'.
You should make sure that the Samba server is in the same workgroup or same domain that your LAN is located in. In my case, I have a Windows 2000 domain called 'timblet.com' and my domain controller is timbletserver1. In Windows NT or 2000 Server, you need to add the Samba server into your domain. in Windows 2000, go to Active Directory Users and Computers and under your domain, go to 'Computers'. Right click and select "New, Computer" from pop-up menu. The New Object - Computer window will appear and you add the name of your Samba Server (linuxking in my case) to both "Computer name" and "Computer name (pre-Windows 2000)" and check the box for "Allow pre-Windows 2000 computers to use this account".
Then you got to join the Samba server to the domain. I typed "smbpasswd -j timblet.com -r timbletserver1" (you probably have to make sure that your /etc/hosts and /etc/lmhosts files contain the right address mappings. If you joined the domain successfully, which I did, you should get the message something like:
smbpasswd: Joined domain timblet.com
It wouldn't be a bad idea to specify the parameter 'netbios name = linuxking' in the Global settings, though I don't think it is truly necessary.
One of the most important settings to ensure that your client can access the Samba server successfully is the 'security' parameter.
For me, I used 'security = server' and then 'password server = timbletserver1'. The first parameter means that all the authentication is done by the domain controller server (in this case timbletserver1), probably rightly so because timbletserver1 is the domain controller for all the machines on the LAN. So, Samba will now not do any authentication. You will now not need to have an account in the Samba server at all. As long as your username is in the domain controller, you can access the resources on the Samba server.
Encrypt passwords for me will be set to yes. My remote announce is 192.168.10.255. By the way, I did not know that the semi colon means that the line is commented. I only thought that the pound sign means that the line is commented.
After all the changes to /etc/smb.conf, restart smb.
I am now able to browse the linuxking in "My Network places" and see all the shares available. However, there is still a slight problem. While I can access the shares, see the files and can copy files from the Samba server over to my Windows 2000 Pro computer by drag and drop, I am unable to copy files to the Samba server.
Let's say I want to copy a text file called simple.txt to the root directory of the Samba server by drag and drop. However, it will give me the message "Cannot copy simple.txt: Access is denied. The source file may be in use". I can assure you that the simple.txt file in not in use so it is not an issue here.
Can someone please enlighten me as how to solve this problem?
I am having the same problem the guy above did, I can view the share from my win2k box, browse and copy from. But I cannot copy too, and I also cannot start a session from the linux box. from the linux box it says error connection to 192.168.0.100 (operation already in progress).
This is a small home network with no DNS, I have the samba set to be a WINS servers and my 2k box set to gets wins from the linuxbox IP. I did the smbpasswd -a deal and I modifed the folder security by right clicking on the folder that's shared and allowing all users to read/write. no luck, I'm thinking my main problem is that I cannot inniate a session from the linux box. I will post my smb.conf next.. Thanks
chmod will work for both folders and files. make sure that the user you are working with has access to an administrative or root account. if you are not worried about security over shares, you might just want a share-level share with the default user as root and no password authentication. its the easiest way to avoid having to enter all of the users and such.