• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 641
  • Last Modified:

Samba errors and very, very slow.

Hello all!!

Again Samba errors.

I have one server with samba and Linux CentOS 5,2 running remotely some applications fox pro and MS-Office on this server in some desktops this applications open very fast without problem but some desktops is very very very slow, after 10 minutes the application is open.

I tried install desktop directly on switch and in different ports to discard physical problem.
I tried format desktop and reinstall windows XP and nothing.
I tried enable port 139 on samba server and nothing.

What happen? My last solution format Linux Server e install Windows Server. :o(

Please I'm crazy with this problem!!!

Thank you.
If someone come to Brazil, I pay the beer... :o)


LOG ERRORS:

[2009/02/13 11:13:56, 0] lib/util_sock.c:get_peer_addr(1224)
getpeername failed. Error was Transport endpoint is not connected
[2009/02/13 11:13:56, 0] lib/util_sock.c:get_peer_addr(1224)
getpeername failed. Error was Transport endpoint is not connected
[2009/02/13 13:11:58, 0] lib/util_sock.c:get_peer_addr(1224)
getpeername failed. Error was Transport endpoint is not connected
[2009/02/13 13:11:58, 0] lib/util_sock.c:get_peer_addr(1224)
getpeername failed. Error was Transport endpoint is not connected
[2009/02/13 13:23:34, 0] lib/util_sock.c:get_peer_addr(1224)
getpeername failed. Error was Transport endpoint is not connected
[2009/02/13 13:23:34, 0] lib/util_sock.c:get_peer_addr(1224)
getpeername failed. Error was Transport endpoint is not connected
[2009/02/13 15:19:26, 0] lib/util_sock.c:get_peer_addr(1224)
getpeername failed. Error was Transport endpoint is not connected
[2009/02/13 15:19:26, 0] lib/util_sock.c:get_peer_addr(1224)
getpeername failed. Error was Transport endpoint is not connected
[2009/02/13 18:06:40, 0] lib/util_sock.c:get_peer_addr(1224)
getpeername failed. Error was Transport endpoint is not connected
[2009/02/13 21:13:04, 0] lib/util_sock.c:get_peer_addr(1224)

   
My smb.conf

[global]
        workgroup = EXECUCAO
        passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
        username map = /etc/samba/smbusers
        syslog = 0
        name resolve order = wins bcast hosts
#       printcap name = CUPS
        show add printer wizard = No
        add user script = /usr/sbin/useradd -m '%u'
        delete user script = /usr/sbin/userdel -r '%u'
        add group script = /usr/sbin/groupadd '%g'
        delete group script = /usr/sbin/groupdel '%g'
        add user to group script = /usr/sbin/usermod -G '%g' '%u'
        add machine script = /usr/sbin/useradd -s /bin/false -m '%u'
        logon script = sistema.bat
        logon path =
        logon drive = X:
        domain logons = yes
        preferred master = yes
        wins support = yes
#       os level = 100
#       announce as = NT Server
#
#       printing = CUPS
#
        unix charset = ISO8859-1
        display charset = ISO8859-1
        create mask = 0777
        directory mask = 0777
        force create mode = 0777
        force directory mode = 0777
;       force user = nobody
;       force group = nobody
        server string = Servidor de Dominio
        log file = /var/log/samba/%m.log
        max log size = 50
#       socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
        socket options = SO_KEEPALIVE TCP_NODELAY SO_RCVBUF=32768 SO_SNDBUF=32768
        idmap uid = 10000-20000
        idmap gid = 10000-20000
        template shell = /bin/false
#[homes]
#   comment = Home Directories
#   browseable = yes
#   writable = yes
# Un-comment the following and create the netlogon directory for Domain Logons
[netlogon]
        comment = Network Logon Service
        path = /home/netlogon
        guest ok = yes
        share modes = no
        writeable = yes
        write list = root
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
[Profiles]
        path = /home/profiles
        browseable = no
        guest ok = yes
# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
#
#[printers]
#       comment = All Printers
#       path = /var/spool/samba
#       browseable = yes

[Fiscal - Financeiro]
        path = /home/dados/sistemas/FinWin
        writeable = yes
        guest ok = no
        valid users = @diretoria,edson,danielly,root

[Sistemas]
        path = /home/dados/sistemas
        writeable = yes
        guest ok = no
        valid users = @diretoria,edson,root

[Sistema RH]
        path = /home/dados/sistemas/
        guest ok = no
        writeable = yes
        valid users = @diretoria,vivian,cleusa,paquito,janaina,root

[Recursos Humanos]
        path = /home/dados/rh
        guest ok = no
        writeable = yes
        valid users = @diretoria,vivian,cleusa,paquito,janaina

[Juridico]
        path = /home/dados/juridico
        guest ok = no
        writeable = yes
        valid users = @diretoria,carla

[Financeiro]
        path = /home/dados/financeiro
        guest ok = no
        writeable = yes
        valid users = @diretoria,danielly

[Contabil]
        path = /home/dados/contabil
        guest ok = no
        writeable = yes
        valid users = @diretoria,edson

[Contabilidade]
        path = /home/dados/contabilidade
        guest ok = no
        writeable = yes
        valid users = @diretoria,danilo,edson,erica

[Diretoria]
        path = /home/dados/diretoria
        guest ok = no
        writeable = yes
        valid users = @diretoria

[Publico]
        path = /home/publico
        writeable = yes
0
acjantsch
Asked:
acjantsch
2 Solutions
 
SergKzCommented:
Whether you checked link between a problem workstation and a server by ping command? (from windows)
ping -l 1000 -n 100 ip_address_server
and from linux server:
ping -s 1000 -c 100 ip_address_workstation
if you see more than 3-4% of loss packets, so you have problem in network infrastructure.
Also, if your server isn't in the same localnet as workstation, check the path to server and back by command
tracert server_ip_adr  (from windows)
traceroute workstation_ip_adr (from server)
if you see timeouts or delays in traceroute hops, maybe there is problem in DNS.
In this case, try to connect to server by ip address, not by name.
0
 
Maciej SsysadminCommented:
0
 
acjantschAuthor Commented:
Microsoft Windows XP [versão 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\edson>ping fileserver

Disparando contra fileserver [192.168.0.100] com 32 bytes de dados:

Resposta de 192.168.0.100: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.0.100: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.0.100: bytes=32 tempo<1ms TTL=64
Resposta de 192.168.0.100: bytes=32 tempo<1ms TTL=64

Estatísticas do Ping para 192.168.0.100:
    Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de perda),
Aproximar um número redondo de vezes em milissegundos:
    Mínimo = 0ms, Máximo = 0ms, Média = 0ms

C:\Documents and Settings\edson>ping -l 1000 -n 100 192.168.0.100

Disparando contra 192.168.0.100 com 1000 bytes de dados:

Resposta de 192.168.0.100: bytes=1000 tempo=1ms TTL=64
Resposta de 192.168.0.100: bytes=1000 tempo=1ms TTL=64
Resposta de 192.168.0.100: bytes=1000 tempo=1ms TTL=64

Estatísticas do Ping para 192.168.0.100:
    Pacotes: Enviados = 43, Recebidos = 43, Perdidos = 0 (0% de perda),
Aproximar um número redondo de vezes em milissegundos:
    Mínimo = 1ms, Máximo = 1ms, Média = 1ms


C:\Documents and Settings\edson>tracert 192.168.0.100

Rastreando a rota para 192.168.0.100 com no máximo 30 saltos

  1    <1 ms    <1 ms    <1 ms  192.168.0.100

Rastreamento concluído.


[root@fileserver ~]# ping -s 1000 192.168.0.175
PING 192.168.0.175 (192.168.0.175) 1000(1028) bytes of data.
1008 bytes from 192.168.0.175: icmp_seq=13 ttl=128 time=1.69 ms

--- 192.168.0.175 ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 12008ms
rtt min/avg/max/mdev = 1.658/1.706/1.829/0.048 ms


[root@fileserver ~]# ping -s 1000 192.168.0.230
PING 192.168.0.230 (192.168.0.230) 1000(1028) bytes of data.
1008 bytes from 192.168.0.230: icmp_seq=20 ttl=128 time=1.73 ms

--- 192.168.0.230 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 18996ms
rtt min/avg/max/mdev = 1.661/1.705/1.801/0.060 ms
[root@fileserver ~]#

C:\Documents and Settings\edson>


Microsoft Windows XP [versão 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\danielly>ping -l 1000 -n 100 192.168.0.100

Disparando contra 192.168.0.100 com 1000 bytes de dados:

Resposta de 192.168.0.100: bytes=1000 tempo=1ms TTL=64
Resposta de 192.168.0.100: bytes=1000 tempo=1ms TTL=64
Resposta de 192.168.0.100: bytes=1000 tempo=1ms TTL=64
Resposta de 192.168.0.100: bytes=1000 tempo=1ms TTL=64
Resposta de 192.168.0.100: bytes=1000 tempo=1ms TTL=64

Estatísticas do Ping para 192.168.0.100:
    Pacotes: Enviados = 36, Recebidos = 36, Perdidos = 0 (0% de perda),
Aproximar um número redondo de vezes em milissegundos:
    Mínimo = 1ms, Máximo = 3ms, Média = 1ms
Control-C
^C
C:\Documents and Settings\danielly>


Microsoft Windows XP [versão 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\danielly>ping -l 1000 -n 100 192.168.0.100

Disparando contra 192.168.0.100 com 1000 bytes de dados:

Resposta de 192.168.0.100: bytes=1000 tempo=1ms TTL=64
Resposta de 192.168.0.100: bytes=1000 tempo=1ms TTL=64
Resposta de 192.168.0.100: bytes=1000 tempo=1ms TTL=64
Resposta de 192.168.0.100: bytes=1000 tempo=1ms TTL=64

Estatísticas do Ping para 192.168.0.100:
    Pacotes: Enviados = 36, Recebidos = 36, Perdidos = 0 (0% de perda),
Aproximar um número redondo de vezes em milissegundos:
    Mínimo = 1ms, Máximo = 3ms, Média = 1ms
Control-C
^C
C:\Documents and Settings\danielly>

C:\Documents and Settings\danielly>tracert 192.168.0.100

Rastreando a rota para 192.168.0.100 com no máximo 30 saltos

  1    <1 ms    <1 ms    <1 ms  192.168.0.100

Rastreamento concluído.

C:\Documents and Settings\danielly>
0
 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

 
Morne LateganCommented:
Check the contents of the wins.dat file. Look for the entries with the server name in it, as well as the entries with the domain name in it. I had a similar problem once with multiple IP's in wins.dat (I changed the IP address AFTER installing the samba service). Both IP's get stuck in the wins database and some clients then try to connect to the wrong IP address and it takes ages before they grab the correct one.

Probably not it, but if you do find multiple IPs you need to stop samba (and winbind), delete the wrong entries, shutdown all workstations and then start samba again.
0
 
acjantschAuthor Commented:
Well,

Everyone
Thanks for help.

Brazil, 03:00 AM all desktops are off... I'm stopping samba and deleting wins.dat. and blocking traffic on 445, with hope that works.

iptables -I INPUT 1 -p tcp --dport 445 -j DROP

More later I post the results.

Thank's again..
0
 
acjantschAuthor Commented:
Everyone..

After deleted wins.dat and blocked port 445, my smdb.log is clear, without any error.

Thank you so much.

I'm very very happy. I don't need install W2K. :o)

Thank you.....
0
 
acjantschAuthor Commented:
Hello all,

This isn't wonderful???

Very clean, without any error!!!

[2009/02/15 04:02:07, 1] smbd/server.c:open_sockets_smbd(495)
  Reloading services after SIGHUP
[2009/02/16 09:02:39, 0] smbd/server.c:main(948)
  smbd version 3.0.28-1.el5_2.1 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2007
[2009/02/16 12:16:40, 1] smbd/server.c:open_sockets_smbd(495)
  Reloading services after SIGHUP
[2009/02/16 12:20:56, 1] smbd/server.c:open_sockets_smbd(495)
  Reloading services after SIGHUP
[2009/02/16 12:22:50, 1] smbd/server.c:open_sockets_smbd(495)
  Reloading services after SIGHUP
[2009/02/16 16:01:14, 1] smbd/server.c:open_sockets_smbd(495)
  Reloading services after SIGHUP
[2009/02/17 03:07:46, 0] smbd/server.c:main(948)
  smbd version 3.0.28-1.el5_2.1 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2007
[2009/02/18 11:58:19, 1] smbd/server.c:open_sockets_smbd(495)
  Reloading services after SIGHUP
0

Featured Post

[Webinar] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

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