Need some help here.

My wireless system for my server is found, it is connected according to the
upper right "Dish Array", shows it is connected to my LAN, but when I try to FIND
the SAMBA server on the LAN network, it is not found. Nothing is found except a WorkGroup, which is meaningless to me.

If I run VMWare, and run windows 7, transfer the wireless adapter to the VM, I am able to find the server and connect like I am supposed to.

But my orignal HOST (operating system), only finds the LAN, and never comes up with the server.

It USED to, every ONCE in a while, but for the most part, 99 percent does not come up with the samba server.

Can someone help me out here?

Thanks in advance!

Dwayne

Is there a reason you need it to autodetect the server? I find that breaks down on Windows systems accessing other Windows systems all the time as well, I never rely on it. Since this is a server you're accessing, presumably it has a static IP on your network, in which case you can just add an entry in /etc/fstab to auto-mount it and never worry about where to find it again.

Thank you very much for your reply. . ..

My knowledge is not good enough to know how to do such a thing. . .

This is what I found on my fstab:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=10ca538b-7260-45cb-b632-adf2e6e7e962 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=07b72ab0-68e0-4e35-a488-4484a889d9eb none swap sw 0 0

Could you possibly help point me in the correct direction and what I must do?

Dwayne

You would need to add an entry for your server. This is what I use on my Linux systems to mount a Windows share, it should look very similar for you:

and /etc/sambapasswords is a file that's only readable by root that contains a valid username/password for the Windows system hosting the share.

You would of course need to change the IP, location of the share, where you want to mount it, and any options you want to adjust.

When you're ready, run "mount -a" to see if it either mounts or complains about something. If it returns without any message, presumably it mounted it, and you can run df to verify. Then just navigate to that location on your filesystem to see the remote share.

Thank you very much. . ..

This is what I put:
Our server is 192.168.3.4 address.

I went to the server and found the directory. . .It was under Timber, and this had all files I wanted.

When I mount -a this is what I get in return:

I also get this, if I do not type in mount -a

Dwayne


Trying my best to understand and learn. . .

You missed the mount location. You only have the server to mount and what the filesystem type is, the second argument (in between those two, "/home/shared" in my example) should be where on your local filesystem you want to mount it.

A workgroup is a name coined by Microsoft that defines a group of computers on a peer to peer network. If you are using nautilus and trying to browse the network you might see an icon called workgroup. By selecting the workgroup icon hopefully any computer in the workgroup will be displayed. Then selecting the computer icon will show its shares.

What operating system is running on the server?

to Both Gents that are helping me with this. . .I really appreciate it immensely.

I do not have internet at home, only at work, so forgive me for not replying sooner.

So, instead of this:
I should have this:

Where the first part is where the server is
and /home/Dwayne is where all of my files are stored on my personal machine.

I recognize the file mode. . .I need to be able to read and write, so would mode be mode=0777 ?

Dwayne

Thank you Michael. . .

I have tried my best to stay away from Microsoft work groups. My guess is, one of the salesmen has turned theirs on, and is showing up in the network.

I try to keep "passwords" to a minimum. Yet try to security to a maximum. . .(if you can call it that <grin>)

The second field is the mount location. This should be an EMPTY directory on your local filesystem where the remote server will be mounted. You could use /home/Dwayne, but as soon as you mounted the share everything that WAS in /home/Dwayne will disappear, and all that you'll see there is the remote filesystem. Your files aren't deleted, they're just being "covered up" by the remote mount, you won't be able to access them again until the share is unmounted and /home/Dwayne reverts back to the local filesystem.

You could put it in something like /home/Dwayne/Timber, but I don't recommend mounting remote filesystems in your home directory unless you know what you're doing and why, it's generally better to put them elsewhere in a neutral location, such as /home/Timber or similar.

file permissions are octal.
read is 4
write is 2
execute is 1

Add the permissions you want up and you get a number 0-7. First number is a 0, that just means it's octal. Second number is the owner of the file, third number is any members of the same group as the file, fourth number is everybody else. So if you want the owner to have read and write permission, group members to have read-only permission, and everybody else to be blocked, you would use "0640". 0664 is pretty standard for files, it gives the owner and group read-write permission and everybody else read-only permission. 0775 is the equivalent for directories. Directories need execute permission in order to traverse them, so again that's read-write (and execute) for the owner and group, and read-only (and execute) for everybody else. 0775 would only be used for executable files, which would be pretty rare on a Windows share, since you wouldn't be able to execute any of your Windows binaries on Linux anyway. "0777" permissions are wide open, it means anybody can do anything they want with any of the files/dirs.