Quote:
Originally posted by ppuru
can you try the commands below to ascertain whether smbd and nmbd are indeed running
Code:
ps -C smbd
ps -C nmbd
If they come up with nothing, you can be assured the services are indeed down.
|
SUSEBOX:~ # ps -C smbd
PID TTY TIME CMD
2653 ? 00:00:00 smbd
SUSEBOX:~ # ps -C nmbd
PID TTY TIME CMD
1942 ? 00:00:00 nmbd
1943 ? 00:00:00 nmbd
i guess they are running?
Quote:
check the logs (messages and log.smb and log.nmb).
|
here's a bit from
/var/log/messages:
Jul 13 04:03:46 SUSEBOX nmbd[1942]: [2004/07/13 04:03:46, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_wins(341)
Jul 13 04:03:46 SUSEBOX nmbd[1942]: become_domain_master_browser_wins: querying WINS server from IP 127.0.0.1 for domain master browser name MSHOME<1b> on workgroup MSHOME
Jul 13 04:03:47 SUSEBOX nmbd[1942]: [2004/07/13 04:03:47, 0] nmbd/nmbd_become_dmb.c:become_domain_master_query_success(225)
Jul 13 04:03:47 SUSEBOX nmbd[1942]: become_domain_master_query_success:
Jul 13 04:03:47 SUSEBOX nmbd[1942]: There is already a domain master browser at IP 24.88.127.149 for workgroup MSHOME registered on subnet UNICAST_SUBNET.
Jul 13 04:04:08 SUSEBOX nmbd[1942]: [2004/07/13 04:04:08, 0] nmbd/nmbd_browsesync.c:domain_master_node_status_fail(247)
Jul 13 04:04:08 SUSEBOX nmbd[1942]: domain_master_node_status_fail:
Jul 13 04:04:08 SUSEBOX nmbd[1942]: Doing a node status request to the domain master browser
Jul 13 04:04:08 SUSEBOX nmbd[1942]: for workgroup MSHOME at IP 24.88.127.149 failed.
Jul 13 04:04:08 SUSEBOX nmbd[1942]: Cannot sync browser lists.
/var/log/samba/log.smbd:
[2004/07/13 03:20:54, 0] smbd/server.c:main(757)
smbd version 3.0.4-SUSE started.
Copyright Andrew Tridgell and the Samba Team 1992-2004
[2004/07/13 03:20:57, 0] lib/pidfile.c
idfile_create(84)
ERROR: smbd is already running. File /var/run/samba/smbd.pid exists and process id 4076 is running.
[2004/07/13 03:24:36, 0] smbd/server.c:main(757)
smbd version 3.0.4-SUSE started.
Copyright Andrew Tridgell and the Samba Team 1992-2004
[2004/07/13 03:24:37, 0] smbd/server.c:main(791)
standard input is not a socket, assuming -D option
[2004/07/13 03:24:38, 0] lib/pidfile.c
idfile_create(84)
ERROR: smbd is already running. File /var/run/samba/smbd.pid exists and process id 4076 is running.
[2004/07/13 03:33:13, 0] smbd/server.c:main(757)
smbd version 3.0.4-SUSE started.
Copyright Andrew Tridgell and the Samba Team 1992-2004
[2004/07/13 03:33:13, 0] printing/print_cups.c:cups_printer_fn(108)
Unable to connect to CUPS server localhost - Connection refused
/var/log/samba/log.nmbd contains the same nmbd info. from messages.
Quote:
Are tcpwrappers blocking connections to smbd and nmbd (hosts.allow, hosts.deny)
|
i can't competently answer the question, but here's a line out of smb.conf:
hosts allow = 24.88.126.16, 24.88.127.149
hosts deny =
the second address is this machine. do i need to specify subnets too?
Quote:
Hope smbd and nmbd are configured to listen on the subnet you are on (the interfaces and hosts allow parameters)
|
again, from smb.conf:
interfaces = eth0, lo
all of this info, especially the logs, probably means more to others than it does me. any ideas?