For whatever reason my samba install only has issues with me attempting to access files on a windows box, copying or moving from it are never allowed from the linux box. But the opposite works just fine, I can copy files across the network to the linux box, and the printer share from the linux box works flawlessly.
Is this just a matter of me needing to somehow enable the OS to access an NTFS file system?
hi
not sure i quite follow you…would you answer the following questions regarding each machine?
From the Windows Machine:
Can see the samba share located on linux box
Can copy files to/from samba share to windows machine
can create or delete files on samba share
From Linux box:
Can see the share located on Windows machine
can can copy files to from windows machine to linux
can create or delete files on windows machine
do you have the windows share mounted somewhere on your linux file system?
If everything from the samba side looks good (all the questions under section “FROM WINDOWS MACHINE” answered yes) then i would say its a permissions issue on your WINDOWS computer. check the folder itself in windows to make sure it is not read only. Also check the share settings on the windows machine and look for a checkbox labeled “allow other users to change my files” or something to that effect…
I can see samba shares.
I can copy, create, move and delete files to/from the samba shares to the windows machines.
From the linux box:
I can see windows shares
I can copy, create, move and delete files to/from windows shares … which is odd as last night I was getting permission denials when attemptig to copy to a windows share, and I have not editied my settings at all on either box.
Would the size of a file transfer, or the fact that I was attempting to copy something with multiple files and subfolders have caused a hiccup in samba?
As for the mounting question… what would the best way to auto-mount windows shares on the linux machine be? The linux machine will be powered on 24/7 … however windows machines will be powered on and off periodically through the day… would a line in /etc/fstab detect and mount them only if the windows machines are powered up when the linux machine starts?
which is odd as last night I was getting permission denials when attemptig to copy to a windows share, and I have not editied my settings at all on either box.
its windows…who knows?
Would the size of a file transfer, or the fact that I was attempting to copy something with multiple files and subfolders have caused a hiccup in samba?
Not sure, I am by no means a Samba expert (however im sure there are many in these forums!)
As for the mounting question… what would the best way to auto-mount windows shares on the linux machine be? The linux machine will be powered on 24/7 … however windows machines will be powered on and off periodically through the day… would a line in /etc/fstab detect and mount them only if the windows machines are powered up when the linux machine starts?
That is correct, if you add the line to /etc/fstab and then power up your linux box with your windows machine off, you will get an error.
I would do a search for an automounter (never used one myself). Maybe you could write a script to do it? something that pings the windows server from time to time and if it gets a good ping then tries to mount your share?
I’ve been stuck for 2 days with this issue. Finally it turns out that my linux firewall config has blocked the processes. I choosed to turn off the firewall and everything works fine, I can print, browse and share from openSUSE to Windows XP over a Wireless router. Yast2 > Security > firewall > Stop firewall > finish !
I seem to recall a similar problem I had a while back (Once I got Samba working, i havent messed with it since…and that was a while ago!)
since you have your machine behind a NAT router…you can try adding your network interface to the “internal zone” and turning your firewall back on for added security…
>
>> which is odd as last night I was getting permission denials when
>> attemptig to copy to a windows share, and I have not editied my settings
>> at all on either box.
>
> its windows…who knows?
>
>> Would the size of a file transfer, or the fact that I was attempting to
>> copy something with multiple files and subfolders have caused a hiccup
>> in samba?
>
> Not sure, I am by no means a Samba expert (however im sure there are
> many in these forums!)
>
>> As for the mounting question… what would the best way to auto-mount
>> windows shares on the linux machine be? The linux machine will be
>> powered on 24/7 … however windows machines will be powered on and off
>> periodically through the day… would a line in /etc/fstab detect and
>> mount them only if the windows machines are powered up when the linux
>> machine starts?
> That is correct, if you add the line to /etc/fstab and then power up
> your linux box with your windows machine off, you will get an error.
>
>
>
> I would do a search for an automounter (never used one myself). Maybe
> you could write a script to do it? something that pings the windows
> server from time to time and if it gets a good ping then tries to mount
> your share?
>
>
orcsoul;
Have you read the HowTos located here: http://www.swerdna.net.au/linux.html
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
Hmm would something like this work out? Reason I ask is i’m not familiar with python at all and I’m not sure if there’s anything ubuntu specific in that scripting or if it’s generic enough to use with suse as is.
Python is an interpreted language and is cross platform for the most part. I do not see any reason it wouldnt work on SuSE. (and if it does not work, i do not see it harming your system)
you need to have the python interpreter installed, invoke the following command from the terminal as root
zypper install python
then you can perform the steps as listed in the link you posted.
Ok great, would putting that line in /etc/init.d/boot.local make sure it’s run after network interfaces are brought up? Or do one of the other files run after the interfaces are brought up?
unfortunately, no. /etc/init.d/boot.local is run before the network is started. you will have to create a custom init script to have this run at boot time. take a look at the following url for more info on creating a script.
Im not sure if you can embed the python code in the init script, but you can save the python script somewhere on your system and call it from the init script.
Okies… just typing my thought process out here to make sure I’ve got the right idea…
Make a custom script in /etc/init.d … call it automount for the sake of simplicity…
following the skeleton template there i’d make sure its default start is level 5 at the least, and specify that it’s required start is $network … and then at some point in the automount script, refer it to the perl script, and things should be a-ok?