Ubuntu 13.04 file sharing with other Ubuntu Computers

[AgentZ86]

I'm getting time outs

I have the default install of 13.04 on 2 machines, and 1 machines is 12.04, and the other is Windows 7
My main share is on a ubuntu 13.04 folder lets call this one MAIN for description purposes.

Ubuntu - Right click share options, share with read/write and guest access with default WORKGROUP name.
Windows 7 box same setup WORKGROUP name

All the computers on the router have a shared folder setup for sharing requirements mostly

I cannot access the MAIN share on the MAIN box itself from the network browser, nor from the other ubuntu computers
Oddly the Windows computer can access the MAIN share

I get time out from the ubuntu computers or from the MAIN itself when accessing the network browser

However, the other 2 Ubuntu computers can access their shared folders among themselves
This is very strange and I have not experienced this before.

Please advise

[redmk2]

From the "network browser" try using cntl+l to get a location bar. Then use this to connect: smb://IP_ADDRESS (use the IP address of the MAIN machine). Does this show the share?

[AgentZ86]

From the "network browser" try using cntl+l to get a location bar. Then use this to connect: smb://IP_ADDRESS (use the IP address of the MAIN machine). Does this show the share?

Yes it does
All shares seem to work normally with smb//IP's
Why is it doing that and how to fix it ?

Thanks for the replies

[redmk2]

Yes it does
All shares seem to work normally with smb//IP's
Why is it doing that and how to fix it ?

Thanks for the replies

This confirms that the Samba daemon (smbd) is working correctly. The name service (nmbd) is not resolving the name to IP. There are several things that can be the culprit. We need to dig some more using the CLI.

From the terminal of the server you call Main post the output of this command

hostname

Also post the output of

cat /etc/hosts

.

is the this machine's IP address static (stays the same)? What is the address? What is the output of this command

ifconfig

[HiImTye]

are you using ufw? if so try adding the following rules

sudo ufw allow from 192.168.0.0/24 to any port 137:139,445 proto tcp
sudo ufw allow from 192.168.0.0/24 to any port 137:139,445 proto udp

substituting the ip range of your network if necessary.

[redmk2]

are you using ufw? if so try adding the following rules

sudo ufw allow from 192.168.0.0/24 to any port 137:139,445 proto tcp
sudo ufw allow from 192.168.0.0/24 to any port 137:139,445 proto udp

substituting the ip range of your network if necessary.

Samba works. There is no need to diddle with the FW at all. See "All shares seem to work normally with smb//IP's" from above.

[HermanAB]

Howdy,

Samba works best if you have a DNS server for your LAN, or at least have all hostnames and IP addresses defined in all /etc/hosts files. Delays are usually due to bad name lookups, forcing Samba to try different methods to resolve things.

[HiImTye]

ignore this

[AgentZ86]

Couldn't do this last night but anyhow here is the outpu

hostname
warehouse-GX617AA-ABA-SR5310F
warehouse@warehouse-GX617AA-ABA-SR5310F:~$


cat /etc/hosts
127.0.0.1 localhost
127.0.1.1 warehouse-GX617AA-ABA-SR5310F

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

ifconfig
eth0 Link encap:Ethernet HWaddr 00:1d:60:d1:7f:4a
inet addr:192.168.1.8 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21d:60ff:fed1:7f4a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:133018 errors:0 dropped:0 overruns:0 frame:0
TX packets:71923 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:131522567 (131.5 MB) TX bytes:24235895 (24.2 MB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:6393 errors:0 dropped:0 overruns:0 frame:0
TX packets:6393 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:598515 (598.5 KB) TX bytes:598515 (598.5 KB)

Look like the other ubuntu boxes

I should mention one thing that may not be related

If I turn off the computer that has the MAIN share on it, the other 2 ubuntu boxes can share among themself more easily without delays.
Just thought I should mention it

[redmk2]

Couldn't do this last night but anyhow here is the output

hostname
warehouse-GX617AA-ABA-SR5310F
warehouse@warehouse-GX617AA-ABA-SR5310F:~$

cat /etc/hosts
127.0.0.1	localhost
127.0.1.1	warehouse-GX617AA-ABA-SR5310F

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

ifconfig
eth0      Link encap:Ethernet  HWaddr 00:1d:60:d1:7f:4a  
          inet addr:192.168.1.8  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::21d:60ff:fed1:7f4a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:133018 errors:0 dropped:0 overruns:0 frame:0
          TX packets:71923 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:131522567 (131.5 MB)  TX bytes:24235895 (24.2 MB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:6393 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6393 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:598515 (598.5 KB)  TX bytes:598515 (598.5 KB)

Look like the other ubuntu boxes

I should mention one thing that may not be related

If I turn off the computer that has the MAIN share on it, the other 2 ubuntu boxes can share among themself more easily without delays.
Just thought I should mention it

The host with the MAIN share is the problem for sure. The first thing I see is the hostname is longer than 15 characters. NETBIOS names must be less than 15 characters. We need to change that. There are 2 ways to do that. We can change the hostname itself or we can explicitly configure a suitable NETBIOS name in the smb.conf file. The second method is the easiest, but the name you browse for will not be the same as the hostname.

There may be other problems, but this is definitely a problem that needs to be resolved (pardon the pun).