|
If your server isn't a PDC (or BDC) then Domain
Logins shouldn't be set to yes.
Your server is also configured to be a WINS server
rather than a WINS client. If this box isn't your PDC, I'll guess that it
shouldn't be your WINS server either. (or if it is, your desktop probably
isn't using it as such) If that's true, then your Name Resolve Order isn't
going to be working very well, because it's using WINS (on that particular
server) as the first place to try to resolve a name. You may want to
change that around a bit.
Kev.
----- Original Message -----
Sent: Monday, March 03, 2003 2:11
PM
Subject: Re: (clug-talk) Samba &
XP
The reg hack is only if you're using samba as a pdc; i'm not in
this instance.
There's just the one client machine.
There were
no errors in the smb.log file; I was going to turn up the debugging and log
levels and test it then. Maybe I'll get more verbose error messages
then.
No, the server isn't too busy. There's just that and my machine,
that's it.
thanks,
tim
On Mon, 3 Mar 2003 10:30:33 -0700,
Kevin Anderson wrote:
>I don't use XP, but I know there is a
registry hack for it if you're using
>it to connect to
Samba.
>Again, I don't know what it does, but you'll find it
at
>http://ca.samba.org/samba/ftp/docs/Registry/
>It's called
SignOrSeal.reg.
>
>Does this happen to all the client machines or
just one?
>
>Were there also errors in the log.smbd
file?
>
>This is obvious, but... Your server isn't just too busy,
is it?
>
>Kev.
>
>
>
>----- Original
Message -----
>From: "timmy" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Sunday, March 02, 2003 3:04
PM
>Subject: (clug-talk) Samba & XP
>
>
>> I'm
running samba 2.2.7a on debian 3.0r1, kernel v2.4.20. For some
>reason,
I keep getting disconnected from the shares. i.e when listening to
>mp3s
from the
>> shared drive, the stream will get choppy, and alot of
times cut out all
>together. I though it might be the swicth I was
using, so I replaced the
>switch. I've also
>> tried replacing
all the network cables, and both the NICs (one on the
>workstation and
one on the server).
>>
>> I keep getting this message in the
log.<machinname> file:
>>
>> [2003/03/02 23:38:50, 0]
lib/util_sock.c:read_data(436)
>> read_data: read failure for 4.
Error = Connection reset by peer
>> [2003/03/02 23:38:50, 1]
smbd/service.c:close_cnum(677)
>> sausage (192.168.0.1) closed
connection to service space
>>
>> Why would my connection be
reset? It's really annoying. I've also noticed
>at this time I cannot
communicate with the server for a few seconds after;
>i.e I
cannot
>> ping it. Then all of a sudden it starts working again no
problem. I'd just
>like some suggestions as to what it might be, so I
can further troubleshoot
>he issue.
>>
>> Here's a
snapshot of my smb.conf, just the global section, as all other
>config
is shares:
>>
>> [global]
>> ;basic server
settings
>> workgroup = BIND
>> server string = Bind.cx LAN
Server
>> smb passwd file = /etc/samba/smbpasswd
>> socket
options = IPTOS_LOWDELAY TCP_NODELAY
SO_SNDBUF=8192
>SO_RCVBUF=8192
>> deadtime = 15
>>
getwd cache = Yes
>> lpq cache time = 45
>> ; PDC and Master
browser settings
>> domain master = yes
>> local master =
yes
>> preferred master = yes
>> os level = 64
>> ;
securtiy and loggin settings
>> security = user
>> encrypt
passwords = True
>> domain logons = yes
>> max log size =
0
>> log file = /var/log/samba/log.%m
>> log level =
2
>> ; other stuff
>> dns proxy = Yes
>> wins
support = Yes
>> name resolve order = wins lmhosts host
bcast
>> bind interfaces only = True
>> interfaces = eth1
192.168.0.254/255.255.255.0 127.0.0.1
>> hosts deny = ALL
>>
hosts allow = 192.168.0.0/255.255.255.0 127.0.0.1
>> debug level =
1
>> create mask = 0644
>> directory mask = 0755
>>
oplocks = True
>> level2 oplocks = True
>> read raw =
No
>> write cache size = 262144
>>
>>
TIA,
>>
>>
tim
>>
>>
>>
>>
>>
>
>
|
