CentOS 5 Networking :: Samba Share Not Accessible From Windows Machine?
Feb 13, 2010
I have Linux installed on one machine with samba running and a second machine running XP. They are going through my router and I am using the same username/passwords for both machines and I have even gone to the point of allowing access to everyone for the share I created and the worgroup in samba is MSHOME just like my XP machine. When I view (or search) my workgroup computers my Linux machine shows up and so do the shares I created but when I try to open them I just get a message that permission is denied and I may not have permission to use this resource. I even tried setting access to the shared folder to 777 but still I can't open this share. Has anyone got any idea of why this is?
I am trying to see share files on my windows machine to my linux machine. I would like an answer to how to fix the problem. This is where i am at i am using my own network to learn who to use nmap properly. I ping my whole network with nmap -sS -O. Then i used nmblookup -a which gave me the infromation i needed. Then i run smbclient -L computername -I ip address -N
This will not show me the windows os this only show me my laptop. What can i change for this to show me the other computer on this network. The port i am wanting is open. I want to be able to mount the share files and move them to my computer i am going to use the commands put and get to move the files when i am able to get to the smb: >
I have ubunto desktop 10.04 LTS I installed samba and able to access the share on windows machines. However i want to access the share on 300 windows machine(for example) systems at a time Is it possible.
I have set up a Samba share via my CentOS 5 server (the samba share is actually a mounted filesystem, not local machine space). I have been successful in adding permissions for my windows users within the smb.conf, but have an additional need that I cannot figure out. I would like for my Windows administrators to be able to create folders and assign permissions from their machines (and their Windows GUI). Ultimately I need the folders on the Samba share to behave correctly when Windows group permissions are applied by these administrators.
When the folders are created, the "Everyone" identity cannot be deleted and sometimes "Creator Owner" or "Creater Group" show up. I have seen several threads start down this path, but haven't seen a definite answer (I may have just missed it!).
I am trying to set up samba in my CentOS virtual machine that is running on a Windows 7 host. I have found a tutorial in the How-Tos on this site but I'm not sure if they are exact and I'm paranoid about messing something up. The link to the tutorial is below. Is there anything that I should do different or anything that I should be aware of? Also, once this is set up, how do I transfer files between the two machines? Please note: I am very inexperienced in the IT field. [URL]...
I'm running Ubuntu 10.04 and Samba 4.The folder I've shared is on NTFS partition and though is visible from other Windows 7 system on LAN, can't be browsed. Even from my own computer if go to network places the folder is there but when I double click on it I get
using OEL 5.4, which uses Gnome 2.16 interface I can see my share from Windows, but whatever I do, I get messages that my share is not accessible. The whole user thing is quite complex, dont understand what user I should use on Windows, what password, what user should have what rights on linux.
I'll post smb.conf tomorrow ... The problem is that Windows lacks any decent error message, stating what kind of error message. Is there no Samba client for Windows?
We have an existing Windows 2000 network that I am trying to add an Ubuntu 8.04 server to. I have put links into the windows domain DFS to the linux machine's samba shares.
The shares work fine for local users that are physically on the same network (192.168.0.X). Remote users from other offices or dialing in with a vpn client can not access the these particular folders off the DFS. However, they can map them directly from the ubuntu server.
have a server here running opensuse 11.3 that I need to access via network using samba. Samba is working so far and I can ping the serve and browse the shares from windows (WinXP) computers; but only via the IP.Now I've read up on samba on this forum and other sources, like the official samba documentation and compared my smb.conf with an older one on another server which works (and even copied this one over to the new one) - to no avail.I seem to be missing something and I just can't find it.Since the problem is probably not in the smb.conf (previously working one doesn't work on new server) - where else could I have screwed up?
I used Samba to share some files. But when I try to share /home/username/download, it is not accessible by WindowsXP. But when I modified the dir to /opt/*. It is OK.
I'm running slack64-current.I setup samba to share a printer on my home network. I can print to the printer locally.The printer is visible on the network. However when I try to print anything on the printer via samba (or cups for that matter) from either the local machine or the remote machine, everything acts as if the job went through, but nothing happens. I'm sure I've seen this before on another slack machine that is currently unavailable, but I can't remember what the answer was, and I'm trying to be more precise with this setup so that I actually learn something.
smb.conf PHP Code: #======================= Global Settings=====================================
I am trying to establish the easiest way to share a folder from an Ubuntu machine to a Windows machine.In the past I have added things to smb.conf and that has all worked fine but what I am trying to do is to figure out what the "new user" way of doing this is so that when I am helping other people I know I am getting them to do the simplest thing.I completely removed samba and reinstalled it so that I didn't have any configuration. Right clicked on a folder and selected "Sharing Options" ticked the "Share this folder box" gave it a name and a comment and ticked the other two boxes.
When I went to the windows laptop then it kept asking for a username/password and nothing worked.Back on the ubuntu machine I did sudo smbpasswd -a [username] and created a blank password. Now from the windows machine I can access the shared folder.Is the smbpasswd step still required? It's very confusing for a new user as there is no suggestion that anything other than right clicking on the folder and choosing the options you want would be required. Is it something to do with the fact that this is an ubuntu machine that has gradually been upgraded through versions and this problem wouldn't have been there from a new install?
I try to access my ubuntu machine via my Windows Machine (Samba Server on Ubuntu Machine). Anytime I try to access the machine it asks me for my password...I enter it but it says it is invalid....is there anyway to reset it? I have already tried to remove and purge everything Samba related and then tried reinstalling, but that still didn't do anything
My network comprises three PC's .... Windows XP, Windows 98SE and Ubuntu 9.04 running SAMBA. All PC's are configured WORKGROUP=WORKGROUP. The network connection To/From XP/UBUNTU via SAMBA Shares works perfectly OK. However, despite scouring all forum information regarding changes to Win98 ENCRYPTION, (Registry change re: DWORD "EnablePlainTextPasswords"), the Win98 PC refuses to connect to UBUNTU. The UBUNTU PC can conect to all the Win98 shared folders OK. I have disabled my Linux Firewall (Firestarter), I have run SMBCLIENT to check the user password for Win98 and it is validated OK. The Win98 error message is ....
"\Inspiron 510m is not accessible. The computer or sharename could not be found. Make Sure you typed it correctly and try again."
My samba.conf file is as follows ..... Any help or assistance PLEASE !
#======================= Global Settings =======================
[global]
## Browsing/Identification ### # Change this to the workgroup/NT-domain name your Samba server will part of workgroup = workgroup # server string is the equivalent of the NT Description field code....
I have Samba 3.5.3-61 running on a Fedora Core 13 system. I created a share that is browseable to all systems, and I made sure to create a user account via the smbpasswd utility. When I try to connect to the server from a Windows XP system, I am able to enter the appropriate sharename as well as the username and password.
i did install and configure samba buy google tutorials. I can ping the centos box from windows but cannt access folder which is on centos. I can ping the machine.
I can't be the first one with this problem. What am I missing?
I have setup Samba servers in the past, just none under SELinux. The last one I configured was a couple years ago, so I wouldn't doubt I'm a bit rusty.
---- Environment summary: Clean server install of CentOS 5.4 includes SELinux - lets call this 'server' - updated samba to 3.0.33-3.15.el5_4.1
Client1 - Windows XP sp4 - WINS configuration uses 'server' noted above Client2 - Windows Vista - WINS configuration uses 'server' noted above
---- What works / what doesn't ------ Clients can see the server (XP and vista) in network neighborhood. The following does not work from windows (xp or vista) net view net view \server net view \server-ip net view \servershare
This does work on the server smbclient -L \server smbclient -L \server --user validuser smbclient -L \client1 --user validuser
---- What I have configured and tried (config/output below) -------- firewall ports for samba are open SELinux enforcing or permissive file context is set on share samba booleans are set
***firewall -A RH-Firewall-1-INPUT -s 192.168.0.0/24 -m state --state NEW -m tcp -p tcp --dport 445 -j ACCEPT -A RH-Firewall-1-INPUT -s 192.168.0.0/24 -m state --state NEW -m udp -p udp --dport 137 -j ACCEPT -A RH-Firewall-1-INPUT -s 192.168.0.0/24 -m state --state NEW -m udp -p udp --dport 138 -j ACCEPT -A RH-Firewall-1-INPUT -s 192.168.0.0/24 -m state --state NEW -m tcp -p udp --dport 139 -j ACCEPT
***SELinux mode/booleans # sestatus SELinux status: enabled SELinuxfs mount: /selinux Current mode: permissive Mode from config file: enforcing Policy version: 21 Policy from config file: targeted
# getsebool -a | grep smb allow_smbd_anon_write --> off smbd_disable_trans --> on
# getsebool -a | grep samba samba_domain_controller --> on samba_enable_home_dirs --> on samba_export_all_ro --> off samba_export_all_rw --> off samba_share_fusefs --> off samba_share_nfs --> off use_samba_home_dirs --> on virt_use_samba --> off
I'm trying to set up a VPN connection between our CentOS 5.3 server at work and my bosses XP computer at home. At this point, we are kinda locked into Quickbooks. I'm testing the connection from my XP boot at home to see if it works. I can log into our servicemanuals easily enough from XP at home however, the windows takes forever to update. I have the Samba server only listening on port 445 because is seems to work more efficiently at work. I connect to the Samba shares via linux from home and everything works well but, when I try to do anything with the shares from Windows client at home, it's very slow!
I'm thinking that it must have something either to do with the Windows OpenVPN client or the client.conf file. Is there anything I should look at in the .conf file for answers?
Can anyone point me in the direction of setting up shares for windows machines on centos. I have found a few document but never managed to get it up and running correctly. I need to be able to get access to subfolder etc for different users. Is there any way of doing it with some sort of gui?
I am trying to set up samba in my CentOS virtual machine that is running on a Windows 7 host. I have found a tutorial in the How-Tos on this site but I'm not sure if they are exact and I'm paranoid about messing something up. The link to the tutorial is below. Is there anything that I should do different or anything that I should be aware of? Also, once this is set up, how do I transfer files between the two machines?
I am trying to mount a file server directory on a client machine. I tried using NFS, but could not mount the share on the client. Several respobses were given to a post on this problem. but I still was not able mount the NFS share. I decided to try instead to mount the directory as a Samba share because I can already access it using Samba from windows, or from KDE or Gnome using smb://fileserver as a desktop location icon URL. When I try to mount the Samba share I get error messages that nearly identical those that occurred with NFS. . Here are some of the setup parameters
CentOS 5.4 on client and server behind a D-Link router server IP: 192.168.0.44 (can ping it client) client IP: 192.168.0.101 (can ping from server)
[code]....
This is the only error message that these commands have produced in the messages log, secure log or smbd log for either machine. My immediate goal is to set up the simplest possible local mount that will allow Grsync to backup to the file server.
he moved in a new place and there is a huge share on the network machine which runs windows... however he has fedora 10 installed on a desktop pc with a big screen and asked me to configure it so it can access the share... i have almost no experience with fedora and i've been trying to do this for two days now... i installed the samba package, but now what? how to do this because the exact commands are unknown to me... i have the root password and everything else on the network... so i just need to know what ot write in order to be able to mount all the TBs of information on the server...
I'm able to connect to a networked Windows machine and its shares using the Places -> Network -> Windows network interface, but unable to do so using smbclient at terminal command line. I can see the shares using:
smbclient -L //server -U username
But when issuing the command:
smbclient //server/service -U username
I get:
domain=[server] OS=[Windows Server 2003 R2 3790 Service Pack 2] Server=[Windows Server 2003 R2 5.2] tree connect failed: NT_STATUS_BAD_NETWORK_NAME
The share name has spaces, like
lab raid root share
I use 40 to fill in the spaces. This problem must be something fairly simple if I can connect via the Places GUI but not through the command line.
I'm giving up in ever hoping that I'll get printing working with windows 7 with the strange comments I've found on the net. Basically I have a samsung ML2240 printer shared on the network, everything can print to it fine except for my windows 7 laptop. It's shared via Samba.
Quote:
Once you have extracted the driver files, copy the 32-bit drivers to the /usr/share/cups/drivers directory and the 64-bit drivers to the /usr/share/cups/drivers/x64 directory exactly as named below:
[Windows 2000 and higher] ps5ui.dll pscript.hlp pscript.ntf pscript5.dll
However after checking this, I dont have the files named within int he correct folder on my windows system :
%WINDIR%SYSTEM32SPOOLDRIVERSX643 folder for 64-bit drivers.I've tried installing the printer via the windows installer, however this adds the driver then tells me its not working and fails to print. I really dont know where to turn with this one. I've tried installing the samsung supplied drivers from the website. However they still fail to connect.
ubuntu 9.04 and win xppro i've been pounding my head aganst this for hours now. reading anything i can find samba works mostly shares created from nautilus work fine from both ubuntu and windows if i check to allow guest access if not i can not log in it does work in the nautilus browser fine. shouldn't make a difference but am using a virtualbox win xp guest shares work without issue. printers work here is a dump of my service defenitions
[global] workgroup = HOME server string = %h server (Samba, Ubuntu) map to guest = Bad User
I have a linux box that I'm using to mount a windows 7 share with samba or cifs. The mounting itself goes fine, but directories with more subdirs or files do not seem to have all the content they actually have.
For example, viewing my music folder shows only first 37 subdirs. The ls says "total 49", which is the correct amount, but the listing itself shows only 37 first in alphapetical order.
On the other hand, my wallpaper folder contains 122 files. Ls claims there is 41872 and displays only 70.
Adding the mount option noserverino increases the listed files or dirs, but it still does not show them all.
I've tried to enable debug printk level, but dmesg doesn't show anything interesting.
I've tried to change values in /proc/fs/cifs, but it does not seem to have any effect.
I've tried changing samba package. So far I've tested with 3.5.7, 3.5.2, 3.5.4 and now 3.5.8.
My distribution was yesterday slackware 13.1. Today I upgraded to 13.37 (with samba 3.5.8) but the problem persists.
I've tried with kernel versions 2.6.35.12, 2.6.38.2 and 2.6.37.6.
cannot restrict share access to a single user. I've played with the security and valid users options in the smb.conf and I can get it to mount if I remove the valid users option, but this does not provide the access restriction I need. I also left it open and tried making the folder permissions rwx for backupadmin only and that didn't work. I'm using a credentials file which I include below, but I've tried manually entering them in the command too.
[root@aaphst02 /]# mount -t cifs //aapsan01/aapxen01 /mnt/aapxen01 --verbose -o credentials=/root/smbcreds mount.cifs kernel mount options: unc=//aapsan01aapxen01,ip=10.0.1.34,user=backupadmin,ver=1,rw,credentials=/root/smbcreds,pass=********
