![]() Policy: all (internal) to (WAN1) all ports any time without protection profile (NAT checked)Īnd now, with only one policy we could figure that we would reach internet from my WS2003. Internal interface/ WAN1 interface / Gateway But the server can not initialize any SMTP session to the internet, so it can not send any mail. From internet I can reach these server with POP and SMTP. this could explain that " also" is not able to connect to the PDC (that is in the same subnet). But the WS2003 that has a mail server running inside is not able to send mail, to browse any web page, etc. The fact is that when I connect the F60B I can reach from internet the two virtual IP I' ve defined above. : Broadcom NetXtreme Gĭirección fÃsica. : 255.255.255.0Īdaptador Ethernet VMware Network Adapter VMnet1:ĭirección fÃsica. : VMware Virtual Etherĭirección fÃsica. Lista de búsqueda sufijo DNS : RETANET.RETANETĪdaptador Ethernet VMware Network Adapter VMnet8:ĭescripción. So I hace disconnected the F60B waiting for a solution to my problem.Ĭ:\Documents and Settings\Administrador.RETANET.000>ipc I wonder if the could be related to the xoops / moodle way to serve pages: they redirect to the url, and perhaps the firewall blocks connections from internal to the external IP. ![]() Web server runs xoops, moodle, and phplist. ![]() The other web and mail server were running fine. ![]() But I had to get back to the becouse the virtualizaded web server (192.168.1.8) couldn' t be reached from internet. Yesterday I tried to do a " hot" replace (the two boxes were running, the " same" configuration. Well, the Fortigate F60B is going to replace a checkpoint 500. There' s a particular fact: the second server is a virtualized one, that is hosted in the first one, sharing the same NIC -bridged mode. I' ve have the following configuration in my F60B: ![]()
0 Comments
Leave a Reply. |