Resolving Host/System name

[netcompsys]

I have just completed a first time install followed by an upgrade on a RPi B+ with an added 1 TB USB disc

I have set the name to PiNAS and the ip address is fixed to 192.168.253.220 (192.168.253.x being my net) which is outside the DHCP servers range.

I have set up a number of SAMBA shares, Photos, Music etc as Public with no username/pwd

The Rpi does not appear in Windows explorer as PiNAS as I expect, but I can access shares and copy files fine if I use the ip address, eg \\192.168.253.220\music

If I go to the command prompt and ping the RPi using the System name then it is resolved satisfactorily

Clearly some sort of name resolution issue, but as a complete linux beginner, any pointers or suggestions would be welcome

cheers
kevin

[uelpenich]

Hi Kevin,

The Rpi does not appear in Windows explorer as PiNAS as I expect, . . .

Seems to be a Windows problem. Some of my WinPCs have the same problem, others not.
I suppose a WINS server or Netbios problem.

Werner

[netcompsys]

I have used the old trick of editing the hosts file on the PC to add the ip address and host name, this allows me to use the host name in that PC's browser address bar and to map a network drive using the name, but the NAS is not appearing as a network device in explorer so i can't easily browse the available shares, so is it not making its name known on the LAN?

kevin

[Jocko]

Hi netcompsys,

I am pretty sure that you did not set the workgroup in the LAN menu:

See : viewtopic.php?f=5&t=2041&p=17023&hilit=workgroup#p17023

[netcompsys]

Thanks for your suggestion

The default Workgroup is mshome but I did change it to workgroup to match my network and then rebooted as part of the original install/setup process

Kevin

[Jocko]

:scratch
Now, It is Ok ?

[netcompsys]

No the problem still exists, the host name is not being resolved by windows. It is not clear to me still if this a problem with the NAS operating system or with windows

as I said before I can ping the NAS host from a command window and this does resolve the name to the address

editing the hosts file allows me to use the hostname in the address bar of explorer and the browser, eg \\PINAS\music but I cannot see the NAS in the networks section of explorer and so cannot browse the shares

I have tried reverting both the windows PC and the NAS to workgroup MSHOME and restarting both but this has not resolved the problem

kevin

[Jocko]

Hi netcompsys,

I assume that you use windows.

So check if computer browser service is running.

[netcompsys]

Yes indeed, Windows 8.1 x2 and Windows 7

Computer Browser Service is running

The 3 windows PC's have no problems seeing each other or my WD MyCloud NAS box

thanks
kevin

[netcompsys]

Stumbling around following a few diagnostic threads elsewhere on the net

Code: Select all

root@PiNAS:/ # ping pinas
PING pinas (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: seq=0 ttl=64 time=0.407 ms
64 bytes from 127.0.0.1: seq=1 ttl=64 time=0.299 ms
64 bytes from 127.0.0.1: seq=2 ttl=64 time=0.302 ms
64 bytes from 127.0.0.1: seq=3 ttl=64 time=0.303 ms
64 bytes from 127.0.0.1: seq=4 ttl=64 time=0.293 ms
64 bytes from 127.0.0.1: seq=5 ttl=64 time=0.301 ms
64 bytes from 127.0.0.1: seq=6 ttl=64 time=0.297 ms
64 bytes from 127.0.0.1: seq=7 ttl=64 time=0.295 ms
64 bytes from 127.0.0.1: seq=8 ttl=64 time=0.301 ms
64 bytes from 127.0.0.1: seq=9 ttl=64 time=0.295 ms
64 bytes from 127.0.0.1: seq=10 ttl=64 time=0.294 ms
64 bytes from 127.0.0.1: seq=11 ttl=64 time=0.297 ms
64 bytes from 127.0.0.1: seq=12 ttl=64 time=0.302 ms
64 bytes from 127.0.0.1: seq=13 ttl=64 time=0.301 ms
64 bytes from 127.0.0.1: seq=14 ttl=64 time=0.297 ms
^C
--- pinas ping statistics ---
15 packets transmitted, 15 packets received, 0% packet loss
round-trip min/avg/max = 0.293/0.305/0.407 ms

root@PiNAS:/ # nmbd -V
Version 3.0.37

root@PiNAS:/ # ps -ef | grep nmbd
root       633     1  0 16:28 ?        00:00:00 /usr/sbin/nmbd -D -l /var/log/samba
root      1140  1113  0 20:20 pts/0    00:00:00 grep nmbd

root@PiNAS:/ # ps -ef | grep smbd
root       636     1  0 16:28 ?        00:00:00 /usr/sbin/smbd -D -l /var/log/samba
root       637   636  0 16:28 ?        00:00:00 /usr/sbin/smbd -D -l /var/log/samba
root      1024   636  0 19:21 ?        00:00:06 /usr/sbin/smbd -D -l /var/log/samba
root      1170  1113  0 20:28 pts/0    00:00:00 grep smbd

root@PiNAS:/ # ps -ef | grep nmbd
root       633     1  0 16:28 ?        00:00:00 /usr/sbin/nmbd -D -l /var/log/samba
root      1175  1113  0 20:28 pts/0    00:00:00 grep nmbd

root@PiNAS:/ # nmblookup -B pinas __SAMBA__
querying __SAMBA__ on 127.0.0.1
192.168.253.220 __SAMBA__<00>

root@PiNAS:/ # ls /var/log/samba
cores  log.nmbd  log.smbd

root@PiNAS:/ # tail /var/log/samba/log.nmbd
[2011/11/16 12:00:20, 0] nmbd/nmbd.c:main(723)
  Netbios nameserver version 3.0.37 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009

root@PiNAS:/ # tail /var/log/samba/log.smbd
[2015/02/26 17:56:38, 0] lib/util_sock.c:read_data(534)
  read_data: read failure for 4 bytes to client 192.168.253.114. Error = Connection reset by peer
[2015/02/26 18:28:49, 0] lib/util_sock.c:read_data(534)
  read_data: read failure for 4 bytes to client 192.168.253.114. Error = Connection reset by peer
[2015/02/26 19:00:55, 0] lib/util_sock.c:read_data(534)
  read_data: read failure for 4 bytes to client 192.168.253.114. Error = Connection reset by peer
[2015/02/26 19:33:01, 0] lib/util_sock.c:read_data(534)
  read_data: read failure for 4 bytes to client 192.168.253.114. Error = Connection reset by peer
[2015/02/26 20:05:13, 0] lib/util_sock.c:read_data(534)
  read_data: read failure for 4 bytes to client 192.168.253.114. Error = Connection reset by peer
root@PiNAS:/ #


As a complete beginner in linux but reading these threads, all seems ok in the results above so far...

kevin