Jump to content

Exchange Server HELP!

Go to solution Solved by Sir Asvald,
6 minutes ago, Falconevo said:

Start reviewing your event logs, it should be the first place you start as a server admin.

Found the problem. Old IP was binding to port 443. I had remove it adding the new one :D

I used the "netsh https add iplisten ipaddress=x.x.x.x" command.

I need help ASAP. My Exchange Server decided to crap itself. I'm Getting this error:

 

 

Spoiler

4432bd3ef6f1a8cc6bebf7cc430f1e66.png

I came home from a trip and I saw this. 

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

Done any windows updates recently?  Error is related to SSL certificate and the protocol in use.

 

I'd log in to the exchange server locally and review your SSL certificate configuration and see if you have recently installed KB931125

Please quote or tag me if you need a reply

Link to comment
Share on other sites

Link to post
Share on other sites

Check time and date. Check SSL cert. Maybe clear SSL state.

Probably gaming or helping technophobes with tech...

Link to comment
Share on other sites

Link to post
Share on other sites

11 minutes ago, Falconevo said:

Done any windows updates recently?  Error is related to SSL certificate and the protocol in use.

 

I'd log in to the exchange server locally and review your SSL certificate configuration and see if you have recently installed KB931125

Nope. I haven't even touched the server while I was away. The certificate works. I tried it on another server. 

 

 

This is what I'm getting when I open the EMC

 

Spoiler

2138ac1dcfd3fa4a4fbfcda3b646a53d.png

 

 

10 minutes ago, userzero said:

Check time and date. Check SSL cert. Maybe clear SSL state.

The SSL is fine. Works on the other servers

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

Check certificate configuration is correct on the *:443 binding then restart IIS.


I would suggest you also make sure all exchange services are running and review the event logs.

Please quote or tag me if you need a reply

Link to comment
Share on other sites

Link to post
Share on other sites

Yep was gonna say check the port binding of that port.

Probably gaming or helping technophobes with tech...

Link to comment
Share on other sites

Link to post
Share on other sites

11 minutes ago, Falconevo said:

Check certificate configuration is correct on the *:443 binding then restart IIS.


I would suggest you also make sure all exchange services are running and review the event logs.

Everything is correct. :/:( Services are working as it is. :( 

 

e08e85ce7da994650f2b2f227ae300ef.png

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

Start reviewing your event logs, it should be the first place you start as a server admin.

Please quote or tag me if you need a reply

Link to comment
Share on other sites

Link to post
Share on other sites

6 minutes ago, Falconevo said:

Start reviewing your event logs, it should be the first place you start as a server admin.

Found the problem. Old IP was binding to port 443. I had remove it adding the new one :D

I used the "netsh https add iplisten ipaddress=x.x.x.x" command.

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

2 minutes ago, Abdul201588 said:

Found the problem. Old IP was binding to port 443. I had remove it adding the new one :D

I used the "netsh https add iplisten ipaddress=x.x.x.x" command.

Good to hear, I'd probably suggest the binding be updated in IIS for the correct IP and cert mapping.  Will save you having to do that again.

Please quote or tag me if you need a reply

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

×