Solved

Outlook Web Access Error

Posted on 2006-06-20
15
2,034 Views
Last Modified: 2009-07-29
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
Comment
Question by:ONYX
  • 8
  • 7
15 Comments
 
LVL 18

Expert Comment

by:amaheshwari
Comment Utility
it should be \\.\BackOfficeStorage\mycompany.com\MBX not this \\BackOfficeStorage\mycompany.com\MBX.Please type this and try to access.
0
 

Author Comment

by:ONYX
Comment Utility
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
 
LVL 18

Expert Comment

by:amaheshwari
Comment Utility
Do not try open but use browse are you able to open owa there after browsing.
0
 

Author Comment

by:ONYX
Comment Utility
Okay...that does work. I still cannot access it from the outside, it says 'Page Not Found'.
0
 
LVL 18

Expert Comment

by:amaheshwari
Comment Utility
So you are able to access owa internally but not externally.Have you tried accessing owa outside with http://Public IP/exchange.
0
 
LVL 18

Expert Comment

by:amaheshwari
Comment Utility
Are you using any router or firewall in between external owa and exchange.
0
 

Author Comment

by:ONYX
Comment Utility
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
Better Security Awareness With Threat Intelligence

See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.

 
LVL 18

Expert Comment

by:amaheshwari
Comment Utility
On your dns server go to command prompt .Type ipconfig/flushdns then press enter the type ipconfig/registerdns and press enter.Then try .
0
 

Author Comment

by:ONYX
Comment Utility
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
 
LVL 18

Expert Comment

by:amaheshwari
Comment Utility
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
 

Author Comment

by:ONYX
Comment Utility
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
 

Author Comment

by:ONYX
Comment Utility
I flushed the DNS and registered it, then tried pinging exchange.mycompany.com and still returned the old exchange server.
0
 
LVL 18

Expert Comment

by:amaheshwari
Comment Utility
You should check your firewall and DNS.
0
 

Author Comment

by:ONYX
Comment Utility
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
 
LVL 18

Accepted Solution

by:
amaheshwari earned 50 total points
Comment Utility
Yes you should .Otherwise go to active directory sites and services and do a replication among the site.
0

Featured Post

Wish Marketing would stop bothering you?

Is your marketing department constantly asking for new email signature updates? Are they requesting a different design for every department? Do they need yet another banner added? Don’t let it get you down! There is an easy way to manage all of these requests...

Join & Write a Comment

This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now