(E-Mail Removed) wrote:
> Lanwench [MVP - Exchange] :
>> (E-Mail Removed) wrote:
>>> I`ve an interface that gets IP and gateway from a DHCP on a network
>>
>> This is on a workstation, I hope... not on your server. Servers
>> should have static IPs.
>>
>>> and the same interface has an PPPoE connection that assigns a real
>>> IP address and a real gateway.
>>
>> I'm confused by the use of "on the same interface".
>>
>> I'm not sure I understand your configuration or question, but
>> basically, don't use PPPoE on a network interface ...have a
>> router/firewall appliance handle it. I'm also not a fan of
>> multihomed DCs; if you're using ISA, you need two NICs, but if you
>> aren't, you need only one (with a decent firewall appliance).
>>
>
> So more detailed describtion goes as follows :
> This is THE server that has an NIC with NO static addresses assigned.
This is not good. Your server needs a static IP.
> the ISP works with 2 DHCP servers,
It doesn't matter what your ISP does.....
> one that gives my NIC an internal
> ip address smth like 192.168.0.183 and by this NIC I make a PPPoE
> connection that gives me the real IP address.
I don't follow, but you need to get rid of that configuration anyway. I'm
not sure how you got here, but it's not going to work.
> so there are two connections both with Ip addresses and GW and so
> on .. both dynamic (auto configured).
> the goal is to connect (web,ftp) to the server from internet by using
> the real ip address.
Yes, which is why you need to fix your configuration.....
> so any of this settings is applicable for changes cause ist the ISP
> that works this way ..
You need a router/firewall between your ISP's modem/router and your network.
Your ISP's modem/router should not be doing NAT. It can do DHCP and assign a
dynamic address to the WAN interface of your router/firewall.....and then
your router/firewall will do NAT between the public and private networks.
Get rid of whatever PPPoE stuff you've got now - get the router/firewall
appliance connected, and run the CEICW. Your workstations & server will
point at the static LAN IP of the router/firewall. Your server will have a
static IP on your network. Unless you are using ISA, I suggest that you use
only one NIC on your server.
When you have all of this working, set up the port forwarding rules in your
router/firewall - 25 for SMTP, 443 for HTTPS, 4125 for RWW/Remote Desktop.
Forward them all to the LAN IP of your server. From the outside, you can
then access your server using your public IP address (that which is set in
the WAN interface on your router/firewall).
If you have a dynamic public IP, check out
www.dyndns.com - you'll want a
Dynamic DNS account. I like to use the Dyndns updater software running as a
Windows service on the server, instead of having it handled by the
router/firewall - this is recommended by DynDNS. There are other options,
such as
www.no-ip.com, and so forth.
For firewall hardware, I like SonicWALLs, but even a simple NetGear/Linksys
would accomplish this, although less securely.