Very Computer

what do the following mean,

(in my log.smb file)

[2001/11/02 10:51:04, 0] lib/util_sock.c:open_socket_in(827)
  Get_Hostbyname: Unknown host
[2001/11/02 10:46:59, 0] smbd/oplock.c:open_oplock_ipc(93)
  open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error
was Connection refused

(in my log.client)
[2001/11/02 10:34:04, 0] lib/access.c:client_match(144)
  client_match: address match failing due to invalid character '*' found in
token '*' in an allow/deny hosts line.

It keeps squaking about the allow/deny hosts line yet there's not reference
to that in my smb.conf file.

here is my smb.conf below:

# Global parameters
[global]
        workgroup = HERMES
        netbios name = SCARUB
        server string = Samba %v running on FreeBSD 4.4
        interfaces = rl0 192.168.0.1/24
        security = SHARE
        encrypt passwords = Yes
        root directory = /var/ftp/UPLOADS
        password level = 2
        username level = 2
        log file = /var/log/samba/log.%m
        max log size = 50
        lock directory = /usr/local/locks
        guest account = pcguest

[uploads]
        comment = Uploads folder
        path = /var/ftp/UPLOADS
        writeable = Yes
        directory mask = 0775
        inherit permissions = Yes
        guest ok = Yes

Quote:> what do the following mean,

> (in my log.smb file)

> [2001/11/02 10:51:04, 0] lib/util_sock.c:open_socket_in(827)
>   Get_Hostbyname: Unknown host
> [2001/11/02 10:46:59, 0] smbd/oplock.c:open_oplock_ipc(93)
>   open_oplock_ipc: Failed to get local UDP socket for address 100007f.
Error
> was Connection refused

> (in my log.client)
> [2001/11/02 10:34:04, 0] lib/access.c:client_match(144)
>   client_match: address match failing due to invalid character '*' found
in
> token '*' in an allow/deny hosts line.

> It keeps squaking about the allow/deny hosts line yet there's not
reference
> to that in my smb.conf file.

> here is my smb.conf below:

> # Global parameters
> [global]
>         workgroup = HERMES
>         netbios name = SCARUB
>         server string = Samba %v running on FreeBSD 4.4
>         interfaces = rl0 192.168.0.1/24
>         security = SHARE
>         encrypt passwords = Yes
>         root directory = /var/ftp/UPLOADS
>         password level = 2
>         username level = 2
>         log file = /var/log/samba/log.%m
>         max log size = 50
>         lock directory = /usr/local/locks
>         guest account = pcguest

> [uploads]
>         comment = Uploads folder
>         path = /var/ftp/UPLOADS
>         writeable = Yes
>         directory mask = 0775
>         inherit permissions = Yes
>         guest ok = Yes

The samba version you have compiled has TCP wrappers so every time a
connection is going to be made to your pc the files
/etc/hosts.allow
and
/etc/hosts.deny

are considered. If you have an error in this files, then services like
samba, telnet ftp and other will miss-behave. Try commenting all the lines
on hosts.allow and hosts.deny and see if the problem appears. If not you
will have to uncomment one line every time in order to pinpoint the
erroneous one.

Also this problem occurs if the host name has an invalid entry on the DNS
and the hostname is pointed to an IP address, but the IP address has an
invalid PTR record. - Check also your DNS.

"Also this problem occurs if the host name has an invalid entry on the DNS
and the hostname is pointed to an IP address, but the IP address has an
invalid PTR record. - Check also your DNS."

well this server isn't connected the the "net" yet, right now it's sitting
on the local network until I can finish some of the basic configuration.
Would not having this computer online cause samba to misbehave?

I just cleared my log files and re-tried connecting to the file server and I
got the following messages in my log.smb file:

[2001/11/02 12:22:00, 0] lib/util_sock.c:set_socket_options(154)
  Failed to set socket option SO_KEEPALIVE (Error Bad file descriptor)
[2001/11/02 12:22:00, 0] lib/util_sock.c:set_socket_options(154)
  Failed to set socket option TCP_NODELAY (Error Bad file descriptor)
[2001/11/02 12:22:00, 0] lib/util_sock.c:open_socket_in(827)
  Get_Hostbyname: Unknown host scarub
[2001/11/02 12:22:00, 0] smbd/oplock.c:open_oplock_ipc(93)
  open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error
was Connection refused
[2001/11/02 12:22:00, 0] lib/util_sock.c:open_socket_in(827)
  Get_Hostbyname: Unknown host scarub
[2001/11/02 12:22:00, 0] smbd/oplock.c:open_oplock_ipc(93)
  open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error
was Connection refused

Quote:> "Also this problem occurs if the host name has an invalid entry on the DNS
> and the hostname is pointed to an IP address, but the IP address has an
> invalid PTR record. - Check also your DNS."

> well this server isn't connected the the "net" yet, right now it's sitting
> on the local network until I can finish some of the basic configuration.
> Would not having this computer online cause samba to misbehave?

If you haven't setupped a DNS server, then you have to add ALL your machines
of your home network to the /etc/hosts. So whenever a connection to the
SAMBA machine is going to happen, then the client will have a valid name
(pointing to the valid IP) and also an IP corresponding to the same name.
Also check the /etc/hosts.allow and .deny, for any hostnames that don't
resolve correctly, by the name and try the same by IP.

And for the net, your don't need to be connected to the NET to have a DNS
server running. Of course care must be taken how to setup the DNS server,
but you can have one, if you like more flexibility to your home network.

If the setup is correct the samba won't have any problem when it will be
connected to the net.

I figured out the problem...well not really what I did was wipe my smb.conf
file clean and reset all the settings to the exact same as they were before
and it worked...almost sounds like a solution you'd try on a windows machine
;)