Samba Question

[scuzzb494]

Hi

I have this problem at the moment with the SAMBA directory being accessed all the time while I have the interface open in Miami. Using SnoopDOS I saved the log and with CED I coppied and inserted it here. This is the series of actions that seem to loop out contunuously. Just wondered if anyone had any idea what was going on. Never use to happen.

[ that log ]


Count Process Name       Action     Target Name                 Options Res.
----- ------------       ------     -----------                 ------- ----
197   [5] samba:bin/nmbd ChangeDir  Work:Miami                              
198   [5] samba:bin/nmbd ChangeDir  Vault:samba/log/locks                  
199   [5] samba:bin/nmbd ChangeDir  Work:Miami                              
200   [4]      Open       NIL:                        Read    OK  
201   [4]      Open       NIL:                        Read    OK  
202   [6] samba:bin/nmbd Open       Samba:log/log.nmb           Modify  OK  
203   [6] samba:bin/nmbd Open       Samba:lib/smb.conf          Read    OK  
204   [6] samba:bin/nmbd Open       Samba:lib/codepages/codepag Read    OK  
205   [6] samba:bin/nmbd Open       Samba:lib/codepages/unicode Read    OK  
206   [6] samba:bin/nmbd Open       Samba:log/locks/nmbd.pid    Read    OK  
207   [6] samba:bin/nmbd Delete     Samba:log/locks/nmbd.pid            OK  
208   [6] samba:bin/nmbd Open       Samba:log/locks/nmbd.pid    Modify  OK  
209   [6] samba:bin/nmbd ChangeDir  Vault:samba/log                        
210   [6] samba:bin/nmbd ChangeDir  Work:Miami                              
211   [6] samba:bin/nmbd ChangeDir  Vault:samba/log/locks                  
212   [6] samba:bin/nmbd ChangeDir  Work:Miami                              
213   [4]      Open       NIL:                        Read    OK  
214   [4]      Open       NIL:                        Read    OK  
215   [5] samba:bin/nmbd Open       Samba:log/log.nmb           Modify      

As I say, when I have the interface online the external SCSI drive with SAMBA on it is continuously active and the above sequence just loops out. You can hear the hard drive working all the time. Any ideas.

Saying all that, the connection works fine and I am able to get onto my broadband router no problem.

scuzz
Amiga1200 WB3 Blizzard 1230 IV 32MB RAM Miami YAM

[Matt_H]

This used to happen to me sometimes, but I can't remember what I did to correct it. What does the interfaces line in SAMBA:lib/smb.conf look like?

[LoadWB]

IIRC, Samba will hold its logs in an open state.  Even if not, the log being modified is the nmbd (name server daemon) log.  Have you looked at the contents?  It may be that some computer on your network is continually querying for machine names.

[scuzzb494]

Hi ... I believe you are right about another computer being the reason for the looping.. I agree the problem is another machine looking at this one to resolve name address cus I just put a Win98 machine onto the system and the hard drive is now going into its loop. And when I took the ethernet off line I get this error

' bsdsocket.library V3 could not be opened ' .... Sorry

So is there any way I can stop this from happening other than not having another computer on the grid when on broadband. When I had assigned IP addresses there wasn't the problem

[  On the issue of assigned IP Addresses ]

The only way I could get the Amiga to run on broadband was to cancel my assigned IPs and run on DHCP. This causes the following to happen on startup, though with no issues running YAM and AWEB online.

When I start Miami using my broadband homehub I get this...

Your IP address could not be resolved so Miami Deluxe has to fall
back to your IP address as your host name. Either your Internet
Service Provider does not support reverse mapping on the SLIP/PPP
ports or there is a problem with the DNS servers.

I have DHCP enabled... and I have the IP address for the computer
in my SMB as 192.168.0.2 which when I use DHCP won't work with
the BT Homehub network. I find this on the PCs as when I obtain the
IP address automatically all the computers with assigned IP addresses
disappear off the grid.

[ log ]

Checking the log...


Failed to open nmb socket on interface 192.168.0.2 for port 137.  Error was
Unknown error 0
Miami Deluxe Request

[ nmb log ]

  Netbios nameserver version 2.0.7 started.
  Copyright Andrew Tridgell 1994-1998
[2007/09/09 15:27:17, 0] lib/util_sock.c:(868)
  bind failed on port 137 socket_addr=192.168.0.2 (Can't assign requested
address)
[2007/09/09 15:27:17, 0] nmbd/nmbd_subnetdb.c:(142)
nmbd_subnetdb:make_subnet()
  Failed to open nmb socket on interface 192.168.0.2 for port 137.  Error
was Unknown error 0
[2007/09/09 15:27:17, 0] nmbd/nmbd.c:(823)
  ERROR: Failed when creating subnet lists. Exiting.

scuzz
Amiga1200 WB3 Blizzard 1230 IV 32MB RAM Miami YAM

[Matt_H]

DHCP with Samba on the Amiga is very troublesome. I eventually gave up on it and switched back to static IP addresses.

You have two separate problems, one with Miami failing to acquire an address through DHCP, and the other with Samba.

In Miami, set the IP type, netmask, and gateway of your interface to DHCP. Then press the 'TCP/IP Settings...' button and enable DHCP there. Send your hostname as well. Set 'Get Dynamic DNS Servers' to 'verify&add'. Hopefully that will solve your general connection problem.

I've found however, that Amiga Samba is dumb, and can't figure out DHCP IP addresses. You'll need to manually adjust the interfaces line in smb.conf to whatever your current IP address is (your router can usually tell you this). You also need to have your hostname and current IP address as well as the hostnames and IP addresses of any machines you want to connect to listed in the 'hosts' page of the Miami database.

Yeah. Having to manually update all this for DHCP changes is extremely annoying. Unless someone else knows a workaround, I say try going back to static addresses.

[LoadWB]

I supposed you could script it.  I've honestly never worked with Samba on any system with a DHCP IP address -- always static.

Aside from the IP issue, you could also just disable logging for nmbd.  You can do it in swat or by adjusting the smb.conf file, though I do not recall the exact parameter to do so.

There's also an option for browse master you'll find somewhere in swat.  A browse master for a work group maintains a list of machines and services offered within that work group, kind-of like a "poor man's" WINS but not quite as I believe SMB/CIFS will still broadcast query for machine names.

Man, I haven't played with this stuff in a LONG time :-)

[scuzzb494]

Hi

>In Miami, set the IP type, netmask, and gateway of your >interface to DHCP. Then press the 'TCP/IP Settings...' >button and enable DHCP there. Send your hostname as well. >Set 'Get Dynamic DNS Servers' to 'verify&add'. Hopefully >that will solve your general connection problem.

Your comments made me realise I was not doing something I usually do when I run the interface on my network... ( ie  when as an assigned IP address for machines not on the broadband network ) When I put online the Ethernet for this network I force NMBD by activating a script from an icon I have on the workbench backdrop.

WAIT8
run>nil: samba:bin/nmbd -D
run>nil: MiamiSysCtl -w inetd.toomany=50

Before, I was using dialup so not using ethernet for my internet ( just a modem ) so when I checked YAM I wasn't using the ethernet. Then I would activate differing computers from running NMBD and putting the interface online and not the DIALER. I would then run another script from an icon on the desktop as follows:

Wait8
Run SMBFS Volume="PCComputer" Workgroup=Amiga user=scuzz Service=//Amiga/c/amiga

This then activated the PC drive as an icon on the workbench and was accessible as a drive on the Amiga. I have several icons on the desktop setup this way to access drives on other machines. Thing is I naturally ran NMBD when I put the network interface online and forgot I would need to do the same to use the ethernet for the broadband. So I just fired up the interface ran NMBD and then YAM and there was one loop as the computers talked to each other and they realised who each was and the loop stopped. Job done. Missing the obvious. But talking here made me realise. So thanks for that.

Process for putting Amiga online on the PCMCIA ethernet interface:

First click my CardReset tool to get over that bug with the PCMCIA interface. Click Suspend and the card goes on line:

I then fire up Miami and finding the Inteface that has the specific IP addresses set up for my local network I put this online.

I then run the NMBD script from an icon I created for the following script:

WAIT8
run>nil: samba:bin/nmbd -D
run>nil: MiamiSysCtl -w inetd.toomany=50

I then get that single looping hard drive sound as the computers talk to each other.

I then click my icon for the drive on the other PC that I want to access:

Wait8
Run SMBFS Volume="PCComputer" Workgroup=Amiga user=scuzz Service=//Amiga/c/amiga

And then that drive appears on the workbench and I can access that drawer as a normal Amiga drawer. I have these set up in DOpus.

[ FOR INTERNET and Broadband ]

For Broadband I need to do the same, but instead run the NMBD after I have gone on line with the Interface set up with DHCP and not my local network, and like magic when I run YAM the looping is no more. It is wonderful that you can set up Miami with differing configs for interfaces.

Thanks for that.

scuzz