Timeouts trying to browse Windows Compatible Member Server


#1

I can’t browse shares on a Windows Compatible Member Server.

From a windows machine,

  • net view domain controller - works
  • net view fileserver - gives ‘System error 53 has occoured . The network path was not found’
  • ping from both the DC and the Windows PC to the fileserver works

More info:
The file server’s name is plato (192.168.20.20)
The Domain master is called phobos (192.168.20.3)

root@phobos:/home/talcom# smbclient -U talcom -L plato
Enter ENVIRO\talcom's password: 
session setup failed: NT_STATUS_IO_TIMEOUT

root@plato:/home/talcom# systemctl status smbd.service 
● smbd.service - LSB: Samba SMB/CIFS daemon (smbd)
   Loaded: loaded (/etc/init.d/smbd; generated; vendor preset: enabled)
   Active: active (running) since Sat 2018-05-19 03:30:22 AEST; 7h left

root@plato:/home/talcom# nmap 192.168.20.20
Starting Nmap 7.40 ( https://nmap.org ) at 2018-05-18 19:40 AEST
Nmap scan report for plato.enviro.intranet (192.168.20.20)
Host is up (0.000022s latency).
Not shown: 991 closed ports
PORT      STATE SERVICE
22/tcp    open  ssh
80/tcp    open  http
111/tcp   open  rpcbind
139/tcp   open  netbios-ssn
443/tcp   open  https
445/tcp   open  microsoft-ds
2049/tcp  open  nfs
5666/tcp  open  nrpe
32768/tcp open  filenet-tms

I would appreciate some tips to try to troubleshoot this


#2

Hey,

which UCS version are you running on that member server? Please post the output of ucr search --brief version.

Kind regards,
mosu


#3

(I first posted the wrong servers out. this post has been corrected)

Thanks Moritz

root@plato:/home/talcom# ucr search --brief version
appcenter/apps/samba-memberserver/version: 4.7
repository/mirror/version/end: <empty>
repository/mirror/version/start: <empty>
repository/online/component/.*/version: <empty>
repository/online/component/4.3-0-errata/version: 4.3
update/umc/nextversion: true
version/erratalevel: 83
version/patchlevel: 0
version/releasename: Neustadt
version/version: 4.3

#4

This problem has fixed itself in the last 12 hours!
Unfortunately I don’t really know why.
It may have been related to cleanups I was doing with S4 connector errors and orphaned DNS records.