Yes now i can see my Win7 laptop on my Linux desktop can open it but on the map users i get: failed to mount Windows share.On my Win7 laptop i now can see my Linux desktop but can"t access it. Windows says the problems is filesharingon the Linux comp.Could this have something to do with the Firewall?Anyway sofar so good!

nuovo wrote:Yes now i can see my Win7 laptop on my Linux desktop can open it but on the map users i get: failed to mount Windows share.On my Win7 laptop i now can see my Linux desktop but can"t access it. Windows says the problems is filesharingon the Linux comp.Could this have something to do with the Firewall?Anyway sofar so good!

I'm following this thread with interest as I encountered the same problem adding a Windows 7 Home Premium computer to my network, which was running perfectly fine with Windows XP and Linux Mint computers. Always I got the error message "Failed to mount Windows share," even if I disable firewall and antivirus on Windows and open up the paths to everyone and the security as well. In the end I got tired of hitting the same roadblock, and solved the problem by a single command. Here is the command: format c: . Not recommended unless you want to get rid of Windows 7. I had a Windows XP drive ready and waiting in the wings to replace it so the only thing lost was the time messing around with Windows 7. If you get Windows 7 working on your network then bravo. Now there are a lot of "helpful suggestions" on the Internet that recommend running programs and services that are not available on Windows 7 Home Premium, so beware.

Sorry for this late reaction but have been busy restoring my Win7 installation, since it froze yesterday. Had to run restore! Don't know what caused it. Now i can see my win7 laptop on my Mint comp and have acces to a lot of maps, although i can't open them. On my Win laptop i see my Mint comp but don't have access at all.

Here you are:cornelis@lintje ~ $ cat /etc/samba/smb.conf## Sample configuration file for the Samba suite for Debian GNU/Linux.### This is the main Samba configuration file. You should read the# smb.conf(5) manual page in order to understand the options listed# here. Samba has a huge number of configurable options most of which # are not shown in this example## Some options that are often worth tuning have been included as# commented-out examples in this file.# - When such options are commented with ";", the proposed setting# differs from the default Samba behaviour# - When commented with "#", the proposed setting is the default# behaviour of Samba but the option is considered important# enough to be mentioned here## NOTE: Whenever you modify this file you should run the command# "testparm" to check that you have not made any basic syntactic # errors. # A well-established practice is to name the original file# "smb.conf.master" and create the "real" config file with# testparm -s smb.conf.master >smb.conf# This minimizes the size of the really used smb.conf file# which, according to the Samba Team, impacts performance# However, use this with caution if your smb.conf file contains nested# "include" statements. See Debian bug #483187 for a case# where using a master file is not a good idea.#

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of workgroup = WORKGROUP

# Windows Internet Name Serving Support Section:# WINS Support - Tells the NMBD component of Samba to enable its WINS Server# wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both; wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS. dns proxy = no

# What naming service and in what order should we use to resolve host names# to IP addresses; name resolve order = lmhosts host wins bcast

#### Networking ####

# The specific set of interfaces / networks to bind to# This can be either the interface name or an IP address/netmask;# interface names are normally preferred; interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the# 'interfaces' option above to use this.# It is recommended that you enable this feature if your Samba machine is# not protected by a firewall or is a firewall itself. However, this# option cannot handle dynamic or non-broadcast interfaces correctly.; bind interfaces only = yes

#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine# that connects log file = /var/log/samba/log.%m

# If you want Samba to only log through syslog then set the following# parameter to 'yes'.# syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log# through syslog you should set the following parameter to something higher. syslog = 0

# "security = user" is always a good idea. This will require a Unix account# in this server for every user accessing the server. See# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html# in the samba-doc package for details.# security = user

# You may wish to use password encryption. See the section on# 'encrypt passwords' in the smb.conf(5) manpage before enabling. encrypt passwords = true

# If you are using encrypted passwords, Samba will need to know what# password database type you are using. passdb backend = tdbsam

# For Unix password sync to work on a Debian GNU/Linux system, the following# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for# sending the correct chat script for the passwd program in Debian Sarge). passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes# when requested by an SMB client instead of the program listed in# 'passwd program'. The default is 'no'. pam password change = yes

# Is this machine able to authenticate users. Both PDC and BDC# must have this setting enabled. If you are the BDC you must# change the 'domain master' setting to no#; domain logons = yes## The following setting only takes effect if 'domain logons' is set# It specifies the location of the user's profile directory# from the client point of view)# The following required a [profiles] share to be setup on the# samba server (see below); logon path = \\%N\profiles\%U# Another common choice is storing the profile in the user's home directory# (this is Samba's default)# logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set# It specifies the location of a user's home directory (from the client# point of view); logon drive = H:# logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set# It specifies the script to run during logon. The script must be stored# in the [netlogon] share# NOTE: Must be store in 'DOS' file format convention; logon script = logon.cmd

# Using the following line enables you to customise your configuration# on a per machine basis. The %m gets replaced with the netbios name# of the machine that is connecting; include = /home/samba/etc/smb.conf.%m

# Most people will find that this option gives better performance.# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html# for details# You may want to add the following on a Linux system:# SO_RCVBUF=8192 SO_SNDBUF=8192# socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package# installed. The samba maintainer and the linpopup maintainer are# working to ease installation and configuration of linpopup and samba.; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this# machine will be configured as a BDC (a secondary logon server), you# must set this to 'no'; otherwise, the default behavior is recommended.# domain master = auto

# The following was the default behaviour in sarge,# but samba upstream reverted the default because it might induce# performance issues in large organizations.# See Debian bug #368251 for some of the consequences of *not*# having this setting and smb.conf(5) for details.; winbind enum groups = yes; winbind enum users = yes

# Un-comment the following (and tweak the other settings below to suit)# to enable the default home directory shares. This will share each # user's home director as \\server\username;[homes]; comment = Home Directories; browseable = no

# By default, the home directories are exported read-only. Change the# next parameter to 'no' if you want to be able to write to them.; read only = yes

# File creation mask is set to 0700 for security reasons. If you want to# create files with group=rw permissions, set next parameter to 0775.; create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to# create dirs. with group=rw permissions, set next parameter to 0775.; directory mask = 0700

# By default, \\server\username shares can be connected to by anyone# with access to the samba server. Un-comment the following parameter# to make sure that only "username" can connect to \\server\username# The following parameter makes sure that only "username" can connect## This might need tweaking when using external authentication schemes; valid users = %S

# Windows clients look for this share name as a source of downloadable# printer drivers[print$] comment = Printer Drivers path = /var/lib/samba/printers browseable = yes read only = yes guest ok = no# Uncomment to allow remote administration of Windows print drivers.# You may need to replace 'lpadmin' with the name of the group your# admin users are members of.# Please note that you also need to set appropriate Unix permissions# to the drivers directory for these users to have write rights in it; write list = root, @lpadmin

# The next two parameters show how to auto-mount a CD-ROM when the# cdrom share is accesed. For this to work /etc/fstab must contain# an entry like this:## /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0## The CD-ROM gets unmounted automatically after the connection to the## If you don't want to use auto-mounting/unmounting make sure the CD# is mounted on /cdrom#; preexec = /bin/mount /cdrom; postexec = /bin/umount /cdrom

The Good News: Your smb.conf file is textbook correct.The Bad News: You don't have any shares defined in smb.conf and the output of the usershare command indicated you didn't create any shares through Nemo so there is nothing for the Win7 machine to access.

Open NemoRight click on /home/cornelis/PublicSelect "Sharing Options"Select "Share this folder", "Allow others to create and delete..", "Guest Access".It will ask you if you want it to alter permissions - you do.You just created a guest accessible samba share.

Now run the following command and see if your machine and the public share show up:

I now have been able to see my Lin-comp. on my Win labtop. Had to switch off the linuxfirewall. Seen the Hp deskjet printer. This printer is controlled with a driver for linux, i don think i will be able to send a printjob to my linuxcomputer from my winlaptop. Anyway thank you for your help.