dances1960
asked on
Only on Static IP
Hi
The office has been sold to another company and we are now tenants, they’ve pulled the ISP we had with 5 static IP addresses and have now issued us with just one IP address which is shared with other companies within the building.
We have an exchange server and Vpn links to other offices, what choices would I have with this? Is there a work around?
Thank you in advance of any help.
The office has been sold to another company and we are now tenants, they’ve pulled the ISP we had with 5 static IP addresses and have now issued us with just one IP address which is shared with other companies within the building.
We have an exchange server and Vpn links to other offices, what choices would I have with this? Is there a work around?
Thank you in advance of any help.
Lee W, MVP
Get your own internet - cable, fios, metro ethernet. Or have management talk to the new owners.
In short: No choices, no workarounds.
The only thing: Any kind of VPN into your parent companies network and use their known, non-shared exit IP's.
The only thing: Any kind of VPN into your parent companies network and use their known, non-shared exit IP's.
You can connect exchange server using a VPN connection to another office, but there are some network things that you need to take care off.
As you know exchange requires a static IP for connection i.e. a public IP.
But I got a customer who had the same situation and he wanted to connect exchange server using VPN and use another office network for temporary purpose since he was going to get public IP for exchange in 1 week.
So basically it was like below:
Fixed Public IP not there (Exchange Server) .
So client was connecting VPN using PPTP CLIENT IP and when he tries to connect exchange server over VPN he would get error as below:
421 4.3.2 Service not available, closing transmission channel
We noticed when we connected exchange server using VPN the LAN IP would change to VPN IP i.e. 192.168.1.200
So we simply added this IP i.e. 192.168.1.200 in the send connector under "use these local IP to receive emails".
As you know exchange requires a static IP for connection i.e. a public IP.
But I got a customer who had the same situation and he wanted to connect exchange server using VPN and use another office network for temporary purpose since he was going to get public IP for exchange in 1 week.
So basically it was like below:
Fixed Public IP not there (Exchange Server) .
So client was connecting VPN using PPTP CLIENT IP and when he tries to connect exchange server over VPN he would get error as below:
421 4.3.2 Service not available, closing transmission channel
We noticed when we connected exchange server using VPN the LAN IP would change to VPN IP i.e. 192.168.1.200
So we simply added this IP i.e. 192.168.1.200 in the send connector under "use these local IP to receive emails".
Maybe a good time to finally join the cloud and go Office 365 (or only plain Exchange Online)
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.