Topics created by ullawolf1

Samba mailing list post fell on deaf ears (or blind eyes I guess 🙂

But!

THIS. IS. SOLVED!

(or at least worked-around)

So, as it was appearing to be, it was a timing issue.

Fileserver share was opened by Nitrobit client pre-logon screen, and was held opened for a bit (by WIn7, or Samba, not sure but suspect a change in upgraded Samba version to be the cause), then FOG Service tries to immediately join domain, join fails due to the “multiple connections…” issue.

Solution?

Set the FOG Service on Win7 to “Start delayed” \0/

This will cause it to start “approximately 2 minutes after system boots.”

I have tested this several times (10+) on the Win7 VM that I set up and, while it may take a little longer (up to 4 about additional mins), the Windows 7 workstation with the Nitrobit client installed on it goes throught the rename, reboot, domain join, reboot-to-domain-logon process flawlessly now - every time!

So my question is, I wonder what the Samba > v3.6.16 smb.conf option might be to alleviate this without having to modify the FOG Service settings?

Also, I wonder if the FOG Service install could be modified to either automatically set the service to “Delayed Start” or ask during the install:

“Do you have any services that connect to the Domain Controller pre-logon screen?” If yes, then set for delayed start, if no, no delayed start.

Possible other option is what I mentioned previously: FOG Service forcefully disconnects any server connections just prior to join attempt.

It is 11:30pm on a Friday night, and I am so done with this. Happy it is solved. Now to notify our client so everyone can rejoice!

🙂

Thanks Tom, thanks BPSTravis!

Whoops… Now it is 11:30AM… Forgot to click “Post Reply” before walking out of office triumphantly. heh 🙂

Thanks for your reply. The problem appears during unicast.
But It wasn’t a switch problem but a problem with the client Broadcom NIC driver in the kernel. I compiled a new kernel with a different NIC driver and everything works now.