This page is a wiki. Please login or create an account to begin editing.


22 posts / 0 new
Last post
m68k's picture
Offline
Joined: 2016 Dec 30
[Solved] NFS or Samba Client for 68k MacOS 8.1

Hello Folks,

I found an archive titled "MacNFS" on the Garden and on some Internet sites, but it always only contains a single extension file and a readme describing it as an "update" to a full flung MacNFS installation. Now where can I get said installation from and does a Samba client exist for 68 Macs?

Comments

fogWraith's picture
Offline
Joined: 2009 Oct 23

You mean this? It seems to contain all the information required.

m68k's picture
Offline
Joined: 2016 Dec 30

Its just one extension, which means it doesn't even have a user interface. And it says its "a patch" for a full flung installation.

fogWraith's picture
Offline
Joined: 2009 Oct 23

In other words, you didn't even bother looking.

Knez's picture
Offline
Admin
Joined: 2010 Feb 11

I'm the one who did the upload and wrote the little guide on the page. It works. Read the guide on the MacNFS page Smile

m68k's picture
Offline
Joined: 2016 Dec 30

I did "bother to try" and its just not working. I tried it with three (3!) different NFS servers and each time the chooser client complains that "no portmapper" daemon is running on the target system. But I veryfied that the NFS servers are working normally.

Maybe it doesn't like OpenTransport or it will only work with ancient NFS servers. But I spend (wasted) two days on this. Sad

Knez's picture
Offline
Admin
Joined: 2010 Feb 11

You have DAVE for Samba/CIFS, but it’s very outdated and won’t connect to recent versions of Windows and Mac OS shares. If you have a Linux or OSX box sitting next to your 68k Mac I would recommend MacNFS.

adespoton's picture
Offline
Joined: 2015 Feb 15

Thanks! This looks like a better file transfer solution than FTP....

m68k's picture
Offline
Joined: 2016 Dec 30

Ha, DAVE 2.5.2 is the one I was looking for. Thx a lot for that hint. The problem with MacNFS is the combination of programs it expects to run on the server's side. Specifically the password authentication daemon pcnfsd is a source of trouble, as it is actually not required for anonymous access - in that case the client performs the authentcation and doesn't even send a password across. So many modern day lighweigt NFS servers (as in embedded routers) don't even offer that daemon. And MacNFS doesn't seem to support v3 of NFS fully either, as I found protocol error messages in the logs of a strict v3 NFS server.

Yet the setup of DAVE went smooth and I was able to mount my SAMBA network share right away. Now I can read & write files across the net and I can even use Windows' printers from my vintage Mac system. Smile

cbone's picture
Offline
Joined: 2011 Sep 17

That's excellent, m68k Laughing out loud now that's what I call networking! DAVE's the real deal then Wink

Just to confirm, it works with Basilisk II w/Mac OS 8.1, right?

m68k's picture
Offline
Joined: 2016 Dec 30

It works *flawlessly* between MacOS 8.1 on B-II and my OpenWRT Router and my Win 10 machine. For all tbe headaches I had with MacNFS, DAVE is almost too ez to set up (hey Murphy, I am not asking for trouble here!).

cbone's picture
Offline
Joined: 2011 Sep 17

Sweet! Installing now Smile

m68k's picture
Offline
Joined: 2016 Dec 30

The one thing I found is that the resolution of domain names works with certain tools (=> MacSSH) but not with others (like DAVE). My solution is to assign fixed IP# on the router to all my devices and then use those IP#s in B-II..

cbone's picture
Offline
Joined: 2011 Sep 17

assign fixed IP# on the router

That's smart. I assigned it inside my Windows server since it's the hub, but I haven't really played with the router's settings to do so on that end.

It was quick and dirty, but I should have done it from the router from the get go Doh! then again, I only did it so my handful of bookmarked server ip addresses would stop breaking. After my old router stopped running, I noticed my new one kept switching IPs on the server, so I configured it manually.

m68k's picture
Offline
Joined: 2016 Dec 30

Also, Windoze 10 by default disables legacy SMB support (CIFS 1.x). As long as you're not in a public or coporate setting, its OK to turn it back on again:

Command line -> appwiz.cpl ->
Click on 'Turn Windows Features On or Off' ->
In the popup scroll to SMB 1.0/CIFS File Sharing Support.
-> Check the option -> Click "Ok".

I installed legacy support for both client & server, which allows me to share files directly between B-II and Win 10, bypassing the shared storage attached to the router (saves me one step when transferring files).

cbone's picture
Offline
Joined: 2011 Sep 17

Great! I've turned it on, so SMB now allows me to share a folder or volume now, right?

And WiFi should be secure so anybody outside won't potentially find and go through any stuff I share on the network, I'd imagine, unless user and password permissions possibly suffice for security at home, and/or the stuff I share isn't financial stuff, pictures and the like.

m68k's picture
Offline
Joined: 2016 Dec 30

The only danger here are "man-in-the-middle" attacks from someone within your own network. Also, you can secure the access by password, Windows domain user and firewall rule (I did all three). Last not least: Only share specific folders, instead of whole drives

m68k's picture
Offline
Joined: 2016 Dec 30

Btw, I found out that fiddling around with namebuffer settings and disabling Namebios detection scans can increase the speed significantly. If you use Namebios at all, then do it via TCP/IP, 'cause Basilisk-II can't handle native NB protocol (who would want that anyway?)

cbone's picture
Offline
Joined: 2011 Sep 17

Thanks for that tip Smile I've always been a fan of speed and disabling non-essentials is always a good practice!

m68k's picture
Offline
Joined: 2016 Dec 30

If you got a floppy disk you could do me a real favor by extracting Speed Doubler for me, as I can not get that installed in B-II w/o a mechanical floppy. Sad

cbone's picture
Offline
Joined: 2011 Sep 17

All my real Macs atm use CD-ROMs and WiFi cards for connectivity and installs.. sorry m68k!

cbone's picture
Offline
Joined: 2011 Sep 17

Which on did you try out? The one that's here is older and fogWraith gave a link to a version that should work, no emulator compatibility info was provided, though.