Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 298
  • Last Modified:

Running Exchange Server and

We have a small office of 6 people who want to run an Exchange 2010 Server on Windows 2012 server alongside another Windows 2012 server that is the domain controller and running active directory.
In normal environments we of course have and external Static IP that points towards a Comcast Business internet modem and then our routers behind that.  In this case they refuse to deal with Comcast Cable because they hate them and they have residential Verizon FIOS TV and internet in the building already.  Plus the internet speed they have of 150/65 now would be extremely expensive for them to do as Business with static.

Is there any safe way of running Exchange, Remote Web Workplace etc. without an external static public IP address?  I know we could use the dynamic one that Verizon assigned initially and if it changes assume we would have to make the appropriate changes in the entire network each time it changed.

Any way around this??
Thanks
0
to2007
Asked:
to2007
  • 2
2 Solutions
 
jss1199Commented:
Not recommended, but certiainly possible.  Use a DDNS provider such as dyndns.com so that DNS is update when your IP changes dynamically.
0
 
to2007Author Commented:
Never used one before.  Would they provide some form of IP or naming convention to point MX and A records to?
0
 
jss1199Commented:
The way dyndns works is that there is an application that runs where your remote computer is that will update your dyndns account and let it know what your IP address is.

Alot of routers will have that application built into it. If not there is an application you can run on your computer that is there
0
 
Cliff GaliherCommented:
Verizon's terms of service don't allow you to run servers on residential accounts. So your client is putting you in the awkward position of knowingly breaking the law. I'd simply refuse. Also, MOST Verizon service areas (and all FIOS areas I am aware of) actively block port 25 on their end, so email delivery would fail, even with a dynamic DNS setup. There are ways around that, but again, it only is digging deeper to circumvent the law.

perhaps a hosted exchange setup may be more to their liking. But realistically they may still be breaking the Verizon terms of service by using a residential account primarily for business purposes. The "right" solution legally is to pay for business service.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now