Exchange 2016 Receive connectors

%3CLINGO-SUB%20id%3D%22lingo-sub-3280089%22%20slang%3D%22en-US%22%3EExchange%202016%20Receive%20connectors%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3280089%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20been%20migrating%20from%20Ex2010%20to%20Ex2016.%20The%20new%20Exchange%202016%20server%20has%20had%20our%20public%20SSL%20certificate%20installed%20for%2C%20let's%20call%20it%20'email.company.com'.%20Recently%20I%20noticed%20that%20the%20Default%20Frontend%20has%20the%20internal%20server%20name%3A%20'email.inside.net'.%20I%20cannot%20change%20it%20as%20Exchange%202016%20won't%20let%20me.%20From%20what%20I've%20read%20this%20can't%20and%20shouldn't%20be%20changed.%20So%20I%20go%20to%20create%20a%20new%20connector.%202016%20won't%20let%20me%20giving%20me%20an%20error%20that%20basically%20says%20it%20overlaps%20with%20the%20Default%20Frontend%20connector.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELast%20night%20I%20attempted%20to%20create%20a%20new%20connector%20and%20fashion%20the%20two%20connectors%20like%20the%20ones%20on%20the%20Exchange%202010%20servers.%20Meaning%20the%20Default%202010%20connectors%20cover%20all%20internal%20addresses%20and%20the%20Internet%20connector%20covers%20all%20public%20Internet%20addressing.%20However%20it%20doesn't%20like%20my%20addressing%20of%3A%26nbsp%3B0.0.0.0-9.255.255.255%20to%20cover%20everything%20before%20the%20private%2010%20net.%20It%20tells%20me%20this%20is%20invalid%20which%20is%20strange%20considering%20the%20default%20'everything%20IPv4'%20is%20notated%20%220.0.0.0-255.255.255.255%22.%20How%20is%20my%20IP%20address%20range%20invalid%3F%20How%20am%20I%20supposed%20to%20address%20this%20connector%3F%20Nothing%20I%20can%20find%20shows%20how%20to%20cover%20a%20large%20range%20of%20IP%20addresses%20like%20this.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEdit1%3A%20No%20matter%20how%20I%20annotate%20the%20IP%20addressing%20I%20cannot%20add%20entire%20subnets%20to%20this%20connector.%20I%20can't%20add%200.0.0.0%2F5%20or%200.0.0.0%20248.8.8.8.%20Neither%20of%20them%20work.%20The%20only%20thing%20that%20works%20is%26nbsp%3B0.0.0.0-255.255.255.255%20for%20ALL%20IPv4%20or%20nothing.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3280089%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Contributor

We have been migrating from Ex2010 to Ex2016. The new Exchange 2016 server has had our public SSL certificate installed for, let's call it 'email.company.com'. Recently I noticed that the Default Frontend has the internal server name: 'email.inside.net'. I cannot change it as Exchange 2016 won't let me. From what I've read this can't and shouldn't be changed. So I go to create a new connector. 2016 won't let me giving me an error that basically says it overlaps with the Default Frontend connector.

 

Last night I attempted to create a new connector and fashion the two connectors like the ones on the Exchange 2010 servers. Meaning the Default 2010 connectors cover all internal addresses and the Internet connector covers all public Internet addressing. However it doesn't like my addressing of: 0.0.0.0-9.255.255.255 to cover everything before the private 10 net. It tells me this is invalid which is strange considering the default 'everything IPv4' is notated "0.0.0.0-255.255.255.255". How is my IP address range invalid? How am I supposed to address this connector? Nothing I can find shows how to cover a large range of IP addresses like this.

 

Edit1: No matter how I annotate the IP addressing I cannot add entire subnets to this connector. I can't add 0.0.0.0/5 or 0.0.0.0 248.8.8.8. Neither of them work. The only thing that works is 0.0.0.0-255.255.255.255 for ALL IPv4 or nothing.

0 Replies