Jump to content

NLB Exchange 2010 connectivity issues.

Hello guys, I'm having a bit of an issue. I've got 2 Exchange servers 2010 OS is 2012 Datacenter on both servers. Running them on ESXi 6.0. Server one has an IP of 192.168.1.20, second server has an IP of 192.168.1.21. Both set for multicast. The issues i'm having is trying to access it from outside my network. The IP address for the cluster is 192.168.1.245. I've ported 25, 443, 80 and 587 to the IP of 192.168.1.245. I've checked all port forwarding sites and they tell me that all the ports are open. 

 

Cheers.

 

@leadeater do you have any ideas?

CPU: AMD Ryzen 5 5600X | CPU Cooler: Stock AMD Cooler | Motherboard: Asus ROG STRIX B550-F GAMING (WI-FI) | RAM: Corsair Vengeance LPX 16 GB (2 x 8 GB) DDR4-3000 CL16 | GPU: Nvidia GTX 1060 6GB Zotac Mini | Case: K280 Case | PSU: Cooler Master B600 Power supply | SSD: 1TB  | HDDs: 1x 250GB & 1x 1TB WD Blue | Monitors: 24" Acer S240HLBID + 24" Samsung  | OS: Win 10 Pro

 

Audio: Behringer Q802USB Xenyx 8 Input Mixer |  U-PHORIA UMC204HD | Behringer XM8500 Dynamic Cardioid Vocal Microphone | Sound Blaster Audigy Fx PCI-E card.

 

Home Lab:  Lenovo ThinkCenter M82 ESXi 6.7 | Lenovo M93 Tiny Exchange 2019 | TP-LINK TL-SG1024D 24-Port Gigabit | Cisco ASA 5506 firewall  | Cisco Catalyst 3750 Gigabit Switch | Cisco 2960C-LL | HP MicroServer G8 NAS | Custom built SCCM Server.

 

 

Link to comment
Share on other sites

Link to post
Share on other sites

8 minutes ago, Abdul201588 said:

Hello guys, I'm having a bit of an issue. I've got 2 Exchange servers 2010 OS is 2012 Datacenter on both servers. Running them on ESXi 6.0. Server one has an IP of 192.168.1.20, second server has an IP of 192.168.1.21. Both set for multicast. The issues i'm having is trying to access it from outside my network. The IP address for the cluster is 192.168.1.245. I've ported 25, 443, 80 and 587 to the IP of 192.168.1.245. I've checked all port forwarding sites and they tell me that all the ports are open. 

 

Cheers.

 

@leadeater do you have any ideas?

My guess is it has to do with the reply/source address the servers are using when responding. Not sure, would need more details on how it's not working and I'd run some wireshark traces to see what the traffic looks like when testing.

Link to comment
Share on other sites

Link to post
Share on other sites

21 minutes ago, leadeater said:

My guess is it has to do with the reply/source address the servers are using when responding. Not sure, would need more details on how it's not working and I'd run some wireshark traces to see what the traffic looks like when testing.

I've taken a look, it seems to connected to the secondary server. I'll check it out. 

CPU: AMD Ryzen 5 5600X | CPU Cooler: Stock AMD Cooler | Motherboard: Asus ROG STRIX B550-F GAMING (WI-FI) | RAM: Corsair Vengeance LPX 16 GB (2 x 8 GB) DDR4-3000 CL16 | GPU: Nvidia GTX 1060 6GB Zotac Mini | Case: K280 Case | PSU: Cooler Master B600 Power supply | SSD: 1TB  | HDDs: 1x 250GB & 1x 1TB WD Blue | Monitors: 24" Acer S240HLBID + 24" Samsung  | OS: Win 10 Pro

 

Audio: Behringer Q802USB Xenyx 8 Input Mixer |  U-PHORIA UMC204HD | Behringer XM8500 Dynamic Cardioid Vocal Microphone | Sound Blaster Audigy Fx PCI-E card.

 

Home Lab:  Lenovo ThinkCenter M82 ESXi 6.7 | Lenovo M93 Tiny Exchange 2019 | TP-LINK TL-SG1024D 24-Port Gigabit | Cisco ASA 5506 firewall  | Cisco Catalyst 3750 Gigabit Switch | Cisco 2960C-LL | HP MicroServer G8 NAS | Custom built SCCM Server.

 

 

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×