Hello all, samba-2.2.3a Solaris 2.6 I'm trying to get my samba-2.2-3a server up and running. I can get smbd to start just find. However, when I try to start nmbd from swat I get the following in the log.nmbd file. Nmbd is running on the system however, it says that it is not running in swat. What is going on here and better yet how to correct it? Thanks in Advance George Cebulka Sr Systems Administrator U.S Steel [2002/03/22 16:04:25, 0] nmbd/nmbd.c:main(783) Netbios nameserver version 2.2.3a started. Copyright Andrew Tridgell and the Samba Team 1994-2002 [2002/03/22 16:04:25, 1] lib/debug.c:debug_message(250) INFO: Debug class all level = 1 (pid 9736 from pid 9736) [2002/03/22 16:04:25, 0] nmbd/nmbd_nameregister.c:register_name_response(109) register_name_response: server at IP 170.191.20.33 rejected our name registration of AZURE<20> with error code 6. [2002/03/22 16:04:25, 0] nmbd/nmbd_mynames.c:my_name_register_failed(40) my_name_register_failed: Failed to register my name AZURE<20> on subnet 170.191.20.27. [2002/03/22 16:04:25, 0] nmbd/nmbd_namelistdb.c:standard_fail_register(290) standard_fail_register: Failed to register/refresh name AZURE<20> on subnet 170.191.20.27 [2002/03/22 16:04:25, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237) find_response_record: response packet id 5559 received with no matching record. [2002/03/22 16:04:25, 0] nmbd/nmbd_nameregister.c:register_name_response(109) register_name_response: server at IP 170.191.20.27 rejected our name registration of AZURE<20> with error code 6. [2002/03/22 16:04:25, 0] nmbd/nmbd_mynames.c:my_name_register_failed(40) my_name_register_failed: Failed to register my name AZURE<20> on subnet 170.191.21.11. [2002/03/22 16:04:25, 0] nmbd/nmbd_namelistdb.c:standard_fail_register(290) standard_fail_register: Failed to register/refresh name AZURE<20> on subnet 170.191.21.11 [2002/03/22 16:04:25, 0] nmbd/nmbd_nameregister.c:register_name_response(109) register_name_response: server at IP 170.191.20.27 rejected our name registration of AZURE<00> with error code 6. [2002/03/22 16:04:25, 0] nmbd/nmbd_mynames.c:my_name_register_failed(40) my_name_register_failed: Failed to register my name AZURE<00> on subnet 170.191.20.27. [2002/03/22 16:04:25, 0] nmbd/nmbd_namelistdb.c:standard_fail_register(290) standard_fail_register: Failed to register/refresh name AZURE<00> on subnet 170.191.20.27 [2002/03/22 16:04:25, 0] nmbd/nmbd_nameregister.c:register_name_response(109) register_name_response: server at IP 170.191.20.27 rejected our name registration of AZURE<00> with error code 6. [2002/03/22 16:04:25, 0] nmbd/nmbd_mynames.c:my_name_register_failed(40) my_name_register_failed: Failed to register my name AZURE<00> on subnet 170.191.21.11. [2002/03/22 16:04:25, 0] nmbd/nmbd_namelistdb.c:standard_fail_register(290) standard_fail_register: Failed to register/refresh name AZURE<00> on subnet 170.191.21.11 [2002/03/22 16:04:25, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237) find_response_record: response packet id 5561 received with no matching record. [2002/03/22 16:04:25, 0] nmbd/nmbd_nameregister.c:register_name_response(109) register_name_response: server at IP 170.191.20.27 rejected our name registration of AZURE<20> with error code 6. [2002/03/22 16:04:25, 0] nmbd/nmbd_mynames.c:my_name_register_failed(40) my_name_register_failed: Failed to register my name AZURE<20> on subnet 170.191.20.33. [2002/03/22 16:04:25, 0] nmbd/nmbd_namelistdb.c:standard_fail_register(290) standard_fail_register: Failed to register/refresh name AZURE<20> on subnet 170.191.20.33 [2002/03/22 16:04:25, 0] nmbd/nmbd_nameregister.c:register_name_response(109) register_name_response: server at IP 170.191.20.27 rejected our name registration of AZURE<00> with error code 6. [2002/03/22 16:04:25, 0] nmbd/nmbd_mynames.c:my_name_register_failed(40) my_name_register_failed: Failed to register my name AZURE<00> on subnet 170.191.20.33. [2002/03/22 16:04:25, 0] nmbd/nmbd_namelistdb.c:standard_fail_register(290) standard_fail_register: Failed to register/refresh name AZURE<00> on subnet 170.191.20.33 [2002/03/22 16:04:25, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237) find_response_record: response packet id 5567 received with no matching record. [2002/03/22 16:04:25, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237) find_response_record: response packet id 5569 received with no matching record. [2002/03/22 16:04:25, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237) find_response_record: response packet id 5575 received with no matching record. [2002/03/22 16:04:25, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237) find_response_record: response packet id 5577 received with no matching record. [2002/03/22 16:04:29, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237) find_response_record: response packet id 5562 received with no matching record. [2002/03/22 16:04:29, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237) find_response_record: response packet id 5563 received with no matching record. [2002/03/22 16:04:29, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237) find_response_record: response packet id 5564 received with no matching record. [2002/03/22 16:04:29, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237) find_response_record: response packet id 5568 received with no matching record. [2002/03/22 16:04:29, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237) find_response_record: response packet id 5570 received with no matching record. [2002/03/22 16:04:29, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237) find_response_record: response packet id 5571 received with no matching record. [2002/03/22 16:04:29, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237) find_response_record: response packet id 5572 received with no matching record. [2002/03/22 16:04:29, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237) find_response_record: response packet id 5576 received with no matching record. [2002/03/22 16:04:29, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237) find_response_record: response packet id 5578 received with no matching record. [2002/03/22 16:04:29, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237) find_response_record: response packet id 5579 received with no matching record. [2002/03/22 16:04:29, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237) find_response_record: response packet id 5580 received with no matching record. [2002/03/22 16:06:08, 0] nmbd/nmbd.c:sig_term(63) Got SIGTERM: going down...