samba timeout solved

[tm]

no pags  i had reloaded the os and forgot to set the static ip address. remembered between commands
    tom

[tm]

terry do you mean smb://192.168.1.2/homes

[pags]

With regards to this:

Try replacing the server name with the IP address (to rule out name resolution as an issue...)
Terry
   I am using Konqueror as per instructed and url is
   smb://samba-server/homes
                                                             tom
     

Looks like a bit was missing...for this, I suggested thay you use the IP instead of the server name, in order to rule out name resolution from the equation...

[tm]

terry do you mean smb://192.168.1.2/homes
   tom

[tm]

terry used smb://192.168.1.2/homes   . Timed out

[tm]

By the way pags and terry thank you for all your efforts. There is likely no other forum like this one  tom

[pags]

terry used smb://192.168.1.2/homes   . Timed out

What do you get if you try

Code: [Select]

smb://192.168.1.2/
Here (on an admittedly older SAMBA server that desperately needs updating), this displays my available shares.

I presume you're using Dolphin...

You're trying to access a "homes" share...do you have a "homes" share defined?

[TerryN]

[tom@localhost ~]$ smbtree -N
failed negprot: NT_STATUS_INVALID_NETWORK_RESPONSE
failed negprot: NT_STATUS_INVALID_NETWORK_RESPONSE

This looks like a network/netmask issue.
Please check the values you have for "hosts allow =" and "interfaces="  in the global section of smb.conf.  (Running testparm -s may show you)

Terry.

[tm]

No i was instructed to use konq** but I will try chrome

[pags]

No i was instructed to use konq** but I will try chrome

Why Chrome?

Have you looked at Terry's suggestion?

[tom@localhost ~]$ smbtree -N
failed negprot: NT_STATUS_INVALID_NETWORK_RESPONSE
failed negprot: NT_STATUS_INVALID_NETWORK_RESPONSE

This looks like a network/netmask issue.
Please check the values you have for "hosts allow =" and "interfaces="  in the global section of smb.conf.  (Running testparm -s may show you)

Terry.

[TerryN]

No i was instructed to use konq** but I will try chrome

The problem is at a lower level than the browser/File Manager so it won't make any difference  
We need to get some valid responses to the smbtree and smbclient commands before worrying about application level.

Please see reply #22

Terry

[tm]

terry working on it   . i work nights and had to get some sleep  tom

[tm]

terry should i run "testparm -s" from server or client  tom

[tm]

terry   from server

root@localhost ~]# testparm -s
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[printers]"
Processing section "[print$]"
Processing section "[pdf-gen]"
Processing section "[homes]"
Loaded services file OK.
Warning: Service printers defines a print command, but rameter is ignored when using CUPS libraries.
Server role: ROLE_STANDALONE
[global]
        workgroup = MSHOME
        netbios name = SAMBA-SERVER
        server string = %h
        security = SHARE
        map to guest = Bad User
        log file = /var/log/samba/%m.log
        max log size = 50
        printcap cache time = 60
        printcap name = cups
        dns proxy = No
        hosts allow = 192.168.1

[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.
        use client driver = Yes
        browseable = No

[print$]
        path = /var/lib/samba/printers
        write list = @adm, root
        inherit permissions = Yes
        guest ok = Yes

[pdf-gen]
        comment = PDF Generator (only valid users)
        path = /var/tmp
        printable = Yes
        printing = bsd
        print command = /usr/share/samba/scripts/print-pdf "%s" "%H" "//%L/%u" "%m" "%I" "%J" &
        lpq command = /bin/true
        lprm command = lprm -P'%p' %j

[homes]
        comment = Home Directories
        path = /home/shared
        read only = No
        guest ok = Yes
[root@localhost ~]#
client

[tom@localhost ~]$ testparm -s
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[homes]"
Processing section "[printers]"
Processing section "[print$]"
Processing section "[pdf-gen]"
Loaded services file OK.
Warning: Service printers defines a print command, but rameter is ignored when using CUPS libraries.
Server role: ROLE_STANDALONE
[global]
        workgroup = MDVGROUP
        server string = %h
        map to guest = Bad User
        log file = /var/log/samba/%m.log
        max log size = 50
        printcap cache time = 60
        printcap name = cups
        dns proxy = No

[homes]
        comment = Home Directories
        read only = No
        browseable = No

[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.
        use client driver = Yes
        browseable = No

[print$]
        path = /var/lib/samba/printers
        write list = @adm, root
        inherit permissions = Yes
        guest ok = Yes

[pdf-gen]
        comment = PDF Generator (only valid users)
        path = /var/tmp
        printable = Yes
        printing = bsd
        print command = /usr/share/samba/scripts/print-pdf "%s" "%H" "//%L/%u" "%m" "%I" "%J" &
        lpq command = /bin/true
        lprm command = lprm -P'%p' %j
[tom@localhost ~]$

[TerryN]

terry should i run "testparm -s" from server or client  tom

When trying to track down SAMBA problems it is best to start by using ONLY the machine you have configured the SERVER on.  You can run client commands on the server machine to check the setup.  That eliminates firewall/router/switch/connection problems.  Only when you have the client commands and apps successfully talking to the server on the SAME machine THEN broaden it out to other machines on the network.

       hosts allow = 192.168.1

Strictly speaking there should be a trailing dot on the end of the address to denote that you are matching a whole subnet  i.e.

       hosts allow = 192.168.1.

Try changing this and then restart SAMBA.

terry used smb://192.168.1.2/homes   . Timed out

I am not clear what the IP address of the SERVER machine is.  Your netstat output shows 192.168.1.29 but you are trying to connect to 192.168.1.2  
(also "homes" is not the name of a share but we'll come back to that later  )
Once you have made the change above and restarted SAMBA please show us the output of the following commands:

Code: [Select]

service smb status
ifconfig
smbtree -N
smbclient -L localhost

(all on the SERVER machine)


Terry.