Hello all, my situation at the moment is I have my primary linux machine (Slackware 10.1) and I have my Windows 2000 (strickly because I need my S-Video to work) as my secondary. On my Windows 2000 machine I have set the correct permissions to log into the machine as a user on my Linux box and that is well. I can edit and change files etc. from my primary which is great. The ordeal in which I am facing is being able to automount the remote share onto my Linux box. I followed the tutorial on just linux and I added the following to my fstab.

//192.168.2.162/shared /mnt/Windows2000 -o username=*****,password=***** 0 0

this appears to be the incorrect method. Aswell I tried SMB4k which is a great application but I accidently chmod u+s to smbmount and now I can no longer mount with that is you can please tell me how to get that fixed as well that would be great. Thanks again for all the great help.

I do alot of networking to so I'll try to help you here. I just have a few questions for you. The way I understand what your saying is you use mainly Linux around the house, but you have one Windows 2000 client box (I'm assuming you are at home and this makes the most sense if this is wrong tell me) that you use as a file server as well as for other purposes having to do with the video card and programs you used on the box. Rather than storing all the files on a linux file server you want the files to stay on the Windows 2000 box. You also when you boot want to mount the share on the 2000 box at boot on your Linux box.
One major issue I see with your fstab entry is no file system type is listed. If you can still sucessfully mount using your smb tool, I would recommend using the following example for an fstab entry as all one line. I got this to work to connect to my samba server. make sure you substitute username and password for the ****'s.



//192.168.x.x/myshare /mnt/mountpoint smbfs username=******,password=********* 0 0

here is an example of the proper format definately don't use the -o .

If you can't mount using this or the smb mount tool it may have to do with the fact that you used the chmod u+s command. The question is what file system or section of the file system did you use it on. Did you run the command by itself or as an option to a mounting command? Will windows still read it's file system? Are there any other problems running programs on the Linux or windows box.
From reading the man pages for chmod if that was all you used, the u option is for user who owns it and +s is to set sticky bit on.
More on that later

Thanks for your quick repsonse I now go the folder from the Windows directory to mount on Linux upon startup. Yet again I cannot thank you enough on that. Now concerning the other issue I issued the command chmod u+s smbmount in the /usr/bin directory if that leads you to any more thoughts on how I can solve this fiasco. Thanks again

If your computer is succesfully mounting the windows share at boot, congratulations. If not post clearly that is isn't working.
As far as chmod u+s /usr/bin
What that did was turn on the sticky bit for the usr not that that really makes sense as a command it probably just turned on the sticky bit reguardless of the weird syntax here.
Here is a quick lesson on permissions so I can explain the permission you enabled.
Many linux users use a number system rather than the letters.
For example various combinations of 4 2 and 1 added together define Linux Permissions for the ext2 and 3 file systems at least. These stand for the basic permissions read 4 write 2 and execute 1. When applied to files and folders they protect your file system.
When you use the chmod command using the number you set the permissions for the owner (user) group and everone else.
For example chmod 761 /usr/bin would cause /bin to be read write and execute for the owner, read and write for the owning group, and execute for everyone else.
There is one more bit that is often overlooked the fourth digit that is assumed when not written.
4 stands for Suid. This allows the file when executed to preform it's tasks with the permissions of the owner. 2 stands for Guid. this allows the file when executed to preform it's tasks with the permissions of the group that owns the file.
Now to your questions 1 the sticky bit the fourth digit. This causes files when created in the folder it's set on to have the group that owns the folder to the be the owning group as opposed to the users group. It's a very useful setting.

To undo this if there is any problems I would recommend the command chmod u-s /usr/bin .
If that command caused any damage that should fix it. You can always use the man command to learn more about a command though sometimes it's rather dry. for example
man chmod
that would tell you that you turned on the sticky bit and you could figure out what to research if not how to turn it off.

danny