I've been using SuSe from 9.0 (8 months) upgraded to 9.3 (3 months)

Here's the question,

Although successfully done, I always have to do a manual mounting of our server share file as - "dodjie:/home/sigeacdws005 # mount -t cifs //10.101.110.101/pub /mnt/ -o user=xxx,password=xxx" is there anyway of doing this automatically at startup?

My previous solutions were:

I already tried editing fstab to no avail (or did I make a mistake in editing fstab?).

Smb4k doesn't mount it automatically either even after editing file system from SMBFS to CIFS.

Mounting using an smbfs gives me an error "cli_negprot: SMB signing is mandatory and we have disabled it. 7545: protocol negotiation failed" meaning no luck in smbfs.

Solution or proper instruction to the above qustion will highly be appreciated.

Dodjie
1st post

Please post a copy of your fstab - I'm betting there's something wrong with it. I've never tried a samba or CIFS mount, but NFS mounts work just fine for me with a good fstab file.

First thought might be - do you have fstab updated to reflect your CIFS change?

I knew it, someone will ask this.

sigeacdws005@dodjie:~> cat /etc/fstab
/dev/hda7 / reiserfs acl,user_xattr 1 1
/dev/hda5 /data1 auto noauto,user 0 0
/dev/hdb7 /data2 auto noauto,user 0 0
/dev/hda1 /windows/C vfat users,gid=users,umask=0002,utf8=true 0 0
/dev/hdb1 /windows/D vfat users,gid=users,umask=0002,utf8=true 0 0
/dev/hdb5 /windows/E vfat users,gid=users,umask=0002,utf8=true 0 0
/dev/hda6 swap swap pri=42 0 0
/dev/hdb6 swap swap pri=42 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
proc /proc proc defaults 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
sysfs /sys sysfs noauto 0 0
/dev/cdrecorder /media/cdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
/dev/dvd /media/dvd subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0
/dev/fd0 /media/floppy subfs noauto,fs=floppyfss,procuid,nodev,nosuid,sync 0 0
//10.101.100.101/pub /mnt/ cifs username=xxx,password=xxx 0 0

and part of my dmesg |more
...........
CIFS VFS: Error connecting to IPv4 socket. Aborting operation
CIFS VFS: cifs_mount failed w/return code = -101
Capability LSM initialized
ieee1394: Initialized config rom entry `ip1394'
ieee1394: raw1394: /dev/raw1394 device initialized
video1394: Installed video1394 module
parport0: PC-style at 0x378 [PCSPP,EPP]
..........

I was thinking the failure is due to the hirarchy in booting. I still am tracing the error. Anyway, proper instruction will be apppreciated.

That looks just fine from my semi-educated standpoint (would work with NFS, at least).

other first things first - can you ping the other computer? You might be investigating a non-issue if it's as simple as network config (or re-config). Is the windows box running any kind of firewall that would block access?

And if you knew someone was going to ask to see your fstab, why didn't you post it in the first place? Help us help you...

I am wondering if perhaps networking is not yet up when it attempts to mount? Have you tried adding your own 'mount' statement to rc.local or similar?

Matir,

That's what I am also thinking when I said "hierarchy in booting".I haven't got my own module to bypass this problem (frankly, I don't know how to). I'm still looking for a solution to this problem, giving me a hard time. I am setting up my own Linux Box to connect to our win2003 server (big company here), this is my last problem. Most of our files/software (Financial Information System, Management Information System etc.) had already been setup to run automatically in my SuSe 9.3 (using wine and dosemu) except this auto mounting thingy.

Another thing, what if I insert this "mount -t cifs //10.101.110.101/pub /mnt/ -o user=xxx,password=xxx" to my etc/init.d/boot.local, will there be any consequences?

So please, any solution will greatly be appreciated.

If i can mount it manually using a console, of course, I can ping not only the server but all PC connected to the server and of course, I can go through the server firewall, right?

About my not posting my fstab in the first place, well, I researched the Linux Tutorials on Networking first before I posted my problem and am 100% sure that my fstab is correct. Reason why I didn't post my fstab.

No sarcasm intended, really.

I can't think of any consequences. It will mount it for you.

Something I noticed that may or may not make a difference: to get nfs up and running in my fstab I had to use the following format instead of the one you're running now:

The main difference is yours has some preceeding //'s and no colon. I couldn't get it working that way either, but this worked as a snap. *shrug*

A smb uri is of the form //host/share. NFS is of the form host:/directory. //ip/share works as well.

Yes I'll try this later.

Didn't work.

I think, I found the solution to my problem, the main thing is I don't know how to edit this .

Please, if anyone can give me an instruction, this might solve my problem.

That's talking about patching and reinstalling the samba source.

How to do it, I'm getting desperate here.

Download and extract the source, then make the changes they discuss.