Samba and SMBFS...

[flaviosr]

Hi to all,
I configured Samba and it's ok! I can ping, the Amiga is seen and the sun is shining... :-)
But when I try to use SMBFS I have some problems:
° I made small scripts to "see" some PCs but only few times these scripts works... most of the times nothing happens and some the computer hangs;
° if I copy these scripts in a CLI shell everything is ok!
ARGH!!! What am I missing?

Another help: is it possible to disconnect a connection? If I stop Miami while a connection is on, the computer hangs most of the times...

Thanx

[flaviosr]

I'm mounting SMBFS shares fine through scripts, so can you give an example of your script that doesn't work?

FYI, you actually don't need Samba installed for using SMBFS.

As for stopping a share, RTFM. Write Status in CLI to see which process you have to break, and then write Break to break the connection.

My script is very easy, changed today to the following line:
RUN SMBFS Volume="name volume" Workgroup=WORKGROUP Service=//computer/directory

I also changed stack to 32768...

Most of the times it hangs and only some it works...
First I had also >nil: but without it I can CTLR+C to stop!

If I copy the line to a CLI line everything works always (apart my CTRL+C problem... if I close this way the PC hangs...).

Since I am not so good in AmigaOS:
° I created the file with editpad and saved it;
° I opened the info for the file;
° I have the "V" (I do not know the word in English!) for script and removed the one for executable;
° I changed the stack today to 32768;
° Priority 0???
° Have I to executo from Workbench? Now I have this doubt... is it better to run from CLI?
° I change the association from editpad to iconx...

anf, anf, anf...

Where am I wrong?

[flaviosr]

Are you sure that everything always works if you launch smbfs manually?

There's a potential issue with name resolution. If you don't have a DNS entry set up for each server you want to connect to, smbfs will fall back to sending broadcast name queries through the network in the hope that the server you want to connect to will respond. This may not always work. In fact, depending upon your TCP/IP stack it may not work at all. The reason why it may not work is because the TCP/IP stack may not be able to send the broadcast query to the right place due to a bug in the old TCP/IP code.

Anyway, a workaround for this name resolution issue is to use the IPv4 address of the server instead of trying its name.

So... the next question would be: how do you launch smbfs if you don't enter the command manually?

Bad news (for me)... I made more tests and SMBFS hangs also when launched from CLI but not so often when lauched with a script!
I tried with IP address instead than name but I had no results!
I tried passing from SMBFS 1.74 to the older 1.66 but again no results.
If I use device and service together the Amiga hangs immediately!!!
When I launch a script nothing happens... but if I open a CLI and try to "enter" the new device I receive a memory error!!! :-o
I am using a standard 18 Mb A4000T, could it be not powerful enough?

Another question: are you using Miami or Genesis?
Which is better?

[flaviosr]

Well, at least there's some consistency now. I'd be mighty surprised if the thing worked one way or not the other. From what I know, this sort of thing either works, or it doesn't, regardless of where or when you launch it.



Ouch. Does the server you want to connect to have a regular name? If so, does the server's own name, as reported by Samba, match it?

This is correct... and the problem is that NOT ALWAYS I have problems...

Generally, the newer versions have drastically fewer bugs and show less wacky and unpredictable behaviour. I recommend you try the newer version.

You are right... I am going to pass again to the newer version (I want to add anyway that I cannot use Picasso96 rev "c" and I have to use rev "b"!!! :-) ...)

Honestly, this sounds rather bizarre. Does your Amiga crash or lock up in connection with the TCP/IP stack, or does it take smbfs to make trouble?

Imagine how I feel!!! ((
The Amiga lock up... never crashed...
I tried different amounts of stack but I notice no differences...

When did you last test your system's memory? Easy way to make a memory test: copy data from your hard disk into RAM-Disk until either RAM-Disk fills up, or your system crashes. If your system crashes before it fills up, you might want to see to those SIMMs.

I will try but I have the same problem in two different Amigas...

Depends upon what you're doing. Miami tends to be slower than Genesis. But Miami's GUI may arguably be a better design.

I am thinking about the Amiga that I am using for tests... a "poor" A4000T with 68040@25... could it be that it needs time for the Amiga to be "connected" to my intranet? For example, even with fast PC, it takes a bit of time before other PCs are seen... perhaps simply the Amiga hangs instead than waiting for the connection to be extablished.

I am going to test the memory (always a good thing) and trying also Genesis that you tell it's faster... and also waiting for some time before asking for a connection...

Other suggestions?