Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: ehbowen on April 13, 2007, 05:02:19 AM
-
So I'm trying to install Samba 2.2.5 to network my classic Amiga 3000 (12+2 MB RAM, stock 25 MHz 68030 processor, X-Surf ethernet card, Miami) with my Dell Windows 2000 machine. I connect to the internet via DSL with a Linksys router as my gateway.
I made it through most of the installation process as outlined on Amiga Samba for Idiots (http://samba.amigaworld.net/index.html) OK; in fact, right now I'm copying a Quarterback backup file of my SYS: partition to my backups drive on the Windows machine.
So sometimes I can access the Amiga drives from the Windows machine, although the connectivity comes and goes for reasons I have not yet been able to determine. But so far I have not been able to access the Windows machine from the Amiga. I'm attempting to use smbfs to mount the Windows drives on the Amiga, but every permutation of passwords, user ids, etc that I can think of gets rejected (and yes, I have created a user account for the A3000 on the PC). Smbclient does work and shows the PC drives which are set for sharing, but smbfs keeps turning up nothing but error messages.
One more thing--while the connectivity works from the Windows side, it's slow as molasses. We're talking 30-45 seconds just to open a directory folder. Anyone have any ideas as to how I could speed that up? Thanks in advance for any help.
-
:-? It's been ages since I've tinkered with Samba, since my A4000 stopped working for me, but one detail that I recall having trouble with was Genesis, my A4000's TCP stack. Samba needs to run as root, with a user ID of zero. Genesis needs to be configured to do that as default. There are settings somewhere that lets you tell it to.
Hopefully this will do the trick for you.
-
There is also a local security policy in Windows XP which MAY or MAY NOT need to be set. I recall setting it in the past, but do not know if it's still relevant. I is the packet signing policy, and I found the info from the Samba page. I can't give you any better than that right now.
I have also found that connectivity comes and goes, mostly seeming to be related to load cause by Windows' SMB stack.
Best I got for ya here. I know that after moving from the WarpEngine 4040 to the CyberStorm MKIII 060 has made a LOT of difference in Samba stability.