May 13, 201511 yr The Problem -Can't access SMB share from Finder on Max OS X 10 -Error Message: There was a problem connecting to the server "Tower". The server may not exist or it is unavailable at this time. Check the server name or IP address, check your network connection, and try again. Steps Leading Up to the Problem -Previously was using UnRaid v5.06 trial. Filled my 2nd data drive so Pro key it is. -Might as well "update" to v6.0b, formatted flash & loaded v6.0b & Pro.key to it -SMB was working fine on same drive each time -Started & finished transferring in data from a 4 TB network drive -Shutdown etc to insert freshly precleared 6 TB WD Red -Now unable to get SMB working. No apparent errors from UnRaid server. Always get these errors in Finder http://i.imgur.com/c7LeKxK.jpg http://i.imgur.com/AsfxSFY.png -Next drive (2 TB) was NTFS-formatted, so I shutdown/etc and mounted with SNAP -Still unable to get SMB working. Same deal -Did internal copy via SNAP -Shutdown/etc to remove 2 TB drive, start up, nothing. -All sorts of SMB/NFS/AFP configuration attempts. -Currently AFP is working, but I can't see individual drives. Just the Share as a whole. Is this a bug/feature of AFP? Attempted Solutions -Connect via root/(blank), test user test/testa, Mac OS X username/password (registered user) -smb://Tower/ -smb://Tower/Media -smb://192.168.1.100 -smb://192.168.1.100/Media System Specs -Note that my Win8 and UnRaid are all on the same physical machine, I interrupt the boot process depending which one I need at the time. Intel i7 3770 3.4 Ghz Gigabyte GA-Z77-DS3H rev1.0 16 GB Patriot 1600 Mhz Nvidia GeForce GTX 670 120 GB Samsung 840 Pro SSD (Win8 OS) 1.5 TB WD Green (Win8 Docs & Programs) 250 GB WD Blue (Spare drive, not currently installed) 250 GB WD Green (Xenserver, not currently installed) * 4 TB WD Green (UnRaid disk1) 4 TB WD Green (UnRaid disk2) 4 TB WD Green (UnRaid disk3) 6 TB WD Red (UnRaid disk4) 4 TB WD Green (UnRaid disk5) *note this drive is weird. 3-4 years ago I was trying to format the 250 GB WD Blue above for my old Xbox and selected this drive by mistake. It physically has 2 TB of storage, but the program I used really, really messed the drive up at a super low level, so it now only reports as 250 GB. No amount of wiping, partitioning, new volumes, etc has fixed it. The IT guy at my old internship was even stumped. Shouldn't matter here, but full disclosure I guess. More Info to Provide ifconfig eth0 eth0 flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.100 netmask 255.255.255.0 broadcast 192.168.1.255 ether [mobo MAC addr] txqueuelen 1000 (Ethernet) RX packets 399089 bytes 48918371 (46.6MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 228648 butes 43991860 (41.9MiB) TX errors 0 dropped 0 overruns 0 carrier 1 collisions 0 Ping Results [Mac name]:~ [username]$ ping 192.168.1.100 PING 192.168.1.100 (192.168.1.100): 56 data bytes 64 bytes from 192.168.1.100: icmp_seq=0 ttl=64 time=118.977 ms 64 bytes from 192.168.1.100: icmp_seq=1 ttl=64 time=3.677 ms 64 bytes from 192.168.1.100: icmp_seq=2 ttl=64 time=3.427 ms 64 bytes from 192.168.1.100: icmp_seq=3 ttl=64 time=3.462 ms 64 bytes from 192.168.1.100: icmp_seq=4 ttl=64 time=3.464 ms 64 bytes from 192.168.1.100: icmp_seq=5 ttl=64 time=3.406 ms 64 bytes from 192.168.1.100: icmp_seq=6 ttl=64 time=3.444 ms 64 bytes from 192.168.1.100: icmp_seq=7 ttl=64 time=3.090 ms 64 bytes from 192.168.1.100: icmp_seq=8 ttl=64 time=3.453 ms 64 bytes from 192.168.1.100: icmp_seq=9 ttl=64 time=3.432 ms 64 bytes from 192.168.1.100: icmp_seq=10 ttl=64 time=3.423 ms ^C --- 192.168.1.100 ping statistics --- 11 packets transmitted, 11 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 3.090/13.932/118.977/33.218 ms syslog.txt
May 13, 201511 yr Community Expert If you were trying with Windows I would suggest Under SMB Settings: Make sure unRAID and PC are on same workgroup. Set unRAID to be Local master Delete any unRAID entries in Credential Manager so they can be recreated. Maybe this is the same as Keychain on Mac?
Archived
This topic is now archived and is closed to further replies.