Microsoft Exchange Server

[IntanMastini]

I get the following error text when I open Microsoft Exchange Server

“The action cannot be completed. The connection to the Microsoft Exchange Server is unavailable. Your network adapter does not have a default gateway” or “Your Microsoft Exchange Server is unavailable”.

I looked around and found a few solutions, but nothing worked for me.

[RichCor]

Seems an odd place to post this type of question.

Do you actually 'have' a Microsoft Exchange Server on your LAN, used by your company, or subscribed to by you?

What device are you using to connect to the Exchange Server, and how are you trying to 'open' Exchange Server?

Wikipedia:

Microsoft Exchange Server

Exchange Server is licensed both in the forms of on-premises software and software as a service. In the on-premises form, customer purchase client access licenses (CALs). In the software as a service form, Microsoft receives a monthly service fee instead.

[NeverSure]

Is this a server you've been using, or is it one you've just set up - either the client or the server?

I think your problem might be with your email client and not with Exchange. I think it might be as simple as lacking a default gateway (Exchange) in the client. I could try a long post, but start with this:

https://support.microsoft.com/en-us/kb/913843

[NeverSure]

Seems an odd place to post this type of question.

Do you actually 'have' a Microsoft Exchange Server on your LAN, used by your company, or subscribed to by you?

What device are you using to connect to the Exchange Server, and how are you trying to 'open' Exchange Server?

Wikipedia:

Microsoft Exchange Server

Exchange Server is licensed both in the forms of on-premises software and software as a service. In the on-premises form, customer purchase client access licenses (CALs). In the software as a service form, Microsoft receives a monthly service fee instead.

I've used Exchange Server a lot and for a long time. The concept of recurring charges is relatively new as it is with some versions of Office. With earlier versions which are still viable, you own them. They share the same risk as a web server in that they must be outside of the DMZ.

I think he has failed to set up Outlook or whatever email client he's using on his work station to look to Exchange for the default email gateway. Just a hunch though.

Cheers.

[Chicog]

Would it be too far out there to suggest that your problem is with Outlook, not the server, and you should check your network settings?

Edited December 16, 2015 by Chicog

[RichCor]

I think he has failed to set up Outlook or whatever email client he's using on his work station to look to Exchange for the default email gateway. Just a hunch though.

That would be my guess as well.

But then, don't know why the OP typed, "I get the following error text when I open Microsoft Exchange Server", if they're trying to configure client software. Makes me think the OP doesn't really know what they're doing.

Also, very odd question for a first post.

[NeverSure]

There are people who specialize in Exchange and Microsoft offers certifications for it (which I have had.) Exchange has always been one of the rigorous exams required for either MCSA or MCSE. Now Microsoft has changed the meaning and the life of those certifications so I am no longer considered "current" but they still require the exam for Exchange.

Microsoft recommends 4 years of experience with Exchange before taking the exam and getting certified. It's no small learning curve.

"MCSA: Windows Server 2012"

"Microsoft recommends that you have four years of Microsoft Exchange Server experience, along with on-premises and cloud experience, before attempting MCSE: Messaging certification." LINK

Microsoft, at seminars, has always made it clear that Server versions are the basic operating system with additional functions added. Windows Enterprise edition is the same as Home but with additional functions such as being able to join a domain. Server is the same but with additional functions. Exchange - the same.

I'm not sure why anyone would use Exchange outside of an enterprise that needed confidentiality. There are simply too many affordable exchange hosts out there with specialists. Hospitals and attorneys with confidential patient files and communication would be candidates for in-house exchange.

Cheers.

[tinhead]

Version Exchange likely important. E2K3 may require manual configure of proxy server settings for RPC over HTTP.

Otherwise DNS on 2007 and above should figure that out.

Your client software is also a factor.

https://exchange.server/exchange or https://exchange.server/owa work?

[chrisinth]

I would assume that you get the error message when you open your email client instead of when you open the exchange server?

Is it a new install or has the problem just started?

Which version of exchange are you running?

Which version of Server have you got it on?

Is your Active Directory setup correctly?

What email client are you using to connect (or not!!) to the exchange server?

Are you using 3rd party gateway software?

Firewalls & anti-virus configured correctly?

What operating system are your workstations using?

Is it only the one workstation that this is affecting or is it all accounts?

Are you subscribed to Office365 and talking about the virtual exchange server?

Etc, etc, etc. Need a bit more info OP......................

[NeverSure]

I would assume that you get the error message when you open your email client instead of when you open the exchange server?

Is it a new install or has the problem just started?

Which version of exchange are you running?

Which version of Server have you got it on?

Is your Active Directory setup correctly?

What email client are you using to connect (or not!!) to the exchange server?

Are you using 3rd party gateway software?

Firewalls & anti-virus configured correctly?

What operating system are your workstations using?

Is it only the one workstation that this is affecting or is it all accounts?

Are you subscribed to Office365 and talking about the virtual exchange server?

Etc, etc, etc. Need a bit more info OP......................

These are excellent and vital questions. I don't think it's possible for an inexperienced person to run Exchange Server. It has to be part of a domain using Server with Active Directory as the domain controller. Exchange Server responds to the Schema in Active Directory, i.e. permissions.

I like to think I'm fairly bright but I had a heckuva time becoming fluent with Active Directory and I'm not the only one. It isn't even worth learning unless you're going to make Server Admin a life's profession IMHO.

We don't even know what OS he has and if Windows, whether it's an upper level version that can join a domain and respond to AD. I think he's in over his head and should outsource email unless he's doing this for the challenge or personal reasons.

Cheers.

[RichCor]

I see that the OP, IntanMastini, has opened accounts under this username on several hundred other forums in the last few days.

Seems he likes posting questions about errors he sees on his screen.

[chrisinth]

I would assume that you get the error message when you open your email client instead of when you open the exchange server?

Is it a new install or has the problem just started?

Which version of exchange are you running?

Which version of Server have you got it on?

Is your Active Directory setup correctly?

What email client are you using to connect (or not!!) to the exchange server?

Are you using 3rd party gateway software?

Firewalls & anti-virus configured correctly?

What operating system are your workstations using?

Is it only the one workstation that this is affecting or is it all accounts?

Are you subscribed to Office365 and talking about the virtual exchange server?

Etc, etc, etc. Need a bit more info OP......................

These are excellent and vital questions. I don't think it's possible for an inexperienced person to run Exchange Server. It has to be part of a domain using Server with Active Directory as the domain controller. Exchange Server responds to the Schema in Active Directory, i.e. permissions.

I like to think I'm fairly bright but I had a heckuva time becoming fluent with Active Directory and I'm not the only one. It isn't even worth learning unless you're going to make Server Admin a life's profession IMHO.

We don't even know what OS he has and if Windows, whether it's an upper level version that can join a domain and respond to AD. I think he's in over his head and should outsource email unless he's doing this for the challenge or personal reasons.

Cheers.

I would agree that if you don't have a good working knowledge of Microsoft Server software, especially AD, and networking, then you shouldn't even think about approaching Exchange.

From the OP (even though I would query some of the error messages) I think he has an Office 365 account and isn't connecting to the virtual exchange server. The below snap is what he should be seeing on his Outlook (this is from Outlook 2016) if that is the email client he is using.

[RichCor]

I would agree that if you don't have a good working knowledge of Microsoft Server software, especially AD, and networking, then you shouldn't even think about approaching Exchange.

From the OP (even though I would query some of the error messages) I think he has an Office 365 account and isn't connecting to the virtual exchange server. The below snap is what he should be seeing on his Outlook (this is from Outlook 2016) if that is the email client he is using.

Exchange Connect.png

You do realize the OP is a troll doing this on multiple forum boards, right?

[chrisinth]

I would agree that if you don't have a good working knowledge of Microsoft Server software, especially AD, and networking, then you shouldn't even think about approaching Exchange.

From the OP (even though I would query some of the error messages) I think he has an Office 365 account and isn't connecting to the virtual exchange server. The below snap is what he should be seeing on his Outlook (this is from Outlook 2016) if that is the email client he is using.

Exchange Connect.png

You do realize the OP is a troll doing this on multiple forum boards, right?

Looks that way, for this thread anyway. I was replying to Never Sure and not the OP.

Was also informing people who do have an Office365 account that their emails are kept on a Microsoft exchange server if they didn't already know that, certainly one of the better things to come with this cloud solution.

Not sure about Office365 Home, but I have admin rights for our company's 365 for Business exchange accounts, very similar to the physical software we had before changing to cloud (albeit I was running Exchange 2003 on MS Server 2003 Ent, software) .

[lostinisaan]

Is this a server you've been using, or is it one you've just set up - either the client or the server?

I think your problem might be with your email client and not with Exchange. I think it might be as simple as lacking a default gateway (Exchange) in the client. I could try a long post, but start with this:

https://support.microsoft.com/en-us/kb/913843

Are you never sure?

[NeverSure]

Yeah, I see that the guy's probably a troll but it's a good discussion anyway.

Despite all of the other good and complex suggestions made here, Outlook must be configured to use Exchange as the default gateway for email even if the rest of the topology and settings are correct. I could have 100 clients using the Exchange server, but that new 101st box is still going to have to be set to look for the Exchange server as the default gateway for email. It's also going to need permission in AD.

Cheers.

Edited December 22, 2015 by NeverSure

[Chicog]

Well it's not an "Exchange Server" nowadays anyway, it's "Exchange Servers".