Arch Samba - Windows 2008 Domain

Question

I have made the thread bellow thinking i solve my problem giving access on FTMG...but unfortunately nope...
https://bbs.archlinux.org/viewtopic.php?id=107350
My Situation:
3 Servers on Windows 2008 Domain (Example: 192.168.1.1 / 2 / 3)
1.1 - DC
1.2 - Exchange
1.3 - ISA FTMG (Gateway to all servers)
1 Arch Server for Backup (Samba Share PUBLIC) - 192.168.1.4
And my problem is annoying at least, i go to one of my windows 2008 servers and push on explorer \\192.168.1.4\Backup and sometimes fully work without any problem... and another times (let's say 5 minutes after i push again) and:
Network path could not be found
or
xx.xx.xx.xx is not setup to establish a connection on port "File and Print Sharing (SMB)"
BUT FROM THIS WINDOWS 2008 SERVER IT PINGS 192.168.1.4
AND
TRACERT GO DIRECTLY TO 192.168.1.4
And if i try and try eventually it will work again.....can't damn understand what's going on with this.....
On ISA I gave FULL ACCESS to my servers to go where the hell they want and even so......
Thanks in advance for all the help....yep i need it.
Sniff

Answer 1

KimTjik wrote:
I'm sorry I didn't know that this wasn't covered in the Wiki. When I get some time I'll probably add something about. No neither of those links are correct. You already have one DC, a native Windows server, and the second one isn't necessary (you don't need to join the whole Linux workstation to the domain, just the Samba service; the Samba service will with hostname be recognized as a stand-alone server).
In lack of an appropriate Wiki entry Samba's own How-to is better: http://www.samba.org/samba/docs/man/Sam … ember.html
Look for this section: "Joining an NT4-type Domain with Samba-3"
Even that How-to might be confusing since it covers all kinds of configurations at the same time. What you need, as far as I can understand your description, is only what's written in that section.
Start with the strings in smb.conf for domain, password server (in your case probably the DC itself) and  security set to domain. Restart samba and the you need to know an administrator account (user and password) and fill it in to the command example shown, e g "net rpc join -S DOMPDC -UAdministrator%password". If everything works you should get confirmation about it. You could also double-check the AD on the DC and see if the Samba server is added.
See if you get this to work.
OK, sorry for the delay in my answer but i was traveling and couldn't test the above in the production environment.
I have add the backup server to the domain successfully but that was not the problem.
Now i have full details and maybe you could give your opinion:
                                         FTMG (Forefront Threat Management Gateway)
                                                               SWITCH LAYER 3
                  SERVER BACKUP----------------------SERVERDC---------------------------SERVEREXCHANGE
THE PROBLEM is that if the DC have a share or exchange, everything works ok \\dc or \\exchange, but if you try to connect to the share archserver the connection drop quite often \\archserver
WHY? Because after some trace in FTMG, the microsoft firewall consider that the archserver is doing spoofing, yes is on the same network as all servers, same domain as above help, trusted...etc.
SOLUTION? First i give permissions on the firewall to the archserver (ALLOW ALL /PROTOCOLS ETC), but even so the FTMG was intercepting all the requests to the archserver and still consider him spoofing...odd enough no??!! By the way the FTMG Server control all network, is the gateway to all servers and switching.
Are you thinking to change the gateway to archserver or just don't put any....yep same result, FTMG catch archserver still.
I gave up and come with my actual solution (VLAN or BACKUP NETWORK), all servers with a extra ethernet card dedicated to the backup network or vlan just to backup without the firewall going there to trace anything.
And that's it....
But my question to you all is, everytime that we have a linux server (share) together with FTMG in same network do you have the same result, it seems to me like FTMG have something like: IT'S LINUX / GET BLOCKED.
Thanks for your help and patience regarding my answer.
TD (Sniffer)