samba - Nov 1998 - Samba startup problems

Hi,
I've got a problem with Samba starting up on an Alpha running redhat 5.0 .
It takes ages
to load to of the services and the second times out with an error:

Starting SMB services:  smbd httpd:  cannot determine local host name.
Use ServerName to configure it manually.

Anybody got any good ideas.  I've read all the stuff I can find about samba 
but not had any luck.

Matthew

I'm running Samba 1.9.18p4 on an SGI Octane running IRIX 6.4.
People who have accounts on the machine can access their home
directories without problems, so it is configured and running OK.

We have a filesystem (/pc1) that is to be used by any of the PC
users.  I have not gotten it to allow people to access the disk
without requiring an account on the octane though.  I've RTFM, and
obviously am missing something.  What am I missing?

My smb.conf file is below.

Thanks for any assistance.

Kenneth

[global]
   load printers = no
   guest account = guest
   lock directory = /usr/freeware/lib/samba/locks
   share modes = yes
   dead time = 15
   hosts allow = 127.0.0.1, 38.254.139.
   security = server
   password server = Windows_NT_Machine
   encrypt passwords = yes
   null passwords = true
   workgroup = ARA_DOMAIN
   auto services = pc1

[homes]
   comment = Home Directories
   browseable = no
   read only = no
   create mode = 0750

[tmp]
  comment = Temporary file space
  path = /tmp
  read only = no
  public = yes
[pc1]
  comment = File storage on octane1
  path = /pc1
  read only = no
  public = yes
  writable = yes
  guest ok = yes
  guest account = guest
  user = guest
  browseable = yes

Hi,

I have somehow created a really strange behaviour for our samba server. I have
no trouble logging on from my NT, I can browse around the shares, create files
and all that, but I can't READ any files! When I log in with smbclient I get
a
"Access denied" message, whereas windows says that the file is open by
someone
else. I have tried many things, inluding unmapping all of windows flags, using
cleartext passwords and much more. The most irritating part is that I
installed samba on another network, using the same smb.conf, and it worked
exactly like it should! Am I cursed?

Using 1.9.18p10 with smb.conf below:

[global]
  workgroup = KINGDOM
  hosts allow = 193.180.255. 127.
  encrypt passwords = no
  map archive = no
  map hidden = no
  map system = no
  workgroup = KINGDOM
  dns proxy = no

[homes]
  comment = Home Directories
  browseable = no
  writable = yes

[tmp]
  comment = Temporary file space
  path = /tmp
  read only = no
  force create mode = 0755 
  public = yes

-- 
http://www.oops.se/~urban
[Heard on answering machine: "Hi. I'm probably home, I'm just
avoiding]
someone I don't like. Leave me a message, and if I don't call back,
it's you]