Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: outlawal2 on January 26, 2020, 09:25:41 PM
-
Attempting to connect to a WINXP box with my Amiga and have the Plipbox installed and configured and it works fine with Amiga Explorer
I bolded that to show that the Plipbox is working as it should and is verified
With that said I have installed SMBFS and cannot get it to work for me.
Running from the console I type the following:
smbfs service=//xp1/amiga workgroup=skynet user=ghost password=xxxxxx
This errors out with the following:
smbfs program failed (error #80000006) Wait for disk activity to finish
Then I need to restart from scratch.
Any suggestions on what I am doing wrong here?
For the record I can connect to the XP machine from other Windows machines on my network with no issues.
Please advise
-
Try the smbfs.debug version and add the DEBUG parameters (I can't remember the exact names but info is in the docs). And then maybe can see if there is anything helpful in the logs.
-
Thank you for the suggestion.. IS that a different version of SMBFS or is that a parameter to run within SMBFS?
Please advise
Thanks!
-
Yes, this is different executable called "smbfs.debug" and is in the #?.lha archive.
But you also need to add the "DEBUG" options to "smbfs.debug" version as well to get the debug output.
-
Is the Amiga able to resolve "xp1" to an IPv4 address?
(The other Windows machines are most likely using IPv6 to access each other, unless you specifically have configured them not to)
-
KOLLA
I can ping the IPv4 address from the Amiga but SMBFS will not allow me to use the IP address as the host name. (Which I find to be perplexing as I would think that if ANYTHING should work the IP address should!) And no, none of my machines are using IPv6. IPv4 for all machines, with most of them in a Windows domain with Windows domain controllers. XP1 is the only machine running in a workgroup as it was specifically built for no other purpose than to communicate with my Amiga machines. XP1 DOES communicate with the other domain PCs and can share files once I provide the password manually so I know that the XP1 share works properly. (At least as far as Windows machines go anyway.) Reading about the newest version of SMBFS I see that it is supposed to work with Windows 7 so I may spin up a Windows 7 VM and see if that works instead. There may be some issues with the version of SMB being used on my Windows PCs that is causing a problem communicating with the Amiga.
Last night I grabbed the latest version of SMBFS and replaced the older version on the Amiga but ran into the same issues with XP. (I haven't had a chance to try the debug options yet as I don't know how to use them, but once I do I will post some more info here.)
Really appreciate everyone's help and more to come!
-
So a simple “ping xp1” on the Amiga works?
-
Not sure if I tried that or not. I do know that pinging the IP works but I will test name resolution when I get home. (At work now)
Thanks for the help!
-
OK, Ping XP1 does not work, but PING 192.168.0.15 does... And yet SMBFS will not accept the IP address as a host name. So now I tried the following:
SMBFS service=//XP1/AMIGAVAULT workgroup=WORKGROUP user=GHOST password=password
ONE TIME it showed as connected. But nothing showed on the desktop and I could not see any way to "see" it or access it. Thought I would try DOPUS at this point and it hung.
Now every time I run it, it simply hangs the system requiring a total restart.
I find all of this behavior as strange as it won't ping XP1 and yet it did connect, once. And no idea why I can't ping it as I have my nameserver listed in the route file and the nameserver file as well in DEVS/Networks
EDIT: Forgot to mention that I am using a Plipbox NIC and RoadShow IP stack..
-
I use SMBFS on my A4000T and my Amithlon to access my NAS volumes.
smbfs WORKGROUP=myworkgroupname User=myusername Password=mypassword Volume=Vol1 Service=//MyNAS/Volume_1
smbfs WORKGROUP=myworkgroupname User=myusername Password=mypassword Volume=Vol2 Service=//MyNAS/Volume_2
This mounts Volume_1 on my NAS box as Vol1: and Volume_2 as Vol2: on the Amiga workbench.
I have in devs:internet/hosts (of Roadshow) added the IP address and name of my NAS at the bottom of the file.
ipaddress MyNAS
-
Yes, it seems to be quite important to have the server entered as a host in the Internet prefs (or directly in the hosts file), with the correct hostname and IP address. SMBFS wants this, even if you use the IP address instead of the hostname in your command.
Best regards,
Niels
-
OK, Ping XP1 does not work, but PING 192.168.0.15 does
Well, then it's no wonder - the protocol is based on netbios and often relies on host names.
Just put xp1 with its IP-address in DEVS:Internet/hosts
-
Thanks guys I will give that a try and see how it goes.
<thumbsup>
-
Entered the info in my HOSTS file and still locks up when I try to connect and interestingly still does not ping the hostname
Do I need to remove my entries for my nameservers when I use HOST file?
-
No, but at this point it is a bit unclear exactly what you have in which files. That you cannot ping the hostname even though you have an entry i hosts suggests that you’ve got something wrong in some file, so that resolution doesn’t work at all.
-
Yeah I agree with you.
Sounds like too many things going on in multiple places so I may just grab another drive and try a fresh 3.1.4 install and start from scratch and see if I have better luck
Of the versions of SMBFS available for 68000 which version(s) do other folks have that are currently working correctly for them?
I have read some conflicting info regarding versions so which version do folks recommend for a fresh install on 68000?
-
Isn't latest version from Olsen is always the one to recommend? I don't use smbfs myself, so I cannot really tell.
What I can tell is that SMB/CIFS is a rarther heavy and complicated protocol with tons of legacy Windows cruft in it, and Amiga users would be better off if there also was a free and open implementation of Amiga NetFS server available. But that's not really the topic here.
-
Well USUALLY I default to using the latest version of whatever software is available as that is generally the best route.
I only asked the question because I seem to recall some folks not recommending the newest version due to some bugs that could be show stoppers. Since I can't verify what individual people say on a forum I wanted to see what the consensus was regarding what version everyone was using and why.
Thanks for all the responses folks much appreciated!
:)
-
I use version 2.1 daily - it works great.
You can find it here: https://github.com/obarthel/amiga-smbfs/releases/tag/V2_1 (https://github.com/obarthel/amiga-smbfs/releases/tag/V2_1)
There has been more development since 2.1 (I think it is up to 2.22 or similar) but my understanding was that 2.1 was a stable version. I can vouch for that.
-
Excellent thank you
If I may ask how are you using it? Meaning what are you connecting to on the other end? Windows XP box, MAC, maybe a NAS?
Just trying to narrow things down a bit to remove as many variables as I can. Thanks!
-
My Asus router has two USB ports, and allows for setting up an external drive for Samba sharing. I plugged in a 32 GB USB thumbdrive and set up a Samba share. I can access the share from my PC or my Amiga (using SMBFS)
Setting up the Amiga required putting an entry in my HOSTS file, so that the name resolution would work. Once that is in place, it all falls together nicely.
I actually have more trouble keeping the PC connected than the Amiga, thanks for Windows 10 updates which seem to constantly change settings.
I placed the SMBFS command in my Network-Startup script, and I keep it always available. On my amiga I access the share as device SMB0:, I also have the option to set up a volume that appears on Workbench.
I only stored compressed archives (LHA, ZIP, Etc) on the share because SMBFS sometimes doesn't get the file date/comments/protection bits quite right on the share, bit that hardly matters for LHA files.