[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 729
  • Last Modified:

Samba problem: Windows only shows guest login option

I have set up Samba on my small mixed Windows and Linux LAN.  All working normally on the Linux side but when I try to access a Linux PC from Windows XP the login dialog contains a grayed out username (myotherpc\guest) and waits for me to enter a password.  None of my root or smbpasswds work.  How do I get restore a dialog box which enables me to enter my Samba username and password instead of having a grayed out guest option?

I am running Suse Linux 10 and am a Linux newbie.  Thanks for reading this.
0
Bloodrule
Asked:
Bloodrule
  • 3
  • 2
1 Solution
 
giltjrCommented:
Can you post the parms from your smb.conf file?
0
 
BloodruleAuthor Commented:
Here it is:

# Samba config file created using SWAT
# from 127.0.0.1 (127.0.0.1)
# Date: 2006/04/16 17:00:10

[global]
workgroup = MSHOME
netbios name = PENTIUMIII
map to guest = Bad User
server signing = Auto
printcap name = cups
add machine script = /usr/sbin/useradd  -c Machine -d /var/lib/nobody -s /bin/false %m$
logon path = \\%L\profiles\.msprofile
logon drive = P:
logon home = \\%L\%U\.9xprofile
os level = 2
preferred master = no
domain master = no
ldap ssl = No
cups options = raw
include = /etc/samba/dhcp.conf
security = share
restrict anonymous = no
max protocol = NT

[homes]
comment = Home Directories
valid users = %S
read only = No
inherit acls = Yes
browseable = No

[profiles]
comment = Network Profiles Service
path = /home/peter/Documents/
create mask = 0600
directory mask = 0700
case sensitive = no
msdfs proxy = no
guest ok = yes
read only = no

[users]
comment = All users
path = /home/
inherit acls = Yes
veto files = /aquota.user/groups/shares/

[groups]
comment = All groups
path = /home/groups
read only = No
inherit acls = Yes

[printers]
comment = All Printers
path = /var/tmp
create mask = 0600
printable = Yes
browseable = No

[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin, root
force group = ntadmin
create mask = 0664
directory mask = 0775
0
 
giltjrCommented:
Are you using XP Pro or XP Home?

Are you logged on to the XP box with a userid that is defined in the smbpasswd file?
0
 
BloodruleAuthor Commented:
I'm using XP Pro.

Your response has given me the hint I needed.  Can I tell you what I did?  My username on the XP side was different from on the Linux side.  Once I renamed my XP account to the same name as my Linux username it all worked without a hitch.  However before I did that I tried adding an account on the Linux PC with the same name as my XP account and logged into Linux as that user.  Strangely, on the XP side the dialog box continued to show LinuxPC\Guest grayed out, with only the password box waiting for input.  I still don't understand that last bit but at least I could get to the files in the end by ensuring that XP and Linux were both logged into with the same name.

Have I got it right or somehow missed the point?
0
 
giltjrCommented:
It sounds almost like you mapped this once before and checked the reconnect at logon box.  I beleive that checking this box will not only attempt to reconnect at logon, but will continue to use the same userid as used the 1st time the map was done.  If you did do this, then you may want to try delete/disconnecting the map and then try re-mapping.

Please note, that your Samba server on the Linux box will use a different password than your Windows box.  You can manually keep them in sync if you want.

You also have "map to guest = Bad User" in your global section, which means if Samba on the Linux box see's a userid that it does not know about, it will automatically map that to the Guest account.
0

Featured Post

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now