samba - Feb 2003 - Mount at boot - and a bug - where to report?

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?

The called name is the netbios name. This seems to be a feature.
What command specifically are you using to mount the share?
Joel

After doing a lot of searching in the archive, I discovered that someone
else had the same problem over a year ago.  Here are the workarounds
that he posted:

<paste>


For comparison/archive purposes, here's an /etc/fstab
entry which works as expected after boot but not
before:

//w2kbox/share	/mnt/thing	smbfs  guest,ro	0 0

I have come up with 2 workarounds for the problem
inspired by your response. 

Workaround #1:
--------------
//w2kbox/share	/mnt/thing	smbfs 
username=guest,guest,ro	0 0

Workaround#2:
-------------
//w2kbox/share	/mnt/thing	smbfs 
username=guest,password=,ro	0 0

I noticed that it is a little inconsistent with regard
to tolerance of presence/absence quotes in the
argument list (actually it seems to accept anything
but username not quoted & password quoted), but that's
not a big deal.

</paste>

I tried workaround #1, and found it to work perfectly.  My mounts now
come up at boot time.  

James, thanks for the pointer to autofs -> I'm still kind of a newbie...
I tend to learn things as I need them.  Can you (or someone else) give a
brief explanation as to why I would want to use autofs instead of
putting auto in the fstab?  Not because I'm challenging it, I just would
like to know.

Thanks, 

Dan