« previous next »
Pages: [1] 2 3 4   Go Down

Author Topic: samba timeout solved  (Read 4859 times)

Offline tm

  • Full Member
  • ***
  • Posts: 154
samba timeout solved
« on: May 08, 2012, 07:01:09 AM »
Good morning to all
    A few months back in the monthly mag (the best) I found a samba tutorial .Top notch work. I set up and old system with 1TB drive and loaded minime. Followed instructions to a T. Everything loaded as shown. Went into full kde machine to look for samba share thru url and received timeout error . I increased timeout para meters but to no avail. I have a linksys router running DDWRT software. I turned off firewall to see if it would help. NG .  Both computers are running PCLinuxos and am a loss as to what to do next. Am not really line command fluent but can follow instruction.
    1)  With windows and linux machines is this my best choice of software
     2) Any suggestions of how to solve this problem
                            
                                                  tom
« Last Edit: May 15, 2012, 09:19:31 AM by tm »
Logged

Offline YouCanToo

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 5333
  • Location: Lebanon, OR., USA
    • Spreading the word.......
Re: samba timeout
« Reply #1 on: May 08, 2012, 06:38:10 PM »
Quote from: tm on May 08, 2012, 07:01:09 AM

Good morning to all
    A few months back in the monthly mag (the best) I found a samba tutorial .Top notch work. I set up and old system with 1TB drive and loaded minime. Followed instructions to a T. Everything loaded as shown. Went into full kde machine to look for samba share thru url and received timeout error . I increased timeout para meters but to no avail. I have a linksys router running DDWRT software. I turned off firewall to see if it would help. NG .  Both computers are running PCLinuxos and am a loss as to what to do next. Am not really line command fluent but can follow instruction.
    1)  With windows and linux machines is this my best choice of software
     2) Any suggestions of how to solve this problem
                             
                                                  tom

Is your Samba service actually running??

in a console window as root enter

service smb restart
Logged




Be sure to visit the NEW Knowledge Base


Linux is user-friendly- it's just picky who its friends are!

Offline tm

  • Full Member
  • ***
  • Posts: 154
Re: samba timeout
« Reply #2 on: May 09, 2012, 10:07:06 AM »
everything is running and is starting during boot,but thanks for the suggestion   tom
Logged

Offline pags

  • Hero Member
  • *****
  • Posts: 2515
  • Keep it clean.
Re: samba timeout
« Reply #3 on: May 09, 2012, 10:26:15 AM »
Are the server and client on the same LAN segment?
Logged

Offline tm

  • Full Member
  • ***
  • Posts: 154
Re: samba timeout
« Reply #4 on: May 09, 2012, 07:00:24 PM »
they are attached to the same router if that is what you mean. I was under the assumption that any computer attached to a router or its switch with the same 192.168.1 was contactable with a server
                       tom
Logged

Offline pags

  • Hero Member
  • *****
  • Posts: 2515
  • Keep it clean.
Re: samba timeout
« Reply #5 on: May 10, 2012, 06:29:53 AM »
Quote from: tm on May 09, 2012, 07:00:24 PM
they are attached to the same router if that is what you mean. I was under the assumption that any computer attached to a router or its switch with the same 192.168.1 was contactable with a server
                       tom


Yes, if the three first octects and the subnet masks are the same, on the same physical segmant, then they are on the same LAN segment.

Try this...from your Samba server:
Code: [Select]
su -c "netstat -anutp"
Supply your root password when required.  Your looking for lines that end with "smbd" and "nmbd".  They'll be listening on ports 137, 138, 139 and 445.  For example:
Quote
[jpaglia@grendel ~]$ su -c "netstat -anutp"
Password:
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address               Foreign Address             State       PID/Program name
tcp        0      0 0.0.0.0:902                 0.0.0.0:*                   LISTEN      3225/xinetd
tcp        0      0 0.0.0.0:139                 0.0.0.0:*                   LISTEN      10952/smbd
tcp        0      0 0.0.0.0:111                 0.0.0.0:*                   LISTEN      3190/portmap
tcp        0      0 0.0.0.0:22                  0.0.0.0:*                   LISTEN      31955/sshd
tcp        0      0 0.0.0.0:631                 0.0.0.0:*                   LISTEN      3437/cupsd
tcp        0      0 127.0.0.1:6010              0.0.0.0:*                   LISTEN      29215/0
tcp        0      0 0.0.0.0:37274               0.0.0.0:*                   LISTEN      3290/rpc.statd
tcp        0      0 0.0.0.0:445                 0.0.0.0:*                   LISTEN      10952/smbd
tcp        0    480 192.168.0.12:22             216.183.92.73:18087         ESTABLISHED 29199/sshd: jpaglia
tcp        0      0 :::22                       :::*                        LISTEN      31955/sshd
tcp        0      0 :::631                      :::*                        LISTEN      3437/cupsd
tcp        0      0 ::1:6010                    :::*                        LISTEN      29215/0
udp        0      0 192.168.0.12:137            0.0.0.0:*                               10962/nmbd
udp        0      0 0.0.0.0:137                 0.0.0.0:*                               10962/nmbd
udp        0      0 192.168.0.12:138            0.0.0.0:*                               10962/nmbd
udp        0      0 0.0.0.0:138                 0.0.0.0:*                               10962/nmbd
udp        0      0 0.0.0.0:922                 0.0.0.0:*                               3290/rpc.statd
udp        0      0 0.0.0.0:59452               0.0.0.0:*                               3296/avahi-daemon:
udp        0      0 0.0.0.0:5353                0.0.0.0:*                               3296/avahi-daemon:
udp        0      0 0.0.0.0:41325               0.0.0.0:*                               3290/rpc.statd
udp        0      0 0.0.0.0:111                 0.0.0.0:*                               3190/portmap
udp        0      0 0.0.0.0:631                 0.0.0.0:*                               3437/cupsd
[jpaglia@grendel ~]$


Now, from your client machine, try this:
Code: [Select]
nmap -p 137-139,445 192.168.0.12

Replace the 192.168.0.12 with the IP address of your samba server.

Your looking for "open" ports.  For example:
Quote

[jpaglia@xbmclg ~]$ nmap -p 137-139,445 192.168.0.12

Starting Nmap 5.51.3 ( http://nmap.org ) at 2012-05-10 08:32 EDT
Nmap scan report for grendel (192.168.0.12)
Host is up (0.0046s latency).
PORT    STATE  SERVICE
137/tcp closed netbios-ns
138/tcp closed netbios-dgm
139/tcp open   netbios-ssn
445/tcp open   microsoft-ds

Nmap done: 1 IP address (1 host up) scanned in 0.80 seconds
[jpaglia@xbmclg ~]$



If there are no open ports on the server (the netstat command) then the service isn't running.

If there are no open ports from the client (the nmap command) then there is a network connectivity issue.
Logged

Offline tm

  • Full Member
  • ***
  • Posts: 154
Re: samba timeout
« Reply #6 on: May 10, 2012, 07:42:12 AM »
thanks I will give it a try and report back
                         tom
Logged

Offline tm

  • Full Member
  • ***
  • Posts: 154
Re: samba timeout
« Reply #7 on: May 10, 2012, 07:54:43 AM »
did as you suggested and outputs are the same as yours. I will verify that the ip's are correct but i am pretty sure they are. verified ip addresses . Thanks Will try some things till I hear from you pags   tom
 
« Last Edit: May 10, 2012, 08:04:42 AM by tm »
Logged

Offline tm

  • Full Member
  • ***
  • Posts: 154
Re: samba timeout
« Reply #8 on: May 10, 2012, 08:43:10 AM »
If both computers are listening to the correct ports even though they can both go online  is it reasonable to assume there is some type of router,switch or cable problem or am I just reaching for straws
                            tom
Logged

Offline pags

  • Hero Member
  • *****
  • Posts: 2515
  • Keep it clean.
Re: samba timeout
« Reply #9 on: May 10, 2012, 09:31:03 AM »
Quote from: tm on May 10, 2012, 08:43:10 AM
If both computers are listening to the correct ports even though they can both go online  is it reasonable to assume there is some type of router,switch or cable problem or am I just reaching for straws
                            tom

Only the server needs to be LISTENING.  That is why I had you run the "netstat" command on the server.  The client wants to "talk" to the server...that is what the "nmap" command shows us.

Do you mind posting the commands and their output?

...and, yes, a router/switch/cable between the two devices can definately cause an issue...
Logged

Offline TerryN

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 723
Re: samba timeout
« Reply #10 on: May 10, 2012, 11:57:08 AM »
In addition to any other info, please check the output from the following command on both machines:

Code: [Select]
smbtree -N
Also can you please clarify what you mean by

Quote from: tm on May 08, 2012, 07:01:09 AM
Went into full kde machine to look for samba share thru url and received timeout error.

Into what application were you entering the URL and what was the format of that URL?

Terry.
Logged
Dell E521 - AMD 64 X2 5000+, 4GB RAM, ATI X1300 graphics
PCLinuxOS 2013 (KDE)
|Twitter|

Offline tm

  • Full Member
  • ***
  • Posts: 154
Re: samba timeout
« Reply #11 on: May 11, 2012, 08:10:12 AM »
this is from server
root@localhost ~]# su -c "netstat -anutp"
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address               Foreign Address             State       PID/Program name  
tcp        0      0 192.168.1.29:58850          206.111.15.87:443           ESTABLISHED 2795/chrome        
tcp        0      0 192.168.1.29:33270          74.125.134.102:80           ESTABLISHED 2795/chrome        
tcp        0      0 :::445                      :::*                        LISTEN      2357/smbd          
tcp        0      0 :::139                      :::*                        LISTEN      2357/smbd          
udp        0      0 0.0.0.0:40107               0.0.0.0:*                               2131/dhclient      
udp        0      0 0.0.0.0:5353                0.0.0.0:*                               2295/avahi-daemon:  
udp        0      0 0.0.0.0:55738               0.0.0.0:*                               2295/avahi-daemon:  
udp        0      0 0.0.0.0:68                  0.0.0.0:*                               2131/dhclient
udp        0      0 192.168.1.29:123            0.0.0.0:*                               2382/ntpd
udp        0      0 127.0.0.1:123               0.0.0.0:*                               2382/ntpd
udp        0      0 0.0.0.0:123                 0.0.0.0:*                               2382/ntpd
udp        0      0 192.168.1.255:137           0.0.0.0:*                               2365/nmbd
udp        0      0 192.168.1.29:137            0.0.0.0:*                               2365/nmbd
udp        0      0 0.0.0.0:137                 0.0.0.0:*                               2365/nmbd
udp        0      0 192.168.1.255:138           0.0.0.0:*                               2365/nmbd
udp        0      0 192.168.1.29:138            0.0.0.0:*                               2365/nmbd
udp        0      0 0.0.0.0:138                 0.0.0.0:*                               2365/nmbd
udp        0      0 :::40962                    :::*                                    2131/dhclient
udp        0      0 ::1:123                     :::*                                    2382/ntpd
udp        0      0 fe80::211:d8ff:fe98:123     :::*                                    2382/ntpd
udp        0      0 :::123                      :::*                                    2382/ntpd
this is from client

Starting Nmap 5.51.3 ( http://nmap.org ) at 2012-05-11 10:17 EDT
Nmap scan report for 192.168.1.2
Host is up (0.00031s latency).
PORT    STATE  SERVICE
137/tcp closed netbios-ns
138/tcp closed netbios-dgm
139/tcp open   netbios-ssn
445/tcp open   microsoft-ds
there is no output to smbtree -N on both machines
« Last Edit: May 11, 2012, 08:21:15 AM by tm »
Logged

Offline tm

  • Full Member
  • ***
  • Posts: 154
Re: samba timeout
« Reply #12 on: May 11, 2012, 08:24:56 AM »
Terry
   I am using Konqueror as per instructed and url is
   smb://samba-server/homes
                                                             tom
     
Logged

Offline tm

  • Full Member
  • ***
  • Posts: 154
Re: samba timeout
« Reply #13 on: May 11, 2012, 08:32:53 AM »
pags update

[tom@localhost ~]$ smbtree -N
failed negprot: NT_STATUS_INVALID_NETWORK_RESPONSE
failed negprot: NT_STATUS_INVALID_NETWORK_RESPONSE
[tom@localhost ~]$
this is from client
server is the same . this is appearing to me to be a router issue does the data concur  tom
Logged

Offline pags

  • Hero Member
  • *****
  • Posts: 2515
  • Keep it clean.
Re: samba timeout
« Reply #14 on: May 11, 2012, 08:46:29 AM »
Quote from: tm on May 11, 2012, 08:10:12 AM
this is from server
Quote
root@localhost ~]# su -c "netstat -anutp"
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address               Foreign Address             State       PID/Program name  
tcp        0      0 192.168.1.29:58850          206.111.15.87:443           ESTABLISHED 2795/chrome        
tcp        0      0 192.168.1.29:33270          74.125.134.102:80           ESTABLISHED 2795/chrome        
tcp        0      0 :::445                      :::*                        LISTEN      2357/smbd          
tcp        0      0 :::139                      :::*                        LISTEN      2357/smbd          
udp        0      0 0.0.0.0:40107               0.0.0.0:*                               2131/dhclient      
udp        0      0 0.0.0.0:5353                0.0.0.0:*                               2295/avahi-daemon:  
udp        0      0 0.0.0.0:55738               0.0.0.0:*                               2295/avahi-daemon:  
udp        0      0 0.0.0.0:68                  0.0.0.0:*                               2131/dhclient
udp        0      0 192.168.1.29:123            0.0.0.0:*                               2382/ntpd
udp        0      0 127.0.0.1:123               0.0.0.0:*                               2382/ntpd
udp        0      0 0.0.0.0:123                 0.0.0.0:*                               2382/ntpd
udp        0      0 192.168.1.255:137           0.0.0.0:*                               2365/nmbd
udp        0      0 192.168.1.29:137            0.0.0.0:*                               2365/nmbd
udp        0      0 0.0.0.0:137                 0.0.0.0:*                               2365/nmbd
udp        0      0 192.168.1.255:138           0.0.0.0:*                               2365/nmbd
udp        0      0 192.168.1.29:138            0.0.0.0:*                               2365/nmbd
udp        0      0 0.0.0.0:138                 0.0.0.0:*                               2365/nmbd
udp        0      0 :::40962                    :::*                                    2131/dhclient
udp        0      0 ::1:123                     :::*                                    2382/ntpd
udp        0      0 fe80::211:d8ff:fe98:123     :::*                                    2382/ntpd
udp        0      0 :::123                      :::*                                    2382/ntpd


this is from client

Quote
Starting Nmap 5.51.3 ( http://nmap.org ) at 2012-05-11 10:17 EDT
Nmap scan report for 192.168.1.2
Host is up (0.00031s latency).
PORT    STATE  SERVICE
137/tcp closed netbios-ns
138/tcp closed netbios-dgm
139/tcp open   netbios-ssn
445/tcp open   microsoft-ds
there is no output to smbtree -N on both machines



Is there a discrepancy of the IPs you're using?

On the server, it appears to have an IP of 192.168.1.29, but from the client, you're scanning 192.168.1.2 ... is that just a typo, or did you scan the wrong system?

With regards to this:
Quote from: tm on May 11, 2012, 08:24:56 AM

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
     
Logged
Pages: [1] 2 3 4   Go Up
« previous next »