Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Hi,
I was wondering if anyone could help me with this. I am running a wireless network. The main server/router is running Windows Server 2003. I have RRAS and DHCP enabled and all is working fine.
I have a person on the LAN side of my network that would like a Static WAN IP to run a mail server on. DHCP has already assigned an IP for the LAN side and he can surf the net just fine. So the question, how can I setup my system to assign a Public WAN IP to this person or route traffic so the world sees him as the WAN IP I assign and not the WIN 2003 NIC IP?
Thanks for any help!
Dean

This mail server would have to have an internet facing nic. Your isp would have to put a mx record in their dns to point everyone via the internet to your mail server. You would need a lan facing nic to access the mail server from the lan.
Really might want to review your security risks.
Imagine the power if you knew how to internet search

The Mail Server will be on the other end of a wireless link thats behind my 2003 Server. The only actual Internet facing nic is the one on the server.
The clients internet facing NIC is actually on the LAN side of my network, he gets his internet from RRAS and DHCP installed on the server.
I wonder if RIPv2 would do this?

How do you think you will get a public ip to route thru your server to private ip on the wireless and then back to public on the mail server?
You would need a router between your lan and the mail server.
What would the point be to have public ip on the mail server when it would be behind private ip?
Imagine the power if you knew how to internet search

>How do you think you will get a public ip to route thru
>your server to private ip on the wireless and then back
>to public on the mail server?Well that’s kind of what I am asking, How do you do that?
>What would the point be to have public ip on the mail >server when it would be behind private ip?
On a Private LAN IP the world will not be able to see the mail server. It would require a Public WAN IP address that can be assigned in DNS. When the world sends data to the WAN IP I want it routed to the Private IP the mail server is on.

i might be missing something here. is this not just a case of forwarding ports for you mail server ??

In order for the mail server to work and for mail to be routed to it it has to have a static IP address that can be listed in DNS.

usually you have a registed domain name associated with a ip address. You would at your router forward smtp [port 25] and pop3 [port 110] ports to the mailservers ip which is a lan [private] ip not a public ip. it takes having your isp put a mx record in their dns server so mail is forwarded to your domains ip.
mail servers do not have to have static ips. Simple google search on mailserver on dynamic ip will show you that.
You wrote:
"When the world sends data to the WAN IP I want it routed to the Private IP the mail server is on."That is what is descibed above. After all when was the last time you sent an email to an ip address?
Imagine the power if you knew how to internet search

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |