Hi!

I've been trying to mount a samba fs in my peg, but it does not work...

Using smbclient, everything works fine, so I think its not a trouble of anything else but smbfs or my configuration.

Peg part: I'm using MOS 1.4.5 with Miami (not DX)
PC part (called shodan): Windows 2003 server, using a domain (and being the domain controller).

If I do something like:

smbclient -Umass //shodan/c$ my_password

It works flawlessly, I can upload and download anything. No problem.

But then, I try:

smbfs domain=casa username=mass password=mypass //shodan/c$

And this returns:

smbfs: ERRDOS - ERRnoaccess (Access denied).
smbfs: Cannot connect to server (13, Permision denied).
smbfs: Could not connect to server (13, Permision denied).

Anyone have any idea about this? Thanks!!

Try to add your shodan host<->ip in hosts database.

Two things:

Did you try by replacing the server by the IP?

Also, try this line:
run smbfs workgroup=casa user=mass password=mypass
devicename=SMB1 volumename=C@shodan service=//shodan/c

I had already the server's ip in my hosts list... And trying with the IP doesn't help, same answer.

With that command, I also get the same result :(... Perhaps it is a problem with the domain... If anyone has any other suggestion...

Hi Amiades,

smbfs stopped working for me here. It used to always work now it fails with similar messages. I bet it stopped working when I switched to MOSNet. I will let you know.

When I get time on my peg I will try to figure out what caused the failure and try to find a workaround.

Matt

Quote:

Did you try removing the "$" symbol from the service name (it seems that SMBFS doesn't like certain characters)?

I'll try it further today, but I have already try another shared directory just called "pepe" and doesn't work also...

I'm sure you already know but... That "permisson denied" error is classic from lack of permissions. The "c$" share is only for Administrators, you should better use normal shares.
Have in mind that shares, as a resource, have their own permissions. And then, when that resource is about a directory, this later element also has permissions. You could very well leave the resource as full control for everyone, and then have restrictions in the directory. Give it a try also with full control for everyone in the later, to see what happens.
It looks as you don't have any other lower level problem (communications itself), because that error message comes from your server, that means that the two computers are actually talking. Otherwise, perhaps the operating system of your server is talking a different dialect of the protocol ("Samba", which actually is "CIFS"), and MorphOS can't cope with. Anyone else dancing samba with Windows 2003 Server?

I could not try yet with a shared folder, as I had had little time this days, but I will try soon... The thing that makes me angry, is that using smbclient everything works fine... that should mean, that it's not a permissions problem ;)... but i will try with a public share, of course... It's quite extrange...

Your syntax is not quite right. Try launching like this:

smbfs workgroup=scc device=smb2 service=//10.0.0.5/music/ user=foo password=bar volume=MP3

Remember to have that IP added in your HOSTS file aswell.

Try using quotes.

smbfs domain=casa username=mass password=mypass service="//shodan/c$"

And as someone mentioned, it's probably wise not use c$ but to set up some proper shares.

Hi Amiades,

smbfs does not run for me under MOSNet or Genesis. It runs perfect with Miami.

I'm using the exact same syntax for my tests.

Try Miami and see if you have the same results.

Good luck

Matt