This machine that's having these issues was the one I've been using since March. It went from 1.0.x to 1.1.x to 1.2 and just more recently to 1.2.3 because I still had the old repository in sources.list and didn't know it was changed.
Just for kicks, I tried something else related to the most-recent samba issue:
root@main:~# /etc/init.d/samba restart
* Stopping Samba daemons [ OK ]
* Starting Samba daemons [ OK ]
root@main:~# /etc/init.d/ebox samba restart
* Restarting eBox module: samba [fail]
Unknown error at EBox::Ldap::modifyAttribute unrecognized objectClass 'eboxEgwAccount'
root@main:~#
2010/01/09 06:18:00 ERROR> EventDaemon.pm:465 EBox::EventDaemon::__ANON__ - Server mm.internal.ebox-controlcenter.com not found via DNS server 10.200.0.4
2010/01/20 01:45:11 ERROR> Sudo.pm:190 EBox::Sudo::_rootError - root command cat /var/run/samba/smbd.pid failed.
2010/01/20 01:45:11 ERROR> PgDBEngine.pm:95 EBox::PgDBEngine::_connect - Connection DB Error: FATAL: Ident authentication failed for user "ebox"
Those are some unique errors I pulled out really quick. My assumption is, when I changed Postgre 8.4 to use the default port 5432 port, it caused these issues whereas before it was on 5433. Maybe it was wanting to connect to the old database? Did eBox use an older Postgres before? I don't really know how to use Postgres, but I do know how to login if I need to check. Anything recent though is unrelated to the eth1 issue though.