I'm experiencing the same problem here. This just started happening within the last week or so.
I have 2 jails. One for deluge/flexget and another for emby server. I've been running these for a few months and never had any issues until recently. If I stop both jails then time machine backups work as they should. With the jails running , automatic backups do not work. I also am having issues connecting to CIFS shares on freenas as well. I get the same message "connection failed". If I stop the jails then everything works as it should.
There is definitely something up with jails and mdns/zeroconf.
UPDATE: Did a clean install of FreeNAS-9.3-STABLE-201503270027 and now time machine and cifs works when jails are running. I'll stay with this version until either I or someone else can figure out what exactly is going on and submit a bug report. I did some watching in wireshark and saw my mac send out a mdns query but it never gets a reply back when 1 or more jails are running. It doesn't matter which jail it is either.
UPDATE 2: It seems the problem is back even on 201503270027. I need to have all of my jails stopped before AFP or CIFS can connect from the finder. When any or all jails are running I am seeing some interesting behavior with tcpdump running on freenas. When I have connection problems I am seeing this:
IP truncated-ip - 31855 bytes missing! 10.1.1.20.mdns > 224.0.0.251.mdns: 0*- [0q] 1/0/3 (Cache flush) SRV freenas.local.:445 0 0 (31972)
10.1.1.20 is my freenas box. I was trying to browse my cifs shares in finder when I got that. Eventually I got "Connection failed" in finder.
I have 2 jails. One for deluge/flexget and another for emby server. I've been running these for a few months and never had any issues until recently. If I stop both jails then time machine backups work as they should. With the jails running , automatic backups do not work. I also am having issues connecting to CIFS shares on freenas as well. I get the same message "connection failed". If I stop the jails then everything works as it should.
There is definitely something up with jails and mdns/zeroconf.
UPDATE: Did a clean install of FreeNAS-9.3-STABLE-201503270027 and now time machine and cifs works when jails are running. I'll stay with this version until either I or someone else can figure out what exactly is going on and submit a bug report. I did some watching in wireshark and saw my mac send out a mdns query but it never gets a reply back when 1 or more jails are running. It doesn't matter which jail it is either.
UPDATE 2: It seems the problem is back even on 201503270027. I need to have all of my jails stopped before AFP or CIFS can connect from the finder. When any or all jails are running I am seeing some interesting behavior with tcpdump running on freenas. When I have connection problems I am seeing this:
IP truncated-ip - 31855 bytes missing! 10.1.1.20.mdns > 224.0.0.251.mdns: 0*- [0q] 1/0/3 (Cache flush) SRV freenas.local.:445 0 0 (31972)
10.1.1.20 is my freenas box. I was trying to browse my cifs shares in finder when I got that. Eventually I got "Connection failed" in finder.
Last edited: