[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2071
  • Last Modified:

Outlook Web Access Error

We created a new exchange server and installed SP2 etc etc, email/Outlook work fine, but Outlook Web Access does not. If I try and access is using the URL for OWA... http://exchange.mycompany.com/exchange, it says it can't find the page. So, in the Exchange server I opened IIS and right clicked on Exchange under default web server..from that menu I clicked open, and here is the error message I get:

\\BackOfficeStorage\mycompany.com\MBX is not accessible. You might now have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. No network provider accepted the given network path.

I'm logged in as the admin. Any idea what this means? I'm guessing that's the reason that OWA doesn't work...

Thanks

0
ONYX
Asked:
ONYX
  • 8
  • 7
1 Solution
 
amaheshwariCommented:
it should be \\.\BackOfficeStorage\mycompany.com\MBX not this \\BackOfficeStorage\mycompany.com\MBX.Please type this and try to access.
0
 
ONYXAuthor Commented:
If I look at the properties, it does show \\.\BackOfficeStorage\mycompany.com\MBX ....but the error message appears exactly as I typed it above. THanks
0
 
amaheshwariCommented:
Do not try open but use browse are you able to open owa there after browsing.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
ONYXAuthor Commented:
Okay...that does work. I still cannot access it from the outside, it says 'Page Not Found'.
0
 
amaheshwariCommented:
So you are able to access owa internally but not externally.Have you tried accessing owa outside with http://Public IP/exchange.
0
 
amaheshwariCommented:
Are you using any router or firewall in between external owa and exchange.
0
 
ONYXAuthor Commented:
I tried the public IP/exchange and that didn't work. There is a firewall and changes have been made to point to our new exchange server. I think this may be a DNS issue now...we had an old exchange server, and I think when you type http://exchange.mycompany.com/exchange, once it gets inside our firewall, it's still resolving to the old exchange server. if I ping exchange.mycompany.com, it comes up with the old servers IP. I looked in DNS but it's not there...so I;m not sure what's going on.
0
 
amaheshwariCommented:
On your dns server go to command prompt .Type ipconfig/flushdns then press enter the type ipconfig/registerdns and press enter.Then try .
0
 
ONYXAuthor Commented:
Here's another bit of info...if I open up IE on my exchange server and type in :

http://localhost/exchange

I would think OWA would come up, but it doesn't....
0
 
amaheshwariCommented:
What if you try with http://Exchange server name/exchange.
There is definitely DNS issue.It is not resolving the name and IP.Have you tried flushdns and registerdns.


Check the network properties of exchnage server .Is DNS entry specified there in network properties?
0
 
ONYXAuthor Commented:
I tried  http://Exchange server name/exchange and OWA does come up. It doesn't prompt me for a login/password to OWA, it just takes me straight into OWA. Strange...

I looked at the TCP/IP settings for the new exchange server and there is a DNS Specified there.

I'll try the flush DNS.
0
 
ONYXAuthor Commented:
I flushed the DNS and registered it, then tried pinging exchange.mycompany.com and still returned the old exchange server.
0
 
amaheshwariCommented:
You should check your firewall and DNS.
0
 
ONYXAuthor Commented:
Okay, I think I;m on to something. I checked our DNS Server and under Forward Lookup Zones, there is a A (Host Record) for exchange.mycompany.com, which points to the old exchange server. I changed the IP address to the new server, did the flush and reregisterdns again, but still the same issue...it's still pinging to the old address. Do I need to give it a few minutes to propegate accross the domain?
0
 
amaheshwariCommented:
Yes you should .Otherwise go to active directory sites and services and do a replication among the site.
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 8
  • 7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now