I have three computers: one dual booting MacBook Pro, one dual booting Hackintosh and one Linux/Windows server. You might already object to my claim on the basis that one of them is not an official Mac, but it is also a proper Windows machine and both of them show the exact same errors and symptoms, so bear with me. For other Hackintoshers, the LAN chip in my build is the Intel I217-V running on hnak's E100e kext.
The newest Yosemite version has broken support for Windows-hosted SMB networking in many levels. I have isolated this to Yosemite and Yosemite only through testing with multiple operating systems combinations on all three machines.
The current setup has Windows 8.1 on the server, serving SMB fileshares and networked local printers as well as an LPD spool for Unix printing, and Yosemite/Windows 8.1 on both MBP and Hackintosh (for the purpose of the article we will refer to this as the Hack). The server connects to local networks via LAN as well as a USB 802.11n dongle; it is of note that it can only advertise the NetBIOS name through LAN due to frequency limitations on the dongle, and any wireless testing was done through IP address locations.
Booting into Windows 8.1 on either Mac or Hack results in a perfectly operable SMB share, with fileshare as well as network printer support, on both Wi-Fi and LAN. Both machines are able to connect to the server by its NetBIOS name on LAN and print through SMB.
On Yosemite, however, both machines are unable to connect to any NetBIOS server. This is not limited to my server only; the rest of my LAN is pretty much Windows 8.1 and none of them are able to network to the Yosemite machines. Specifying a direct IP address on the LAN connection enables SMB filesharing access, and an unstable one at that; large file transfers tend to crash the connection very easily on both Mac and Hack. Once the SMB share crashes, it apparently brings down every connection to the server, as it also crashes the RDP connection.
LAN SMB printing is even worse. The Windows menu on the printer setup page shows the workgroup and all associated printers including my server, but is unable to connect to any of them with the following message:
Manually adding it through the Advanced menu accessible by holding down the Control key allows me to specify a direct IP address to the printer. It was only through this that I was able to add the printer to the menu. Printing is another story, however, as although it was able to connect, any print job that got sent was received by the spooler on the Windows side, marked as "finished" or simply disappeared, and nothing came from the printer. Compare this to the Windows 8.1 client which was able to completely manage the entire printer right down to the ink levels.
I also mentioned that LPD was enabled for the Windows server. That was utterly useless for Yosemite; the printer setup does not see any LPD connection even when specified an IP address, never mind connecting to and printing from it.
What is even more troubling is that this seems not to be limited to my server. The college dorm I'm in has many, many computers on its LAN as you can imagine, with most computers being Windows 8.1 based. Yosemite is unable to connect to ANY of them; it does not even prompt for a login unless forced via manual IP address entry for fileshares. Printing does not work period.
The fact that this server was originally a Linux-based one is also very interesting. I was forced to switch to Windows after shoddy support for Linux from Highpoint, a RAID card manufacturer. Before I made the switch, however, I was able to do some testing with samba, the Linux port of SMB. It also supports file sharing and printer networking. On both Mac and Hack, on both Yosemite and Windows, the Linux-hosted SMB fileshares and printers worked without any issue.
I point this out because from what I know, samba is based on SMB1/CIFS, while Windows and Yosemite use SMB 3, a newer version of the protocol. Perhaps this is the repeat of the SMB 2 fiasco on Mavericks.
I have been testing Yosemite since its early previews. It has had its share of bugs but this one seems to be unique to the public release builds only as SMB was working fine on previous builds of Yosemite.
Any information and suggestion on how to fix this would be greatly appreciated. I will do some more testing with fallback to CIFS for printing in the interim.
UPDATE: CIFS printing is not supported as you cannot add a printer using cifs://.
The newest Yosemite version has broken support for Windows-hosted SMB networking in many levels. I have isolated this to Yosemite and Yosemite only through testing with multiple operating systems combinations on all three machines.
The current setup has Windows 8.1 on the server, serving SMB fileshares and networked local printers as well as an LPD spool for Unix printing, and Yosemite/Windows 8.1 on both MBP and Hackintosh (for the purpose of the article we will refer to this as the Hack). The server connects to local networks via LAN as well as a USB 802.11n dongle; it is of note that it can only advertise the NetBIOS name through LAN due to frequency limitations on the dongle, and any wireless testing was done through IP address locations.
Booting into Windows 8.1 on either Mac or Hack results in a perfectly operable SMB share, with fileshare as well as network printer support, on both Wi-Fi and LAN. Both machines are able to connect to the server by its NetBIOS name on LAN and print through SMB.
On Yosemite, however, both machines are unable to connect to any NetBIOS server. This is not limited to my server only; the rest of my LAN is pretty much Windows 8.1 and none of them are able to network to the Yosemite machines. Specifying a direct IP address on the LAN connection enables SMB filesharing access, and an unstable one at that; large file transfers tend to crash the connection very easily on both Mac and Hack. Once the SMB share crashes, it apparently brings down every connection to the server, as it also crashes the RDP connection.
LAN SMB printing is even worse. The Windows menu on the printer setup page shows the workgroup and all associated printers including my server, but is unable to connect to any of them with the following message:
Code:
10/22/14 7:00:54.845 PM sharingd[757]: 19:00:54.844 : SDSharePointBrowser::handleOpenCallBack returned 65Manually adding it through the Advanced menu accessible by holding down the Control key allows me to specify a direct IP address to the printer. It was only through this that I was able to add the printer to the menu. Printing is another story, however, as although it was able to connect, any print job that got sent was received by the spooler on the Windows side, marked as "finished" or simply disappeared, and nothing came from the printer. Compare this to the Windows 8.1 client which was able to completely manage the entire printer right down to the ink levels.
I also mentioned that LPD was enabled for the Windows server. That was utterly useless for Yosemite; the printer setup does not see any LPD connection even when specified an IP address, never mind connecting to and printing from it.
What is even more troubling is that this seems not to be limited to my server. The college dorm I'm in has many, many computers on its LAN as you can imagine, with most computers being Windows 8.1 based. Yosemite is unable to connect to ANY of them; it does not even prompt for a login unless forced via manual IP address entry for fileshares. Printing does not work period.
The fact that this server was originally a Linux-based one is also very interesting. I was forced to switch to Windows after shoddy support for Linux from Highpoint, a RAID card manufacturer. Before I made the switch, however, I was able to do some testing with samba, the Linux port of SMB. It also supports file sharing and printer networking. On both Mac and Hack, on both Yosemite and Windows, the Linux-hosted SMB fileshares and printers worked without any issue.
I point this out because from what I know, samba is based on SMB1/CIFS, while Windows and Yosemite use SMB 3, a newer version of the protocol. Perhaps this is the repeat of the SMB 2 fiasco on Mavericks.
I have been testing Yosemite since its early previews. It has had its share of bugs but this one seems to be unique to the public release builds only as SMB was working fine on previous builds of Yosemite.
Any information and suggestion on how to fix this would be greatly appreciated. I will do some more testing with fallback to CIFS for printing in the interim.
UPDATE: CIFS printing is not supported as you cannot add a printer using cifs://.
Last edited: