[Samba] Mount at boot - and a bug - where to report?
Daniel Armbrust
daniel.armbrust at charter.net
Sun Feb 2 04:02:25 GMT 2003
I have been having problems trying to get my samba mounted windows (XP)
shares to mount at boot time on my Redhat 8 machine. I have tried
changing the start order of things, but it didn't seem to help.
Here is the interesting bits from the boot.log
Feb 1 11:17:46 vortex-550 network: Setting network parameters:
succeeded
Feb 1 11:17:46 vortex-550 network: Bringing up loopback interface:
succeeded
Feb 1 11:17:49 vortex-550 network: Bringing up interface eth0:
succeeded
Feb 1 11:17:57 vortex-550 mount: 572: session request to 192.168.0.4
failed (Called name not present) Feb 1 11:17:57 vortex-550 mount: 572:
session request to 192 failed (Called name not present)
Feb 1 11:17:57 vortex-550 mount: 572: tree connect failed: ERRDOS -
ERRnoaccess (Access denied.)
Feb 1 11:17:57 vortex-550 mount: SMB connection failed
Feb 1 11:17:58 vortex-550 mount: 573: session request to 192.168.0.4
failed (Called name not present)
Feb 1 11:17:58 vortex-550 mount: 573: session request to 192 failed
(Called name not present)
Feb 1 11:17:58 vortex-550 mount: 573: tree connect failed: ERRDOS -
ERRnoaccess (Access denied.)
Feb 1 11:17:58 vortex-550 mount: SMB connection failed
Feb 1 11:17:59 vortex-550 mount: 574: session request to 192.168.0.4
failed (Called name not present)
Feb 1 11:17:59 vortex-550 mount: 574: session request to 192 failed
(Called name not present)
Feb 1 11:17:59 vortex-550 mount: 574: tree connect failed: ERRDOS -
ERRnoaccess (Access denied.)
Feb 1 11:17:59 vortex-550 mount: SMB connection failed
Feb 1 11:18:00 vortex-550 mount: 575: session request to 192.168.0.4
failed (Called name not present) Feb 1 11:18:00 vortex-550 mount: 575:
session request to 192 failed (Called name not present)
Feb 1 11:18:00 vortex-550 mount: 575: tree connect failed: ERRDOS -
ERRnoaccess (Access denied.)
Feb 1 11:18:00 vortex-550 mount: SMB connection failed
Feb 1 11:18:00 vortex-550 netfs: Mounting SMB filesystems: failed
Feb 1 11:18:01 vortex-550 netfs: Mounting other filesystems: succeeded
Feb 1 11:18:01 vortex-550 autofs: automount startup succeeded
Feb 1 11:18:01 vortex-550 sshd: Starting sshd:
Feb 1 11:18:01 vortex-550 sshd: succeeded
Feb 1 11:18:02 vortex-550 sshd:
Feb 1 11:18:02 vortex-550 rc: Starting sshd: succeeded
Feb 1 11:18:05 vortex-550 xinetd: xinetd startup succeeded
Feb 1 11:18:06 vortex-550 ntpd: succeeded
Feb 1 11:18:06 vortex-550 ntpd: ntpd startup succeeded
Feb 1 11:18:09 vortex-550 lpd: lpd startup succeeded
Here is what happens when I run mount -a after it has finished booting:
vortex-550==> ~>mount -a
996: session request to 192.168.0.4 failed (Called name not present)
996: session request to 192 failed (Called name not present)
1000: session request to 192.168.0.4 failed (Called name not present)
1000: session request to 192 failed (Called name not present)
1003: session request to 192.168.0.4 failed (Called name not present)
1003: session request to 192 failed (Called name not present)
1006: session request to 192.168.0.4 failed (Called name not present)
1006: session request to 192 failed (Called name not present)
vortex-550==> ~>
But the mounts do work. I looked into the "Called name not present"
message, and it appears that there is a bug somewhere. I don't know if
it is in samba, or in the mount code. The bug is that it does not
properly deal with ip addresses. This is what part of my fstab looks
like:
//192.168.0.4/Media /mnt/vortex2533/Media smbfs auto,guest,r
//192.168.0.4/Public /mnt/vortex2533/Public smbfs auto,guest,rw
//192.168.0.4/MP3s /mnt/vortex2533/MP3s smbfs auto,guest,r
When I defined 192.168.0.4 in my host file as a named machine, and then
used that name instead of the ip address in the fstab, the messages
about "Called name not present" went away. Where should I report this
(minor) bug?
So now, when I run mount -a, It mounts all the shares with no messages.
But in my boot.log, I still get one of these for each attempted mount:
Feb 1 11:18:00 vortex-550 mount: 575: tree connect failed: ERRDOS -
ERRnoaccess (Access denied.)
Can anyone give me a clue why these mounts fail at boot time?
More information about the samba
mailing list