0 votes

I have recently created a new ClearOS 6.3 server for our Windows systems and have just (within the last 2 days) run into a problem setting up PCs on the domain. I can join the domain, but whenever I go to log in using a domain user, I get "The system cannot log you on now because the domain MCMS is not available". Prior to last night, I had no problems doing this at all.

The only change between Friday night and last night (that I knowingly performed) was physically installing the server in a server rack (previously it was simply sitting on a filing cabinet in the same location).

From my samba log for the machine in question, I grabbed the following from my login attempt:

[2012/09/02 21:37:47.581512, 0] lib/fault.c:48(fault_report)
INTERNAL ERROR: Signal 11 in pid 2875 (3.6.5-1.v6)
Please read the Trouble-Shooting section of the Samba3-HOWTO
[2012/09/02 21:37:47.581567, 0] lib/fault.c:50(fault_report)

[2012/09/02 21:37:47.581599, 0] lib/fault.c:51(fault_report)
[2012/09/02 21:37:47.581622, 0] lib/util.c:1117(smb_panic)
PANIC (pid 2875): internal error
[2012/09/02 21:37:47.585601, 0] lib/util.c:1221(log_stack_trace)
BACKTRACE: 26 stack frames:
#0 smbd(log_stack_trace+0x1a) [0x7f845db8460a]
#1 smbd(smb_panic+0x2b) [0x7f845db846db]
#2 smbd(+0x413184) [0x7f845db75184]
#3 /lib64/ [0x7f845a508920]
#4 smbd(copy_serverinfo+0x1a) [0x7f845dbd8a4a]
#5 smbd(make_server_info_guest+0x10) [0x7f845dbd8c00]
#6 smbd(+0x476775) [0x7f845dbd8775]
#7 smbd(+0x471151) [0x7f845dbd3151]
#8 smbd(+0x47de4c) [0x7f845dbdfe4c]
#9 smbd(ntlmssp_server_auth+0x2e1) [0x7f845d9454d1]
#10 smbd(ntlmssp_update+0x1ca) [0x7f845d93b8fa]
#11 smbd(auth_ntlmssp_update+0x16) [0x7f845d93ccc6]
#12 smbd(+0x13af4e) [0x7f845d89cf4e]
#13 smbd(reply_sesssetup_and_X+0x7f6) [0x7f845d89e196]
#14 smbd(+0x177c94) [0x7f845d8d9c94]
#15 smbd(+0x1780ab) [0x7f845d8da0ab]
#16 smbd(+0x1784c5) [0x7f845d8da4c5]
#17 smbd(run_events_poll+0x376) [0x7f845db93956]
#18 smbd(smbd_process+0x86d) [0x7f845d8d801d]
#19 smbd(+0x68fb5f) [0x7f845ddf1b5f]
#20 smbd(run_events_poll+0x376) [0x7f845db93956]
#21 smbd(+0x431dff) [0x7f845db93dff]
#22 smbd(_tevent_loop_once+0x90) [0x7f845db94180]
#23 smbd(main+0xeeb) [0x7f845ddf2f0b]
#24 /lib64/ [0x7f845a4f4cdd]
#25 smbd(+0xf49f9) [0x7f845d8569f9]
[2012/09/02 21:37:47.585887, 0] lib/fault.c:372(dump_core)
dumping core in /var/log/samba/cores/smbd

As this is for a school and we start on Tuesday, I need to get this resolved within 24 hours (I do the IT work at night, so I have until about 2 a.m. Tuesday morning to resolve this.

Please help me out,
Monday, September 03 2012, 02:51 AM
Share this post:
Responses (3)
  • Accepted Answer

    Tuesday, September 04 2012, 12:59 AM - #Permalink
    0 votes
    Sorry. Had some family stuff and sleep to catch up on today. After a server reboot last night as I left, it is working fine today. Not sure what was the problem.

    Thanks for the advice.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, September 04 2012, 12:46 AM - #Permalink
    0 votes
    The reply is currently minimized Show
  • Accepted Answer

    Monday, September 03 2012, 05:56 AM - #Permalink
    0 votes
    Make sure that your naming is working well. In particular, you should be able to ping the server by the short name. Also, you should be running WINS and be on the same subnet as the server.

    Run the following from command line of the workstation the following:

    nbtstat -A

    (where is the IP address of your server). If it doesn't return entries then your NBT is not communicating.
    The reply is currently minimized Show
Your Reply