Jump to content

Connect to SMB windows Error -50


  • Please log in to reply
23 replies to this topic

#21
wahwahman89

wahwahman89

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 184 posts
  • Gender:Male
  • Location:Someplace, Somewhere, United Kingdom
I had this problem too and fixed it using Vas's method. Works like a bloody charm!!! Thank you so much and anyone having the same problem, use that method!!!

The weird thing is my fiancee's laptop is running 10.4.6 and doesn't have that problem whilst mine had it from install (mine is 10.4.8... Jas's). Brilliant!!! Thanks!! :) :wacko:

#22
Pericles Silva

Pericles Silva

    InsanelyMac Protégé

  • Members
  • PipPip
  • 54 posts
  • Gender:Male
  • Location:Rio Grande do Sul - Brasil
Works great for me!!! I' using Tiger 10.4.8 (JAS), and works fine. Thanks my man!

#23
fyrekrig

fyrekrig

    InsanelyMac Protégé

  • Members
  • Pip
  • 42 posts
Trying to use Vas method on 10.4.11 but unsuccessful.

Done the script twice, same result. Message says that smbfs.kext is incorrectly installed and connot be used.

When I try to connect via "Go" and smb:// I now get Error 36.

Have a second Tiger 10.4.11 running on the network and from this I have no problem accessing the Windows XP PC.

Have tried to find any differences between the two versions without luck.

#24
Jason Gr

Jason Gr

    InsanelyMac Protégé

  • Just Joined
  • Pip
  • 1 posts
I am havin gthe same issue, error 50 when trying to connect to my NAS using SMB://IP

after trying the instructions above regarding the use of smbfs.kext I am now getting an error 36.

Does anyone know the fix?
I just need to get my mapped network drives back online...





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy