| View previous topic :: View next topic |
| Author |
Message |
darkphader
Veteran
Joined: 09 May 2002
Posts: 1225
Location: Motown
|
 Posted: Fri Apr 08, 2005 4:41 pm Post subject: |
 |
|
Do you have an "include = " line in your smb.conf that shouldn't be there (or should ordinarily be commented out as in the example file)? Hard to see why you would get the particular testparm error otherwise (other than my first guess).
_________________
WYSIWYG - What You See Is What You Grep |
|
| Back to top |
|
 |
darkphader
Veteran
Joined: 09 May 2002
Posts: 1225
Location: Motown
|
| Posted: Fri Apr 08, 2005 4:52 pm Post subject: |
|
|
Instead of | Code: | | mount -t smbfs //your-vp7x3s9ctm/temp /mnt/winxp |
try | Code: | | mount -t smbfs -o username=ValidUserNameOnRemoteSystem //your-vp7x3s9ctm/temp /mnt/winxp |
and supply the proper password if requested (properly replacing ValidUserNameOnRemoteSystem with an actual valid logon name that has permissions to use the share).
Make sure that "//your-vp7x3s9ctm/temp" is of the format //SystemName/ShareName, IOW that "temp" is a share name and not just a directory name.
PS. check the permissions on /mnt/winxp
_________________
WYSIWYG - What You See Is What You Grep |
|
| Back to top |
|
|
ONEEYEMAN
Advocate
Joined: 01 Mar 2005
Posts: 3674
|
| Posted: Fri Apr 08, 2005 5:40 pm Post subject: |
|
|
Thank you for the reply, darkfader.
| Code: |
bash-2.05b# cat smb.conf
[global]
workgroup = MSHOME
netbios name = gentoo
log file = /var/log/samba3/log.%m
max log size = 50
log level = 3
hosts allow = 127.0.0.1 192.168.1.
hosts deny = 0.0.0.0
security = share
guest account = samba
guest ok = yes
include =/etc/samba/smb.conf.%m
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
server string = Samba Server %v
interfaces = lo eth0
bind interfaces only = yes
vfs object = vscan-clamav
vscan-clamav: config-file = /etc/samba/vscan-clamav.conf
[public]
comment = Public Staff
browseable = yes
public = yes
create mode = 0766
guest ok = yes
path = /home/samba/public
|
This is a Samba configuration file. There is an include line just like in an example file in the [global] sub-group.
| Code: |
bash-2.05b# mount -t smbfs -o Owner //your-vp7x3s9ctm/temp /mnt/winxp
Can't find include file /etc/samba/smb.conf.
opts: rw
opts: Owner
passthrough options 'Owner'
mount.smbfs started (version 3.0.10)
added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0
added interface ip=192.168.1.142 bcast=192.168.1.255 nmask=255.255.255.0
resolve_lmhosts: Attempting lmhosts lookup for name your-vp7x3s9ctm<0x20>
resolve_wins: Attempting wins lookup for name your-vp7x3s9ctm<0x20>
resolve_wins: WINS server resolution selected and no WINS servers listed.
resolve_hosts: Attempting host lookup for name your-vp7x3s9ctm<0x20>
Connecting to 192.168.1.133 at port 445
timeout connecting to 192.168.1.133:445
Connecting to 192.168.1.133 at port 139
timeout connecting to 192.168.1.133:139
Error connecting to 192.168.1.133 (Operation already in progress)
6711: Connection to your-vp7x3s9ctm failed
SMB connection failed
bash-2.05b# ping -c 3 192.168.1.133
PING 192.168.1.133 (192.168.1.133) 56(84) bytes of data.
64 bytes from 192.168.1.133: icmp_seq=1 ttl=128 time=0.678 ms
64 bytes from 192.168.1.133: icmp_seq=2 ttl=128 time=0.494 ms
64 bytes from 192.168.1.133: icmp_seq=3 ttl=128 time=0.489 ms
--- 192.168.1.133 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 0.489/0.553/0.678/0.092 ms
|
As you could see I could ping the XP, but I couldn't connect with the Samba.... 
Thank you. |
|
| Back to top |
|
|
darkphader
Veteran
Joined: 09 May 2002
Posts: 1225
Location: Motown
|
| Posted: Fri Apr 08, 2005 5:54 pm Post subject: |
|
|
Remove the include line, it is causing the testparm error.
Again note: you are not using Samba (at least on your local system) when doing "mount -t smbfs". You can stop the Samba services/daemons altogether unless you need WINS resolution etc. Please see my previous clarification post.
As for your ping, note that you are pinging the IP address (192.168.1.133) and not the netbios name. Make sure that you have name resolution, ie: you are trying to connect to "your-vp7x3s9ctm" so you should be able to ping it. Make an entry in your hosts file if needed or connect to the IP address and not the system name.
_________________
WYSIWYG - What You See Is What You Grep |
|
| Back to top |
|
|
darkphader
Veteran
Joined: 09 May 2002
Posts: 1225
Location: Motown
|
| Posted: Fri Apr 08, 2005 7:59 pm Post subject: |
|
|
Another thought: check any firewall settings. Turn off any firewalling on both the boxes to verify they aren't causing the problem.
_________________
WYSIWYG - What You See Is What You Grep |
|
| Back to top |
|
|
ONEEYEMAN
Advocate
Joined: 01 Mar 2005
Posts: 3674
|
| Posted: Fri Apr 08, 2005 8:55 pm Post subject: |
|
|
Thank you for the fast reply.
I commented out the include line, and the testparm error is gone. But what is the include line doing? Why they put it in the "smb.conf.example" file?
Now, in regards to the mount error.
If you look closely you will see that the I pinged IP address, that the mount tried to mount to. Which means that the IP adress/name is resolving correctly. But my guess is that the mount and the ping are using different port. Also, when I use "Ipconfig" on my XP box, I receive the IP address correctly, i.e. the address that mount tried to connect to. So, that is my guess. Also what do you mean by "netbios name"?
Thank you. |
|
| Back to top |
|
|
ONEEYEMAN
Advocate
Joined: 01 Mar 2005
Posts: 3674
|
| Posted: Fri Apr 08, 2005 8:57 pm Post subject: |
|
|
OK, is it just for the testing purposes? Because I don't want to remove firewall on my XP machine.... 
Thank you. |
|
| Back to top |
|
|
darkphader
Veteran
Joined: 09 May 2002
Posts: 1225
Location: Motown
|
| Posted: Fri Apr 08, 2005 9:23 pm Post subject: |
|
|
| Code: | resolve_hosts: Attempting host lookup for name your-vp7x3s9ctm<0x20>
Connecting to 192.168.1.133 at port 445
timeout connecting to 192.168.1.133:445
Connecting to 192.168.1.133 at port 139
timeout connecting to 192.168.1.133:139 |
OK. I see the above. It does look like the name resolves eventually. But you should make an entry in your /etc/hosts file so that it resolves sooner and doesn't depend on broadcasts (which is my guess currently).
I did notice that you pinged the IP address but you should also be able to ping the netbios name (the name of your XP system - "ping your-vp7x3s9ctm") since that is what you are trying to connect to. If you fix up your hosts file it will all work better.
As to the XP firewall it is probably the problem as you see from above that attempts to connect to the ports 445 and 139 timeout. First turn it off to verify it is the culprit and then adjust it's settings so that it allows for smb connections from your local subnet.
_________________
WYSIWYG - What You See Is What You Grep |
|
| Back to top |
|
|
ONEEYEMAN
Advocate
Joined: 01 Mar 2005
Posts: 3674
|
| Posted: Fri Apr 08, 2005 10:17 pm Post subject: |
|
|
Thank you for the reply.
The /etc/hosts consists the info about my local gentoo box and XP box. I put them at the time of install.
Also, I was able to ping the XP machine name and not the IP adress. I have in there:
1. localhost.
2. gentoo machine
3. XP machine
I don't know if I have to keep the localhost line in there, but the IP addresses are in.
As for the XP firewall, I will try to connect with it disabled and let you know, what happened.
Thank you. |
|
| Back to top |
|
|
ONEEYEMAN
Advocate
Joined: 01 Mar 2005
Posts: 3674
|
| Posted: Fri Apr 08, 2005 10:21 pm Post subject: |
|
|
Yeah, it is Symantec firewall. Now all I need is to change it's settings accordingly, so it allow connection through the samba ports.
Thank you very much, all. |
|
| Back to top |
|
|
ONEEYEMAN
Advocate
Joined: 01 Mar 2005
Posts: 3674
|
| Posted: Fri Apr 08, 2005 11:18 pm Post subject: |
|
|
Ok, looks like I don't have a winner just yet!!
I reconfigured the Firewall to gain access to the XP, but when I tried to mount the share I got following:
| Code: |
bash-2.05b# mount -t smbfs -o Owner //your-vp7x3s9ctm/temp /mnt/winxp
opts: rw
opts: Owner
passthrough options 'Owner'
mount.smbfs started (version 3.0.10)
added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0
added interface ip=192.168.1.142 bcast=192.168.1.255 nmask=255.255.255.0
resolve_lmhosts: Attempting lmhosts lookup for name your-vp7x3s9ctm<0x20>
resolve_wins: Attempting wins lookup for name your-vp7x3s9ctm<0x20>
resolve_wins: WINS server resolution selected and no WINS servers listed.
resolve_hosts: Attempting host lookup for name your-vp7x3s9ctm<0x20>
Connecting to 192.168.1.133 at port 445
Password:
ERROR: smbfs filesystem not supported by the kernel
Please refer to the smbmnt(8) manual page
smbmnt failed: 255
|
Who does not support smbfs? Linux Gentoo kernel compiled with the Gentoo support.....
Thank you |
|
| Back to top |
|
|
darkphader
Veteran
Joined: 09 May 2002
Posts: 1225
Location: Motown
|
| Posted: Fri Apr 08, 2005 11:40 pm Post subject: |
|
|
When you configure the kernel you need to select the network file systems you want to use (remember you are not using Samba here). Compile in or as modules:
| Code: | File systems ---> Network File Systems ---> SMB file system support
and
File systems ---> Network File Systems ---> CIFS support |
You may have to load the modules if you didn't select kernel module autoloading.
Actually I would highly recommend the switch right over to CIFS instead of SMBFS. If you use the essentially deprecated SMBFS you will encounter many problems with files and directories over 2GB.
Just use "mount -t cifs" instead of "mount -t smbfs" in the future.
_________________
WYSIWYG - What You See Is What You Grep |
|
| Back to top |
|
|
ONEEYEMAN
Advocate
Joined: 01 Mar 2005
Posts: 3674
|
| Posted: Sat Apr 09, 2005 12:38 am Post subject: |
|
|
Thank you for the reply, darkphader.
As a matter of fact, I do have a SMB file system support compiled in the kernel. But I didn't know that it requires CIFS...
Is this required to support Samba file system? If not I would think about compiling it as a module. Maybe my particular kernel branch doesn't support in-compilation with the re-compilation.....
Thank you. |
|
| Back to top |
|
|
darkphader
Veteran
Joined: 09 May 2002
Posts: 1225
Location: Motown
|
| Posted: Sat Apr 09, 2005 4:30 am Post subject: |
|
|
| ONEEYEMAN wrote: | I do have a SMB file system support compiled in the kernel. But I didn't know that it requires CIFS...
Is this required to support Samba file system? |
CIFS is, in essence, another name for SMBFS but the modules are different; neither depends on the other, nor is there such a thing as the "Samba file system". I suggest using the CIFS code over the SMBFS code when connecting to an SMB share for already clearly stated reasons; it is, however, your choice.
As for Samba, even though in some ways it acts as a client, think of it generally as a server; a server that allow your Linux system to share it's files/printers with Windows systems in a way they understand. You use Samba to expose your Linux files and printers as 'Windows' shares (and possibly much more - your Linux system could act as a Windows server PDC), but you use cifs or smbfs to connect to your Windows system's shares.
AFAIK, it shouldn't matter whether or not the smbfs/cifs support is in-kernel or modules. I have both compiled as modules and both work. Although CIFS works much better due to the SMBFS limitations. As an example I have a large remote directory of mp3's on a Windows 2000 Server share where smbfs cannot show all of the files but cifs does. Also trying to move/copy a file large than 2GB will fail with smbfs but not with cifs. Guess which one I use.
I suggest you test with your firewall off, if it works until you turn your firewall on then your firewall settings need to be modified.
_________________
WYSIWYG - What You See Is What You Grep |
|
| Back to top |
|
|
ONEEYEMAN
Advocate
Joined: 01 Mar 2005
Posts: 3674
|
| Posted: Sat Apr 09, 2005 4:50 am Post subject: |
|
|
Ok, if I disable my firewall I get the same results. Also do I have to have Samba installed in order to use CIFS? And actually I think that's what I need since Samba is only for back compatibility with the older Windows versions.... What do I need to use CIFS?
Any other suggestion?
Thank you.
Last edited by ONEEYEMAN on Sat Apr 09, 2005 4:58 am; edited 1 time in total |
|
| Back to top |
|
|
darkphader
Veteran
Joined: 09 May 2002
Posts: 1225
Location: Motown
|
| Posted: Sat Apr 09, 2005 4:58 am Post subject: |
|
|
I can only suggest that you verify that smbfs or cifs, whichever you're using, are compiled into or as modules for the currently running kernel. If they are modules make sure thay are loaded (lsmod).
_________________
WYSIWYG - What You See Is What You Grep |
|
| Back to top |
|
|
ONEEYEMAN
Advocate
Joined: 01 Mar 2005
Posts: 3674
|
| Posted: Sat Apr 09, 2005 5:02 am Post subject: |
|
|
Well Samba compiled in the kernel. I could try to recompile it as a module and see what happens. BTW, what module will CIFS compiled into?
Thank you. |
|
| Back to top |
|
|
darkphader
Veteran
Joined: 09 May 2002
Posts: 1225
Location: Motown
|
| Posted: Sat Apr 09, 2005 5:18 am Post subject: |
|
|
| ONEEYEMAN wrote: | | Well Samba compiled in the kernel. I could try to recompile it as a module and see what happens. BTW, what module will CIFS compiled into? |
You are missing an important point. Samba is not smbfs. Samba != smbfs. Samba is not equivalent to smbfs. Samba and smbfs are different things. You cannot compile Samba into the kernel nor as a kernel module, the option simply does not exist.
Look at help on CIFS during the configure, the module is probably called cifs.
_________________
WYSIWYG - What You See Is What You Grep |
|
| Back to top |
|
|
ONEEYEMAN
Advocate
Joined: 01 Mar 2005
Posts: 3674
|
| Posted: Sat Apr 09, 2005 6:31 am Post subject: |
|
|
OK, so just to be clear.
Samba is a software that is installed on (any) machine and support the Windows shares. SMBFS is a file system type, and support of this file system can be compiled in the kernel directly or as a module. So, what I am saying is: SMBFS is compiled directly to the kernel, and it still doesn't work.
So, is there anything else, we could try?
Thank you. |
|
| Back to top |
|
|
darkphader
Veteran
Joined: 09 May 2002
Posts: 1225
Location: Motown
|
| Posted: Sat Apr 09, 2005 2:43 pm Post subject: |
|
|
Provide the output of: | Code: | grep 'SMB_FS' /usr/src/linux/.config
ls -l /usr/src/linux
uname -r |
_________________
WYSIWYG - What You See Is What You Grep |
|
| Back to top |
|
|
darkphader
Veteran
Joined: 09 May 2002
Posts: 1225
Location: Motown
|
| Posted: Sat Apr 09, 2005 3:09 pm Post subject: |
|
|
| ONEEYEMAN wrote: | OK, so just to be clear.
Samba is a software that is installed on (any) machine and support the Windows shares. SMBFS is a file system type, and support of this file system can be compiled in the kernel directly or as a module. |
Better to think of Samba as a piece of software that allows a 'nix system to export it's shares as SMB shares so that Windows (and other SMB enabled systems) can use them.
And to say SMBFS is a network file system type, as is CIFS.
When mounting a Windows SMB share as you are trying to do, we are not using Samba at all. It is out of the picture. We are only using SMBFS, although we should switch to CIFS for reasons previously stated.
_________________
WYSIWYG - What You See Is What You Grep |
|
| Back to top |
|
|
ONEEYEMAN
Advocate
Joined: 01 Mar 2005
Posts: 3674
|
| Posted: Sat Apr 09, 2005 5:24 pm Post subject: |
|
|
Here is the output requested:
| Code: |
bash-2.05b$ grep 'SMB_FS' /usr/src/linux/.config
CONFIG_SMB_FS=y
bash-2.05b$ ls -l /usr/src/linux
lrwxrwxrwx 1 root root 22 Mar 1 12:48 /usr/src/linux -> linux-2.6.10-gentoo-r6
bash-2.05b$ uname -r
2.6.10-gentoo-r6
|
|
|
| Back to top |
|
|
darkphader
Veteran
Joined: 09 May 2002
Posts: 1225
Location: Motown
|
| Posted: Sat Apr 09, 2005 10:05 pm Post subject: |
|
|
It all looks OK.
May be the error message isn't providing us the right information.
Also it looks like your mount string may be wrong (although it may work both ways).
Intead of | Code: | | mount -t smbfs -o Owner //your-vp7x3s9ctm/temp /mnt/winxp |
try | Code: | | mount -t smbfs -o username=Owner //your-vp7x3s9ctm/temp /mnt/winxp |
and if CIFS support is compiled in try | Code: | | mount -t cifs -o user=Owner //your-vp7x3s9ctm/temp /mnt/winxp |
as well.
_________________
WYSIWYG - What You See Is What You Grep |
|
| Back to top |
|
|
darkphader
Veteran
Joined: 09 May 2002
Posts: 1225
Location: Motown
|
| Posted: Sat Apr 09, 2005 10:41 pm Post subject: |
|
|
PS
In the above reply I am assuming that "Owner" is the valid username on the XP box (many XP Home systems come set up this way).
_________________
WYSIWYG - What You See Is What You Grep |
|
| Back to top |
|
|
ONEEYEMAN
Advocate
Joined: 01 Mar 2005
Posts: 3674
|
| Posted: Sat Apr 09, 2005 10:56 pm Post subject: |
|
|
Nope, gives exactly the same error.
Maybe I ought to recompile SMBFS support as a module?
Thank you. |
|
| Back to top |
|
|
|
Kernel & Hardware
