On Thu, 07 Jan 2016 14:33:29 +0100, Richard PALO wrote:
Le 07/01/16 09:11, Jonathan Adams a écrit :
Quick question, if I may.

What happens if you do a "getent <host>" for the affected remote?

Jon

Well, as of now it looks like :
richard@omnis:/home/richard$ getent hosts
127.0.0.1       localhost loghost omnis
192.168.0.6     omnis-e1000g0
192.168.0.7     omnis-e1000g1
plus a few more

originally, I had the nodename on the 192.168.0.6  address
and had omitted configuring the second nic. Made no difference to `smbutil 
status' though.

I still get the following mDNSResponder sort of errors on reboot:
Jan  7 14:14:53 omnis mDNSResponder: [ID 702911 daemon.error] mDNSResponder 
(Engineering Build) (Dec  4 2015 09:35:14) starting
Jan  7 14:14:53 omnis mDNSResponder: [ID 702911 daemon.error] 
mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
Jan  7 14:14:53 omnis mDNSResponder: [ID 702911 daemon.error] 
mDNSPlatformSourceAddrForDest: connect 1.1.1.1 failed errno 128 (Network is 
unreachable)
Jan  7 14:14:54 omnis mDNSResponder (Engineering Build) [621]: [ID 702911 
daemon.info] starting
Jan  7 14:14:54 omnis smbd[653]: [ID 231464 daemon.debug] upgrade: smb2_enable 
not found
Jan  7 14:14:54 omnis smbd[653]: [ID 243688 daemon.debug] smb_ddiscover_service 
waiting
Jan  7 14:14:54 omnis mDNSResponder: [ID 702911 daemon.error] Local Hostname 
omnis.local already in use; will try omnis-2.local instead
Jan  7 14:14:55 omnis mDNSResponder: [ID 702911 daemon.error] 
mDNSCoreReceiveResponse: Received from 192.168.0.6:5353   15 
6.0.168.192.in-addr.arpa. PTR omnis-2.local.
Jan  7 14:14:55 omnis mDNSResponder: [ID 702911 daemon.error] 
mDNSCoreReceiveResponse: Unexpected conflict discarding   13 
6.0.168.192.in-addr.arpa. PTR omnis.local.
Jan  7 14:15:04 omnis smbd[653]: [ID 646321 daemon.debug] 
smbd_localtime_monitor: online
Is there something special to do to clean up any caches?
btw, what are the 'mDNSPlatformSourceAddrForDest' and 'smb2_enable' messages?  
Looks like they may be important..

smb2_enable one isn't, we first introduced the smb2_enable option, which was then changed to max_protocol, and smbd simply checks if smb2_enable exists to convert it.


-------------------------------------------
illumos-discuss
Archives: https://www.listbox.com/member/archive/182180/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4
Powered by Listbox: http://www.listbox.com

Reply via email to