@Raziel

Quote:

Raziel wrote: @Mikey_C I have two 137 ports one is upd and one tcp, but that shouldn't matter, should it?

No, that doesn't matter. What's important is that UDP is registered for port 137. The NetBIOS name service does not use TCP.

@MichaelMerkel

Quote:

MichaelMerkel wrote: hi. i have one little problem after configuring everything like described: on our win xp pro machine the network neighborhood does not show any single computer from the workgroup. everything seems to be set correct. right after i set up samba it worked for one day. i could see both computers listed there - the pc itself and also the amigaone. now the list is empty! if i type in the ip address of the amigaone in the exporer address bar i can connect to it, browse the disks and copy files. just the workgoups list is empty. any hints? i tried all i can imagine byebye...

That's how these things work, I'm afraid. Name resolution information (the stuff that comes out as the local network neighbourhood list) is cached by one of the systems in your network. Since neither the name resolution protocol nor the caching is particularly sophisticated or sound you are bound to see quirky behaviour like this.

Here's a recent example: about three weeks ago I set up a storage server in my company. That server runs Samba, but I made a small mistake in configuring the workgroup name for it. The small mistake had the effect of making the server show up as a member of workgroup "unknown", with all attempts to authenticate to it failing. That was three weeks ago. I corrected that mistake quickly, but the invalid host name entry is still being cached by one of the other SMB servers in my company. In fact, the server now shows up twice in the network neighbourhood: once as an invalid entry, and once as the correct entry. How do you tell which is which? Trial and error.

So, what do you do to keep the network neighbourhood list up to date and reasonably correct? The general answer is (...drum roll...) that you can't. Due to how the name/address database caching works, there's always bound to be one sorry server around which didn't catch the drift and insists on keeping and supplying outdated information. While it's easy to get junk into the name resolution database, it's not as if it were easy to get correct information into that database either.

@vortexau

Quote:

vortexau wrote: I was trying to setup Samba to connect (via a ADSL Modem + 4 Port) to the eMac in another room. The main problem is the hard drive engauges non-stop writing a log file to the log directory. This log repeats that it "ERROR: can't open /samba/log/locks/nmbd.pid: Error was No such file or directory" So, where should this elusive nmbd.pid file reside?

It goes into "Samba:log/locks". Make sure that the "Samba:" assignment exists and the "Samba:log" directory is writable. Samba should create the "locks" subdirectory, if it doesn't exist, but that's pretty much all it does for you.

Quote:

and how to point Samba at it?

This is usually configured in the "Samba:lib/smb.conf" file, which should contain a line which reads as "log file = /Samba/log/log.%m" (without the double quotes, of course).

Quote:

. . . and why is that log file being written to that log directory in Samba when the Amiga documentation points out it will keep its log file in RAM: ?

Because what's in the configuration file does not match the documentation? Also, I would not recommend to keep log files in RAM: since they tend to eat up a lot of memory. Put differently, keeping Samba's log files in RAM: is a good way to make Samba fail due to running out of memory.

Quote:

Final question- Why is Samba expecting a *nix directory structure?

Because Samba is a Unix program and still "believes" that it runs on a Unix system. My emulation layer library gives it that impression.

@olsen

Olaf, cheers for answering some of the questions I am unable to help out on, many thanks

_________________
No cause is lost if there is but one fool left to fight for it.

@Mikey_C

Quote:

Mikey_C wrote: @olsen Olaf, cheers for answering some of the questions I am unable to help out on, many thanks

I heartly second that! Thank you for those answers.

_________________
-vortexau, who's A1 XE-G4 remains at half-RAM !
A2000HD (from 1991) 060 64Mb PicassoII with OS3.5 . . . still working.

@olsen

Understood, i still get this messages in the nmbd-log

[2005/07/13 17:25:33, 0] nmbd/nmbd.c:(803)
Netbios nameserver version 2.2.5 started.
Copyright Andrew Tridgell and the Samba Team 1994-2002
[2005/07/13 17:25:33, 0] nmbd/nmbd.c:(835)
standard input is not a socket, assuming -D option
[2005/07/13 17:25:33, 0] lib/util_sock.c:(810)
bind failed on port 137 socket_addr = 0.0.0.0.
Error = Address already in use

Any idea?

@Raziel

You sure you are not calling NMBD twice?

If you have nmbd in your user-startup, there is a good chance it's already been called once via roadshow.

_________________
No cause is lost if there is but one fool left to fight for it.

@Mikey_C

Solved it on the AOne, it was a typo in smbd.conf (Aone address was the same as
A4000 address)

Now for the 68k part, i get no error (log) from nmbd, but there's also no "nmbd"
in the status list

Also the fact that is really giving me headaches, i CANNOT ping the AmigaONE
Neither form the A4000 NOR from the AOne?

There is some minor glitch which i cannot nail

@Raziel

Oh, and btw, if i try to "smbclient -L azure", i get:

Added interface 192.168.1.41 bcast=192.168.1.255 nmask=255.255.255.0
Connection to azure failed

on the AOne and
Added interface 192.168.1.42 bcast=192.168.1.255 nmask=255.255.255.0
Connection to azure failed

on the A4000

@Raziel

Quote:

Added interface 192.168.1.41 bcast=192.168.1.255 nmask=255.255.255.0 Connection to azure failed on the AOne

On the A4000 side Genesis tells me in a loop

inetd[8c0e000]: samba:bin/nmbd: exit status 0xffffffff

and then the last message is:

inetd[8c0e000]: netbios-ns/upd server failing (looping), service terminated

@Raziel

I had that problem too.

Darn! can't remember what the solution was now, but I did fix it. Will try to remember and post back. (Yes I did fix it)

_________________
No cause is lost if there is but one fool left to fight for it.

@Mikey_C

Ehmm ok, my hd is becoming full with log...SnoopDOS says (ever and ever):

Count Process Name Action Target Name Options Res.
----- ------------ ------ ----------- ------- ----
1 [1] AmigaOS4:Devs/ Lock samba:log/locks/nmbd.pid Read Fail
2 [1] AmigaOS4:Devs/ Lock samba:log/locks/nmbd.pid Read Fail
3 [1] AmigaOS4:Devs/ Lock samba:log/locks/nmbd.pid Read Fail

etc etc...

uhm, I've configured following your guide...

Ciao

ShInKurO

@ShInKurO

yuu!?

@Raziel

Quote:

Raziel wrote: @Mikey_C Solved it on the AOne, it was a typo in smbd.conf (Aone address was the same as A4000 address) Now for the 68k part, i get no error (log) from nmbd, but there's also no "nmbd" in the status list Also the fact that is really giving me headaches, i CANNOT ping the AmigaONE Neither form the A4000 NOR from the AOne? There is some minor glitch which i cannot nail

Sounds tragic. I suggest you try hard to make nmbd cough up a log file of sorts. There may be more than one reason why there is no log file to start with. SnoopDOS might produce some information that could be helpful here. For example, it's possible that nmbd isn't even getting started.

Quote:

by olsen on 12-Jul-2005 10:00:29 @vortexau Quote: vortexau wrote: I was trying to setup Samba to connect (via a ADSL Modem + 4 Port) to the eMac in another room. The main problem is the hard drive engauges non-stop writing a log file to the log directory. This log repeats that it "ERROR: can't open /samba/log/locks/nmbd.pid: Error was No such file or directory" So, where should this elusive nmbd.pid file reside? It goes into "Samba:log/locks". Make sure that the "Samba:" assignment exists and the "Samba:log" directory is writable. Samba should create the "locks" subdirectory, if it doesn't exist, but that's pretty much all it does for you. Quote: and how to…

The nmbd.pid file should reside in the 'locks' subdirectory within '/Samba/log'. Ensure this directory exists and is writable by Samba, which will create the necessary directories if they don't exist already. The log files are configured to be written on disk for safety reasons; storing them in RAM would risk memory exhaustion due to their size. Lastly, despite being a Unix program, Samba uses *nix-style paths because it was originally developed as part of the NetWare suite and maintains compatibility with that environment structure.