SAM440ep+os4.1 Networking Problem

[Hans_]

That sounds a lot like a firewall blocking everything. However, I thought that the firewall (which has no GUI) was disabled by default.

Just a few things worth checking:
- Is the SAM on the same subnet, i.e., do all IP addresses have the same first three numbers (e.g., 192.168.0.x)?
- Have you actually installed the Samba services properly? It's not going to serve anything unless the smbd is running (nmbd should be running too). This doesn't explain why you can't ping the SAM machine from the other machines though.
- try accessing via IP address directly instead of name, e.g., \\192.168.0.2\share.

As to why the transfer in one way is faster than the other, I have no idea. Years ago I had set up Samba on my A1200, and it had a 0.5-1 second delay per file being copied. It made copying directories with many little files painfully slow. Windows networking is a complex beast, and you tend to get problems from time to time even with windows machines (e.g., one computer doesn't see the other computers, but can connect directly via IP address).

Hans

[Hans_]

Ruud wrote:

Hans_ wrote:
That sounds a lot like a firewall blocking everything. However, I thought that the firewall (which has no GUI) was disabled by default.

I thought that but how do you check whether the firewall is active or not?

No idea, sorry. I've never needed to set up the firewall.

Another possibility is that your wireless router's own firewall settings are locking you out. Log on to the router and check if there are any firewall settings that restrict machines on the wireless connection, or any rules that block certain IP addresses. Also, try connecting via wire to the router.

- Have you actually installed the Samba services properly? It's not going to serve anything unless the smbd is running (nmbd should be running too). This doesn't explain why you can't ping the SAM machine from the other machines though.

I presume so as I can read and write to shares on the PC with the SAM.  I've set up both smbd and nmbd in servers.  And as you say I should still be able to ping the SAM from the PC even if samba wasn't installed at all.

You don't need to have the server running in order to connect to other machines. AFAIK, smbfs doesn't need the Samba package to be there at all.

Hans

[Hans_]

Ruud wrote:
Even if samba is not properly installed I should still be able to ping the SAM from the other machines on the network, shouldn't I?

Yes, you should. That's what makes it sound like a firewall issue. Unfortunately I don't have my A1 here so I can't have a closer look at my network configuration.

Hans

[Hans_]

@Ruud

It sounds like your Windows machine is trying to use your windows logon as username and password for shares on other machines. However, it could also just be giving a bogus error message for some other problem.

Have you tried accessing the shares via IP address directly? Otherwise it is still worth checking that you have the shares set up properly in smb.conf. Given that your Amigas can access each other's shares, the Samba server is up and running.

I think that it is possible to tell Windows to not assume that the windows log-on is the user name and password for network shares, but I have no idea how to change that. The other option would be to create a username and password on Samba that matches the one that you use on windows.

Hans