[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: AARRGGHH: Samba + WinXP Home



On Wed, Feb 05, 2003 at 02:15:26PM +0100, Wilfried Essig wrote:
> Dear David,
> 
> 
> David Purton sagte:
> > We Just bought a new server at work and its running linux + samba.
> > Most seems to run fine, except I can't make the WinXP boxes remember
> > their passwords for reconnecting to shares at login.
> I assume you are able to connect to samba "by hand" (by explorer and
> mouse). 

Yes - winXP asks for both a username and a password which enable
connection to the server.

> Maybe i could ask you if you know that "smbpasswd" on linux
> console is necessary to change samba-passwords?

this is all set up I think as it should be

linux accounts have been created and users have been added to
smbpasswd file also.

> 
> Are you asked for username/password when making the connect by hand? Is
> your samba login and password the same as your locals at winxp? If not, it
> would be much better make them the same.

mmm - this is a possible issue

linux and smbpasswd are the same, but the win XP passwords are prolly
set to blank - user names are the same on each.

> 
> If the problem is only the automatic login at startup i would expect, that
> your Workstation won't find the server at once. In that case you should
> make your samba a wins server. Have also a look at your dns. Maybe you
> should create file "lmhosts" out of "lmhosts.sam" (editing name and adress
> of your server into it) and set "use lmhosts" inside the properties of yor
> tcp/ip-stack.
> 

No - It's not this - You just need to log out, then log in again for
the win XP boxes to not be able to reconnect.

And I can view the samba logs to see XP try to reconnect, but fail
with a bad password. (correct username is sent)


> Do you get your ip-address by dhcp? then you could give your wxx
> helpful

all ip addresses are static

> tips by your dhcp.conf :
> subnet 192.168.0.0 netmask 255.255.255.0
>   {
>   authoritative;
>   range 192.168.0.20 192.168.0.99;
>   option domain-name-servers 192.168.0.1;
>   option routers 192.168.0.1;
> # this to lines :
>   option netbios-name-servers 192.168.0.1;
>   option netbios-node-type 8;
> # !!
>   option broadcast-address 192.168.0.255;
>   }
> 
> 
> Maybe, my smb.conf is more worthy for you. It runs with winxp-home and w95
> very clean.


mmm - much the same. Only possible difference is I haven't included
wins support, but I would not have thought that a likely cause of
problems.

win98 clients also do not experience any problems


> # Global parameters
> [global]
>         interfaces = 192.168.0.0/255.255.255.0
>         passwd program = /usr/bin/passwd %u
>         debug level = 1
>         passwd chat = *Enter\snew\sUNIX\spassword:* %n\n
> *Retype\snew\sUNIX\spassword:* %n\n .
>         read prediction = yes
>         dns proxy = No
>         encrypt passwords = Yes
>         server string = %h server (Samba %v)
>         workgroup = Essignetz
>         syslog = 0
>         getwd cache = yes
>         socket options = TCP_NODELAY IPTOS_LOWDELAY
>         bind interfaces only = Yes
>         wins support = true
>         hosts allow = 192.168.0.0/255.255.0.0
> 
> [homes]
>         comment = Home Directories
>         writeable = Yes
>         create mask = 0700
>         directory mask = 0700
> 
> [root]
>         comment = root
>         path = /
>         writeable = Yes
>         create mask = 0700
>         directory mask = 0700
> 
> [printers]
>         comment = All Printers
>         path = /tmp
>         create mask = 0700
>         printable = Yes
>         browseable = No
> 


-- 
David Purton
dcpurton@chariot.net.au

If you, O LORD, kept a record of sins, O Lord, who could stand?
					Psalm 130:3

Attachment: pgp9x4FFWWXxH.pgp
Description: PGP signature


Reply to: