General discussion

Locked

Static to DHCP with Exchange 5.5

By hindsite ·
Our company (22 users - 5 TCP/IP printers) has run out of static ips. We are getting DSL from a provider who can not "expand" our ip block. What is the best course to take? What headaches will I have by switching to DHCP? The Exchange server is probably my biggest worry.

Any suggestions (constructive!) would be much appreciated.

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Static to DHCP with Exchange 5.5

by Cactus Pete In reply to Static to DHCP with Excha ...

I recommend a firewall and NAT. The firewall and only other public servers need the IPs from your provider, then you can NAT addresses to your heart's content within your own network.

It sounds like you'll want to get a consultant to help you dothis the first time, and perhaps you can just take a course on networking to manage this in the future by yourself.

Collapse -

Static to DHCP with Exchange 5.5

by hindsite In reply to Static to DHCP with Excha ...

Poster rated this answer

Collapse -

Static to DHCP with Exchange 5.5

by LordInfidel In reply to Static to DHCP with Excha ...

Additional-

Exchange server must have a static IP.

It can be pvt, but it must be static.

As poster #1 said, you will need to do nat and port forwarding.

Essentially you just need tcp 25 forwarded to the exchange server. So any request that comes thru to your public IP on tcp 25 automatically goes to your exch srvr.

Collapse -

Static to DHCP with Exchange 5.5

by hindsite In reply to Static to DHCP with Excha ...

Poster rated this answer

Collapse -

Static to DHCP with Exchange 5.5

by hindsite In reply to Static to DHCP with Excha ...

This question was closed by the author

Back to Networks Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums