I'm trying to get Samba functioning on my home network. It worked fine on Ubuntu - and I've saved the configuration file. Obviously I'm doing something wrong here, but I don't see it.
My smb.conf has the line WORKGROUP=SATTERWHITE
When I try to browse the network on my Windows box, I get the error message "Satterwhite is not accessible The associated network name is no longer available."
I can post / send anything else that you need to help me with the problem.
Does anyone know where I should start?
Thanks in advance. ---Michael
On Nov 29, 2006, at 12:47 PM, Michael Satterwhite wrote:
I'm trying to get Samba functioning on my home network. It worked fine on Ubuntu - and I've saved the configuration file. Obviously I'm doing something wrong here, but I don't see it.
My smb.conf has the line WORKGROUP=SATTERWHITE
When I try to browse the network on my Windows box, I get the error message "Satterwhite is not accessible The associated network name is no longer available."
I can post / send anything else that you need to help me with the problem.
Does anyone know where I should start?
Thanks in advance. ---Michael
http://www.funix.org/fr/linux/fichiers/DIAGNOSIS.txt
is where I start when I have problems with samba
Also there is a samba mailing list at
https://lists.samba.org/mailman/
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Michael Satterwhite wrote:
<... snip ...>
Does anyone know where I should start?
Thanks in advance. ---Michael
Michael,
Start first with trying to restart the service. `service smbd restart`
Any changes to the configuration file don't happen until a restart of the service.
- -James
James Kosin wrote:
Michael Satterwhite wrote:
<... snip ...>
Does anyone know where I should start?
Thanks in advance. ---Michael
Michael,
Start first with trying to restart the service. `service smbd restart`
Any changes to the configuration file don't happen until a restart of the service.
Good thought ... but I did that right after I made the changes. Thanks for the suggestion - because I remembered it this time doesn't mean I always will.
---Michael
On Wed, 2006-11-29 at 13:49 -0600, Michael Satterwhite wrote:
James Kosin wrote:
Michael Satterwhite wrote:
<... snip ...>
Does anyone know where I should start?
Thanks in advance. ---Michael
Michael,
Start first with trying to restart the service. `service smbd restart`
Any changes to the configuration file don't happen until a restart of the service.
Good thought ... but I did that right after I made the changes. Thanks for the suggestion - because I remembered it this time doesn't mean I always will.
---- actually samba re-reads the smb.conf approx once a minute for changes and will incorporate them automatically if possible so that is probably not all that important to remember.
Generally, when running a samba network on the same LAN segment, if both systems have ip addresses in the same class C network with the same subnet mask, the problem is going to be firewall related.
First make sure each system can ping each other's ip address to make sure that basic networking is good.
If networking is OK, then try to temporarily turn off firewall on Linux system...service iptables stop and then see if you can connect.
Craig
Michael Satterwhite wrote:
I'm trying to get Samba functioning on my home network. It worked fine on Ubuntu - and I've saved the configuration file. Obviously I'm doing something wrong here, but I don't see it.
My smb.conf has the line WORKGROUP=SATTERWHITE
When I try to browse the network on my Windows box, I get the error message "Satterwhite is not accessible The associated network name is no longer available."
I can post / send anything else that you need to help me with the problem.
While running the tests suggested by margaret, I ran nmblookup -B photon __SAMBA__
and got back querying __SAMBA__ on 192.168.1.20 name_query failed to find name __SAMBA__
The web page indicates an inetd problem - which I could have addressed. I see that Fedora is using xinetd, and I don't see any smb or nmb settings in the xinetd.d directory (I grepped for both). While this *MIGHT* be OK, I'm suspecting a problem here. Should there be entries for smb and nmb? If so, what should they be (and in what files?)
Thanks much ---Michael
On Wed, 2006-11-29 at 15:01 -0600, Michael Satterwhite wrote:
Michael Satterwhite wrote:
I'm trying to get Samba functioning on my home network. It worked fine on Ubuntu - and I've saved the configuration file. Obviously I'm doing something wrong here, but I don't see it.
My smb.conf has the line WORKGROUP=SATTERWHITE
When I try to browse the network on my Windows box, I get the error message "Satterwhite is not accessible The associated network name is no longer available."
I can post / send anything else that you need to help me with the problem.
While running the tests suggested by margaret, I ran nmblookup -B photon __SAMBA__
and got back querying __SAMBA__ on 192.168.1.20 name_query failed to find name __SAMBA__
The web page indicates an inetd problem - which I could have addressed. I see that Fedora is using xinetd, and I don't see any smb or nmb settings in the xinetd.d directory (I grepped for both). While this *MIGHT* be OK, I'm suspecting a problem here. Should there be entries for smb and nmb? If so, what should they be (and in what files?)
---- generally samba is responsible for it's own startup/shutdown and wouldn't make sense to use xinetd for samba.
make sure it's running...
service smb status
ps aux|grep smb ps aux|grep nmb
but check the firewall & networking issues that I just wrote about
Craig
Craig White wrote:
On Wed, 2006-11-29 at 15:01 -0600, Michael Satterwhite wrote:
Michael Satterwhite wrote:
I'm trying to get Samba functioning on my home network. It worked fine on Ubuntu - and I've saved the configuration file. Obviously I'm doing something wrong here, but I don't see it.
My smb.conf has the line WORKGROUP=SATTERWHITE
When I try to browse the network on my Windows box, I get the error message "Satterwhite is not accessible The associated network name is no longer available."
I can post / send anything else that you need to help me with the problem.
While running the tests suggested by margaret, I ran nmblookup -B photon __SAMBA__
and got back querying __SAMBA__ on 192.168.1.20 name_query failed to find name __SAMBA__
The web page indicates an inetd problem - which I could have addressed. I see that Fedora is using xinetd, and I don't see any smb or nmb settings in the xinetd.d directory (I grepped for both). While this *MIGHT* be OK, I'm suspecting a problem here. Should there be entries for smb and nmb? If so, what should they be (and in what files?)
generally samba is responsible for it's own startup/shutdown and wouldn't make sense to use xinetd for samba.
make sure it's running...
service smb status
It is (I'd done that, but I just redid it to make sure)
ps aux|grep smb ps aux|grep nmb
but check the firewall & networking issues that I just wrote about
both systems can ping the other. I've stopped iptables (I wouldn't have thought of that), The laptop still doesn't see the Samba machine. Knowing the eccentricities of Windows, I then tried restarting Samba and rebooting Win2K. It still doesn't see the Samba machine.
I've stopped iptables
On Wed, 2006-11-29 at 15:37 -0600, Michael Satterwhite wrote:
Craig White wrote:
On Wed, 2006-11-29 at 15:01 -0600, Michael Satterwhite wrote:
Michael Satterwhite wrote:
I'm trying to get Samba functioning on my home network. It worked fine on Ubuntu - and I've saved the configuration file. Obviously I'm doing something wrong here, but I don't see it.
My smb.conf has the line WORKGROUP=SATTERWHITE
When I try to browse the network on my Windows box, I get the error message "Satterwhite is not accessible The associated network name is no longer available."
I can post / send anything else that you need to help me with the problem.
While running the tests suggested by margaret, I ran nmblookup -B photon __SAMBA__
and got back querying __SAMBA__ on 192.168.1.20 name_query failed to find name __SAMBA__
The web page indicates an inetd problem - which I could have addressed. I see that Fedora is using xinetd, and I don't see any smb or nmb settings in the xinetd.d directory (I grepped for both). While this *MIGHT* be OK, I'm suspecting a problem here. Should there be entries for smb and nmb? If so, what should they be (and in what files?)
generally samba is responsible for it's own startup/shutdown and wouldn't make sense to use xinetd for samba.
make sure it's running...
service smb status
It is (I'd done that, but I just redid it to make sure)
ps aux|grep smb ps aux|grep nmb
but check the firewall & networking issues that I just wrote about
both systems can ping the other. I've stopped iptables (I wouldn't have thought of that), The laptop still doesn't see the Samba machine. Knowing the eccentricities of Windows, I then tried restarting Samba and rebooting Win2K. It still doesn't see the Samba machine.
I've stopped iptables
---- restarting can cause some issues with NETBIOS since WINS election/resolution can sometimes take as long as 15 minutes (that's by Microsoft design).
Try connecting from Windows system to Linux system via ip adress...
open Internet Explorer on Windows system and type '\192.168.1.1' (no quotes and change the ip address to whatever the ip address of the Linux system).
That should present you with a login challenge.
If not, then you probably have something in your 'smb.conf' like 'hosts allow =' that is preventing it from accepting the lan client.
Craig
Craig White wrote:
On Wed, 2006-11-29 at 15:37 -0600, Michael Satterwhite wrote:
Craig White wrote:
On Wed, 2006-11-29 at 15:01 -0600, Michael Satterwhite wrote:
Michael Satterwhite wrote:
I'm trying to get Samba functioning on my home network. It worked fine on Ubuntu - and I've saved the configuration file. Obviously I'm doing something wrong here, but I don't see it.
My smb.conf has the line WORKGROUP=SATTERWHITE
When I try to browse the network on my Windows box, I get the error message "Satterwhite is not accessible The associated network name is no longer available."
I can post / send anything else that you need to help me with the problem.
While running the tests suggested by margaret, I ran nmblookup -B photon __SAMBA__
and got back querying __SAMBA__ on 192.168.1.20 name_query failed to find name __SAMBA__
The web page indicates an inetd problem - which I could have addressed. I see that Fedora is using xinetd, and I don't see any smb or nmb settings in the xinetd.d directory (I grepped for both). While this *MIGHT* be OK, I'm suspecting a problem here. Should there be entries for smb and nmb? If so, what should they be (and in what files?)
generally samba is responsible for it's own startup/shutdown and wouldn't make sense to use xinetd for samba.
make sure it's running...
service smb status
It is (I'd done that, but I just redid it to make sure)
ps aux|grep smb ps aux|grep nmb
but check the firewall & networking issues that I just wrote about
both systems can ping the other. I've stopped iptables (I wouldn't have thought of that), The laptop still doesn't see the Samba machine. Knowing the eccentricities of Windows, I then tried restarting Samba and rebooting Win2K. It still doesn't see the Samba machine.
I've stopped iptables
restarting can cause some issues with NETBIOS since WINS election/resolution can sometimes take as long as 15 minutes (that's by Microsoft design).
Try connecting from Windows system to Linux system via ip adress...
open Internet Explorer on Windows system and type '\192.168.1.1' (no quotes and change the ip address to whatever the ip address of the Linux system).
That should present you with a login challenge.
Actually, it presents me with the Fedora Core Test Pge for Apache. Regardless, an http connection works.
On Wed, 2006-11-29 at 15:57 -0600, Michael Satterwhite wrote:
Craig White wrote:
On Wed, 2006-11-29 at 15:37 -0600, Michael Satterwhite wrote:
Craig White wrote:
On Wed, 2006-11-29 at 15:01 -0600, Michael Satterwhite wrote:
Michael Satterwhite wrote:
I'm trying to get Samba functioning on my home network. It worked fine on Ubuntu - and I've saved the configuration file. Obviously I'm doing something wrong here, but I don't see it.
My smb.conf has the line WORKGROUP=SATTERWHITE
When I try to browse the network on my Windows box, I get the error message "Satterwhite is not accessible The associated network name is no longer available."
I can post / send anything else that you need to help me with the problem.
While running the tests suggested by margaret, I ran nmblookup -B photon __SAMBA__
and got back querying __SAMBA__ on 192.168.1.20 name_query failed to find name __SAMBA__
The web page indicates an inetd problem - which I could have addressed. I see that Fedora is using xinetd, and I don't see any smb or nmb settings in the xinetd.d directory (I grepped for both). While this *MIGHT* be OK, I'm suspecting a problem here. Should there be entries for smb and nmb? If so, what should they be (and in what files?)
generally samba is responsible for it's own startup/shutdown and wouldn't make sense to use xinetd for samba.
make sure it's running...
service smb status
It is (I'd done that, but I just redid it to make sure)
ps aux|grep smb ps aux|grep nmb
but check the firewall & networking issues that I just wrote about
both systems can ping the other. I've stopped iptables (I wouldn't have thought of that), The laptop still doesn't see the Samba machine. Knowing the eccentricities of Windows, I then tried restarting Samba and rebooting Win2K. It still doesn't see the Samba machine.
I've stopped iptables
restarting can cause some issues with NETBIOS since WINS election/resolution can sometimes take as long as 15 minutes (that's by Microsoft design).
Try connecting from Windows system to Linux system via ip adress...
open Internet Explorer on Windows system and type '\192.168.1.1' (no quotes and change the ip address to whatever the ip address of the Linux system).
That should present you with a login challenge.
Actually, it presents me with the Fedora Core Test Pge for Apache. Regardless, an http connection works.
----- that's a web connection...
\ip_address should provide a network connection - not an http connection. Perhaps I misspoke with Internet Explorer. Try doing this in 'My Computer' instead of Internet Explorer though it shouldn't mater.
Craig
Craig White wrote:
that's a web connection...
Right. IE adds http: to a raw address
\ip_address should provide a network connection - not an http connection. Perhaps I misspoke with Internet Explorer. Try doing this in 'My Computer' instead of Internet Explorer though it shouldn't mater.
That got somewhere. When I entered 192.168.1.20 into the My Computer address bar, it got a failure to connect. 192.168.1.100 (the laptop address) did show it's file system.
It looks like it's getting closer, but I can't for the life of me see what's wrong. The hosts parameters in smb.conf read hosts allow =127. 192.168.
Which is a direct paraphrase from the man smb.conf page.
---Michael
On Wed, 2006-11-29 at 18:42 -0600, Michael Satterwhite wrote:
Craig White wrote:
that's a web connection...
Right. IE adds http: to a raw address
\ip_address should provide a network connection - not an http connection. Perhaps I misspoke with Internet Explorer. Try doing this in 'My Computer' instead of Internet Explorer though it shouldn't mater.
That got somewhere. When I entered 192.168.1.20 into the My Computer address bar, it got a failure to connect. 192.168.1.100 (the laptop address) did show it's file system.
It looks like it's getting closer, but I can't for the life of me see what's wrong. The hosts parameters in smb.conf read hosts allow =127. 192.168.
Which is a direct paraphrase from the man smb.conf page.
---- failure to connect? - i.e. it was a logon failure or did it never ask for your login/password?
Look at your log files too. /var/log/samba - there might be a file like log.192.168.1.100 with some extra information.
Also /var/log/samba/log.smbd & log.nmbd
Craig
On Wed, 2006-11-29 at 18:42 -0600, Michael Satterwhite wrote:
Craig White wrote:
that's a web connection...
Right. IE adds http: to a raw address
\ip_address should provide a network connection - not an http connection. Perhaps I misspoke with Internet Explorer. Try doing this in 'My Computer' instead of Internet Explorer though it shouldn't mater.
That got somewhere. When I entered 192.168.1.20 into the My Computer address bar, it got a failure to connect. 192.168.1.100 (the laptop address) did show it's file system.
It looks like it's getting closer, but I can't for the life of me see what's wrong. The hosts parameters in smb.conf read hosts allow =127. 192.168.
Which is a direct paraphrase from the man smb.conf page.
---- OK had another idea of something to try...
from linux system
smbclient -L YOUR_IP_ADDRESS_or_NETBIOS_NAME
press enter when it asks for a password...does it connect? does it show shares?
Craig
Michael Satterwhite wrote:
I'm trying to get Samba functioning on my home network. It worked fine on Ubuntu - and I've saved the configuration file. Obviously I'm doing something wrong here, but I don't see it.
My smb.conf has the line WORKGROUP=SATTERWHITE
You may want to run "testparm /etc/samba/smb.conf"
Dumb idea - change "WORKGROUP=SATTERWHITE" to "workgroup = SATTERWHITE". It may not matter, but every example I have seen of Samba configurations has a space on each side of the = sign. I have run into cases before where missing spaces have caused problems in config files.
Mikkel
Mikkel L. Ellertson wrote:
Michael Satterwhite wrote:
I'm trying to get Samba functioning on my home network. It worked fine on Ubuntu - and I've saved the configuration file. Obviously I'm doing something wrong here, but I don't see it.
My smb.conf has the line WORKGROUP=SATTERWHITE
You may want to run "testparm /etc/samba/smb.conf"
Dumb idea - change "WORKGROUP=SATTERWHITE" to "workgroup = SATTERWHITE". It may not matter, but every example I have seen of Samba configurations has a space on each side of the = sign. I have run into cases before where missing spaces have caused problems in config files.
From where I'm sitting, there are no dumb ideas (well, maybe typing while standing on my head - but no one has gone that far)
Didn't work, but I tried it. Thanks for the idea. ---Michael
On Thursday 30 November 2006 00:14, Michael Satterwhite wrote:
Mikkel L. Ellertson wrote:
Michael Satterwhite wrote:
I'm trying to get Samba functioning on my home network. It worked fine on Ubuntu - and I've saved the configuration file. Obviously I'm doing something wrong here, but I don't see it.
My smb.conf has the line WORKGROUP=SATTERWHITE
You may want to run "testparm /etc/samba/smb.conf"
Dumb idea - change "WORKGROUP=SATTERWHITE" to "workgroup = SATTERWHITE". It may not matter, but every example I have seen of Samba configurations has a space on each side of the = sign. I have run into cases before where missing spaces have caused problems in config files.
From where I'm sitting, there are no dumb ideas (well, maybe typing while standing on my head - but no one has gone that far)
Didn't work, but I tried it. Thanks for the idea. ---Michael
I agree with Mikkel about spaces. Some applications are fussier than others - some want spaces, some don't, but samba uses them by default, so I'd keep them there.
Just one more suggestion to try. Have you got 'security = user' or 'security = share' in your global section? Try the other one. If it makes any difference it would give a pointer to the problem.
Anne
OK, I'm not sure what change did it, but I can connect to *SOME* of my shares. I have one more that I can't seem to connect to. The definition in smb.conf is
[windows] case sensitive = no msdfs proxy = no read only = no comment = windows directory path = /windows
This is the vfat partition holding my windows setup. The fstab entry makes the partition readable / writable by anyone. When I try to attach this partition, I get a "The Network Name Cannot be found."
Obviously, the windows box knows about the name as it displays it for me to select - and the setup looks right to me. What am I missing?
Thanks again ---Michael
On Thu, 2006-11-30 at 09:45 -0600, Michael Satterwhite wrote:
OK, I'm not sure what change did it, but I can connect to *SOME* of my shares. I have one more that I can't seem to connect to. The definition in smb.conf is
[windows] case sensitive = no msdfs proxy = no read only = no comment = windows directory path = /windows
This is the vfat partition holding my windows setup. The fstab entry makes the partition readable / writable by anyone. When I try to attach this partition, I get a "The Network Name Cannot be found."
Obviously, the windows box knows about the name as it displays it for me to select - and the setup looks right to me. What am I missing?
---- possibly selinux block - is selinux active?
is the share visible if you try from the linux client...
smbclient -L NETBIOS_NAME
does executing...
testparm -s
reveal any errors?
Craig
Craig White wrote:
On Thu, 2006-11-30 at 09:45 -0600, Michael Satterwhite wrote:
OK, I'm not sure what change did it, but I can connect to *SOME* of my shares. I have one more that I can't seem to connect to. The definition in smb.conf is
[windows] case sensitive = no msdfs proxy = no read only = no comment = windows directory path = /windows
This is the vfat partition holding my windows setup. The fstab entry makes the partition readable / writable by anyone. When I try to attach this partition, I get a "The Network Name Cannot be found."
Obviously, the windows box knows about the name as it displays it for me to select - and the setup looks right to me. What am I missing?
possibly selinux block - is selinux active?
No. I'd read enough on the list not to trust it, so I disabled it during install.
is the share visible if you try from the linux client...
smbclient -L NETBIOS_NAME
Yes, I can see it in that display - remember that it's visible on the windows machine, too ... I just can't attach it.
does executing...
testparm -s
reveal any errors?
No errors.
...at least I haven't done anything *OBVIOUS* <g> Part of me hates it when that happens - another part likes it cause it leads to a quick solution.
Today Michael Satterwhite did spake thusly:
Craig White wrote:
On Thu, 2006-11-30 at 09:45 -0600, Michael Satterwhite wrote:
OK, I'm not sure what change did it, but I can connect to *SOME* of my shares. I have one more that I can't seem to connect to. The definition in smb.conf is
[windows] case sensitive = no msdfs proxy = no read only = no comment = windows directory path = /windows
This is the vfat partition holding my windows setup. The fstab entry makes the partition readable / writable by anyone. When I try to attach this partition, I get a "The Network Name Cannot be found."
Obviously, the windows box knows about the name as it displays it for me to select - and the setup looks right to me. What am I missing?
possibly selinux block - is selinux active?
No. I'd read enough on the list not to trust it, so I disabled it during install.
is the share visible if you try from the linux client...
smbclient -L NETBIOS_NAME
Yes, I can see it in that display - remember that it's visible on the windows machine, too ... I just can't attach it.
does executing...
testparm -s
reveal any errors?
No errors.
...at least I haven't done anything *OBVIOUS* <g> Part of me hates it when that happens - another part likes it cause it leads to a quick solution.
There's a bug which might still be open where if a directory has too many files in it it'll not work when you try and mount it under linux - or are you trying to mount it under windows?
Scott van Looy wrote:
Today Michael Satterwhite did spake thusly:
Craig White wrote:
On Thu, 2006-11-30 at 09:45 -0600, Michael Satterwhite wrote:
OK, I'm not sure what change did it, but I can connect to *SOME* of my shares. I have one more that I can't seem to connect to. The definition in smb.conf is
[windows] case sensitive = no msdfs proxy = no read only = no comment = windows directory path = /windowsThis is the vfat partition holding my windows setup. The fstab entry makes the partition readable / writable by anyone. When I try to attach this partition, I get a "The Network Name Cannot be found."
Obviously, the windows box knows about the name as it displays it for me to select - and the setup looks right to me. What am I missing?
possibly selinux block - is selinux active?
No. I'd read enough on the list not to trust it, so I disabled it during install.
is the share visible if you try from the linux client...
smbclient -L NETBIOS_NAME
Yes, I can see it in that display - remember that it's visible on the windows machine, too ... I just can't attach it.
does executing...
testparm -s
reveal any errors?
No errors.
...at least I haven't done anything *OBVIOUS* <g> Part of me hates it when that happens - another part likes it cause it leads to a quick solution.
There's a bug which might still be open where if a directory has too many files in it it'll not work when you try and mount it under linux - or are you trying to mount it under windows?
I have it mounted under linux. I'm trying to access it under windows through Samba.
On Thu, 2006-11-30 at 11:37 -0600, Michael Satterwhite wrote:
Craig White wrote:
On Thu, 2006-11-30 at 09:45 -0600, Michael Satterwhite wrote:
OK, I'm not sure what change did it, but I can connect to *SOME* of my shares. I have one more that I can't seem to connect to. The definition in smb.conf is
[windows] case sensitive = no msdfs proxy = no read only = no comment = windows directory path = /windows
This is the vfat partition holding my windows setup. The fstab entry makes the partition readable / writable by anyone. When I try to attach this partition, I get a "The Network Name Cannot be found."
Obviously, the windows box knows about the name as it displays it for me to select - and the setup looks right to me. What am I missing?
possibly selinux block - is selinux active?
No. I'd read enough on the list not to trust it, so I disabled it during install.
is the share visible if you try from the linux client...
smbclient -L NETBIOS_NAME
Yes, I can see it in that display - remember that it's visible on the windows machine, too ... I just can't attach it.
does executing...
testparm -s
reveal any errors?
No errors.
...at least I haven't done anything *OBVIOUS* <g> Part of me hates it when that happens - another part likes it cause it leads to a quick solution.
---- one would think that the error should be logged in /var/log/messages then.
From a command line on Linux (without Windows or samba), can you
access /windows as root? as a user? do files show up when you do things like 'ls' or 'ls -l' ?
does it show up as mounted?
command to show active mounts....
'mount'
Craig
Craig White wrote:
On Thu, 2006-11-30 at 11:37 -0600, Michael Satterwhite wrote:
Craig White wrote:
On Thu, 2006-11-30 at 09:45 -0600, Michael Satterwhite wrote:
OK, I'm not sure what change did it, but I can connect to *SOME* of my shares. I have one more that I can't seem to connect to. The definition in smb.conf is
[windows] case sensitive = no msdfs proxy = no read only = no comment = windows directory path = /windows
This is the vfat partition holding my windows setup. The fstab entry makes the partition readable / writable by anyone. When I try to attach this partition, I get a "The Network Name Cannot be found."
Obviously, the windows box knows about the name as it displays it for me to select - and the setup looks right to me. What am I missing?
possibly selinux block - is selinux active?
No. I'd read enough on the list not to trust it, so I disabled it during install.
is the share visible if you try from the linux client...
smbclient -L NETBIOS_NAME
Yes, I can see it in that display - remember that it's visible on the windows machine, too ... I just can't attach it.
does executing...
testparm -s
reveal any errors?
No errors.
...at least I haven't done anything *OBVIOUS* <g> Part of me hates it when that happens - another part likes it cause it leads to a quick solution.
one would think that the error should be logged in /var/log/messages then.
From a command line on Linux (without Windows or samba), can you
access /windows as root? as a user? do files show up when you do things like 'ls' or 'ls -l' ?
does it show up as mounted?
command to show active mounts....
'mount'
From the linux machine, I can do anything I want with /windows as user
or root. Read - write, browse, whatever. I wasn't surprised to see it listed when I ran mount - it's there.
On Thu, 2006-11-30 at 12:00 -0600, Michael Satterwhite wrote:
Craig White wrote:
On Thu, 2006-11-30 at 11:37 -0600, Michael Satterwhite wrote:
Craig White wrote:
On Thu, 2006-11-30 at 09:45 -0600, Michael Satterwhite wrote:
OK, I'm not sure what change did it, but I can connect to *SOME* of my shares. I have one more that I can't seem to connect to. The definition in smb.conf is
[windows] case sensitive = no msdfs proxy = no read only = no comment = windows directory path = /windows
This is the vfat partition holding my windows setup. The fstab entry makes the partition readable / writable by anyone. When I try to attach this partition, I get a "The Network Name Cannot be found."
Obviously, the windows box knows about the name as it displays it for me to select - and the setup looks right to me. What am I missing?
possibly selinux block - is selinux active?
No. I'd read enough on the list not to trust it, so I disabled it during install.
is the share visible if you try from the linux client...
smbclient -L NETBIOS_NAME
Yes, I can see it in that display - remember that it's visible on the windows machine, too ... I just can't attach it.
does executing...
testparm -s
reveal any errors?
No errors.
...at least I haven't done anything *OBVIOUS* <g> Part of me hates it when that happens - another part likes it cause it leads to a quick solution.
one would think that the error should be logged in /var/log/messages then.
From a command line on Linux (without Windows or samba), can you
access /windows as root? as a user? do files show up when you do things like 'ls' or 'ls -l' ?
does it show up as mounted?
command to show active mounts....
'mount'
From the linux machine, I can do anything I want with /windows as user
or root. Read - write, browse, whatever. I wasn't surprised to see it listed when I ran mount - it's there.
---- then the only thing that I can think of is that a Windows FAT partition mounts as a particular user and if you are trying to share it with 'samba' - the issue is that there might be a conflict between the user trying to use it and and the 'local' user who has the mount.
bear in mind that POSIX attributes are not available on a FAT volume mount and I have to wonder if something isn't being logged somewhere, either in /var/log/messages or /var/log/samba/smbd.log or /var/log/samba/log.smbd that provides a clue.
I can't say that I've ever tried to share a VFAT or NTFS volume via samba before and I don't know the consequences of that.
Craig
then the only thing that I can think of is that a Windows FAT partition mounts as a particular user and if you are trying to share it with 'samba' - the issue is that there might be a conflict between the user trying to use it and and the 'local' user who has the mount.
bear in mind that POSIX attributes are not available on a FAT volume mount and I have to wonder if something isn't being logged somewhere, either in /var/log/messages or /var/log/samba/smbd.log or /var/log/samba/log.smbd that provides a clue.
I can't say that I've ever tried to share a VFAT or NTFS volume via samba before and I don't know the consequences of that.
Actually, it got a little curiouser (to borrow from Lewis Carrol). To get a required task to run, I created a symlink from the ext3 partition that I'm having no problem connecting to to the windows partition. Going through that symlink, I have no problem accessing the files in the vfat partition. I believe this pretty much rules out a permissions problem in the Linux setup. There could be a permissions issue in the *SAMBA* setup, but Linux doesn't have any problem with that remote user using the files in vfat.
On Fri, 2006-12-01 at 07:47 -0600, Michael Satterwhite wrote:
then the only thing that I can think of is that a Windows FAT partition mounts as a particular user and if you are trying to share it with 'samba' - the issue is that there might be a conflict between the user trying to use it and and the 'local' user who has the mount.
bear in mind that POSIX attributes are not available on a FAT volume mount and I have to wonder if something isn't being logged somewhere, either in /var/log/messages or /var/log/samba/smbd.log or /var/log/samba/log.smbd that provides a clue.
I can't say that I've ever tried to share a VFAT or NTFS volume via samba before and I don't know the consequences of that.
Actually, it got a little curiouser (to borrow from Lewis Carrol). To get a required task to run, I created a symlink from the ext3 partition that I'm having no problem connecting to to the windows partition. Going through that symlink, I have no problem accessing the files in the vfat partition. I believe this pretty much rules out a permissions problem in the Linux setup. There could be a permissions issue in the *SAMBA* setup, but Linux doesn't have any problem with that remote user using the files in vfat.
---- your description is a bit too vague to comment
you could always try a bind mount...i.e.
mkdir /home/windows chmod 777 /home/windows mount --bind /windows /home/windows
Craig
-
Anne Wilson -
Craig White -
Craig White -
James Kosin -
Margaret Doll -
Michael Satterwhite -
Mikkel -
Scott van Looy