Jump to content

Samba users problem (Win98 and MDK8.1)


Steve Scrimpshire
 Share

Recommended Posts

For some reason, frequently I have to go back into SWAT and reenable my Windows user to enable my Win98SE computer to see the Linux shares accessible by them. Does anyone know what causes this and how to prevent it or is it normal?

 

Here is my smb.conf (laluna is my Win98 user):

# Samba config file created using SWAT

# from localhost.localdomain (127.0.0.1)

# Date: 2002/12/28 19:43:23



# Global parameters

[global]

netbios name = OMAR

netbios aliases = omar

server string = Samba Server %v

interfaces = 192.168.0.1/255.255.255.0

encrypt passwords = Yes

update encypted = Yes

log file = /var/log/samba/log.%m

max log size = 50

socket options = TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=8192

printcap name = lpstat

local master = No

wins server = 192.168.0.1

default service = homes

path = /home/public

valid users = omar laluna

hosts allow = 192.168.0.0/255.255.255.0 127.0.0.1 192.168.

printing = cups



[homes]

comment = Home Directories

path = /home/%u

read only = Yes

hosts allow = 192.168.0.0/255.255.255.0 127.0.0.1 192.168.255.255 192.168.0.2



[printers]

comment = All Printers

path = /var/spool/samba

create mask = 0700

guest ok = Yes

printable = Yes

print command = lpr-cups -P %p -o raw %s -r   # using client side printer drivers.

lpq command = lpstat -o %p

lprm command = cancel %p-%j

browseable = No



[Linux]

comment = Linux

path = /

Relevant smbpasswd lines:

 omar:501:<<encrypted password>>:[UN         ]:LCT-3E01471D

laluna:502:<encrypted password:[U          ]:LCT-3E0F43C1:

 

smbusers:

 pted = Yes

log file = /var/log/samba/log.%m

max log size = 50

socket options = TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=8192

printcap name = lpstat

local master = No

wins server = 192.168.0.1

default service = homes

path = /home/public

valid users = omar laluna

hosts allow = 192.168.0.0/255.255.255.0 127.0.0.1 192.168.

printing = cups



[homes]

comment = Home Directories

path = /home/%u

read only = Yes

hosts allow = 192.168.0.0/255.255.255.0 127.0.0.1 192.168.255.255 192.168.0.2



[printers]

comment = All Printers

path = /var/spool/samba

create mask = 0700

guest ok = Yes

printable = Yes

print command = lpr-cups -P %p -o raw %s -r   # using client side printer drivers.

lpq command = lpstat -o %p

lprm command = cancel %p-%j

browseable = No



[Linux]

comment = Linux

path = /

Relevant smbpasswd lines:

 omar:501:<<encrypted password>>:[UN         ]:LCT-3E01471D

laluna:502:<encrypted password:[U          ]:LCT-3E0F43C1:

 

smbusers:

  pted = Yes

log file = /var/log/samba/log.%m

max log size = 50

socket options = TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=8192

printcap name = lpstat

local master = No

wins server = 192.168.0.1

default service = homes

path = /home/public

valid users = omar laluna

hosts allow = 192.168.0.0/255.255.255.0 127.0.0.1 192.168.

printing = cups



[homes]

comment = Home Directories

path = /home/%u

read only = Yes

hosts allow = 192.168.0.0/255.255.255.0 127.0.0.1 192.168.255.255 192.168.0.2



[printers]

comment = All Printers

path = /var/spool/samba

create mask = 0700

guest ok = Yes

printable = Yes

print command = lpr-cups -P %p -o raw %s -r   # using client side printer drivers.

lpq command = lpstat -o %p

lprm command = cancel %p-%j

browseable = No



[Linux]

comment = Linux

path = /

Relevant smbpasswd lines:

 omar:501:<<encrypted password>>:[UN         ]:LCT-3E01471D

laluna:502:<encrypted password:[U          ]:LCT-3E0F43C1:

Link to comment
Share on other sites

The problem is a little vague but I think that windows is set to rescan the network every 30 minutes or so. This causes problems if a new computer is booted up and windows misses its announcement that it has connected to the network. This also happens amongst windows machines. Therefore, it wont pick up the new machine until it rechecks the network. I don't know if there is a way to force it to rescan the network or shorten the rescanning period. Linux allows you to force a rescan any time. I don't know if this is actually the problem you're describing but that's my $0.02 worth (not adjusted for inflation :wink: ).

 

Glitz.

Link to comment
Share on other sites

Well, it has nothing to do with Windows refreshing the view of the network. I can look in /var/log/samba/nmbd.log and see something like this:

 

User 'nobody': Invalid user

 

(or something to that effect.) and then I can go into SWAT and go to Password and type in laluna and her password and then click 'Enable user' and VOILA, she can log in and the shares show up in Windows. I have to 'Enable User' quite often. Dunno what causes it.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...