Solved

New Server - Problems With Outlook Web Access

Posted on 2006-11-10
16
520 Views
Last Modified: 2013-11-29
Hello,

I just installed a new Win 2003 server, with Exchange 2003 and IIS.  I copied my web site from old server to new one and set it up the same, as far as I can tell.   All mailboxes from the old exchange server were moved to the new server yesterday, with no problems.   However, when I try to access OWA, it tells me the webpage can not be found.

Am trying using in-house intra net.  Have tried using following:

mail.calvaryspringfield.org/exhange   - fails
172.16.1.222/exchange                    - fails

172.16.1.223/exchange - logs me in and shows and incompleted page....missing stuff, does not look correct
                                     IE shows a lot less than Firefox

Server has 2  - 1GB LAN connections into a LINKSYS GB network switch, which connects into a single GB port on an HP PRO CURVE Switch........

In DNS have configured 172.16.1.222 as mail.calvaryspringfield.org
This is a domain controller and global catalog server
This is a DNS server.

If I try OWA to the old exchange server, it logs me in, but does not show anything.

Please advise.  Thanks.
0
Comment
Question by:rstuemke
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 4
  • 3
  • +2
16 Comments
 
LVL 6

Expert Comment

by:bigphuckinglizard
ID: 17915785
You can't just copy the OWA website across to another computer - you'll need to reinstall it from the exchange cd.
0
 

Author Comment

by:rstuemke
ID: 17915968
Changed the new server web site to point to 172.16.1.222, so now mail.calvaryspringfield.org/exchange
will log me in but it gets a really funky display.  No list of folders, just a bunch of boxes and the words INBOX,  FOLDERS
and LOADING......

Like it is starting to load but quits  and then leaves an incomplete page......


So to recap....I am getting something now, but it is not correct....that is with IE.
With FireFox, I am getting a list of email in the INBOX, but it is not right either....if I try to click on an INBOX
             entry, it fails with Bad Request (Invalid Hostname)
0
 
LVL 6

Expert Comment

by:bigphuckinglizard
ID: 17915975
reinstall owa
0
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

 
LVL 9

Expert Comment

by:PeterMac
ID: 17916097
bigphuckinglizard is correct OWA is not a website as such, just an intercept dll that accesses exchange. You must reinstall OWA on new server, should also remove from old server, since this no longer has any mailboxes.
0
 
LVL 38

Expert Comment

by:Hypercat (Deb)
ID: 17916117
Was the old server the same version of Exchange as the new one?  If not, then you should not have copied your web site from the old server to the new one.  It wasn't necessary, anyway, unless you had some customizations to the old site that you wanted to preserve.  In any case, if the versions were different, it's highly unlikely that the older version would work with Exchange 2003.  The Exchange installation installs OWA by default, so by copying you overwrote the correct version with a different one.  I concur with the previous post - put your Exchange 2003 CD back in the new server and reinstall OWA.

Hope this helps!
0
 

Author Comment

by:rstuemke
ID: 17916387
Let me clarify.......

I copied the folder C:\INETPUT\WEBSITE from old server to new server.
Then changed the Default Web Site to point to the new directory.

C:\INETPUB\WEBSITE is our web site.  Contains HTML and images and CSS.  As far as OWA is concerned I did not copy anything specific for it.

Both servers exactly same software versions and corrections.
0
 

Author Comment

by:rstuemke
ID: 17921278
OK....on old server, which is still the real web site, I changed the EXCHANGE properties to point to the new servers BACKOFFICE and still does not work.  I have checked the settings between servers and can not find the culprit.  May be an IIS problem, since that does not work correctly either on this server....it wants a password for anonymous users....have question out on it also....
0
 
LVL 9

Expert Comment

by:PeterMac
ID: 17928866
Re anonymous user - This can be edited in "Directory Security" on web site properties.

Other problems may be partly security settings, User that IIS service runs under needs full access to all Exchange Directories, normally this would default to local system account, so would not be a problem if Exchange, and IIS on same server, but will prevent remote access to Exchange from another server. If your IIS service is not running under local system account make sure that account used has full access to Exchange.
0
 

Author Comment

by:rstuemke
ID: 18038675
OK - Update....

I moved all the mailboxes back to the old server.  Uninstalled Exchange 2003, and IIS.  Re-installed Exchange 2003 + service pack + corrections.  Moved 1 test user to new exchange server.  

The website itself now works correctly, there was a sync problem with the IUSR_ and IWAM_  accounts and IIS.
Now back to the original problem of OWA not working......

I have 2 LAN connections.....set up one dedicated to IIS - 172.16.1.223 - ok. works fine.  
I go to http://172.16.1.223/exhange ---- enter my userid (which is still on old server) and password....it connects to
old server and I have to log onto the old server as well....so have to enter userid and password twice.....

Then I tried the one test user whose mailbox has been moved over to the new server......

Got it to work successfully for test user.  Now this was all done inhouse.....the real test will be from outside the local network.......more later as I get this set up and tested......
0
 
LVL 9

Assisted Solution

by:PeterMac
PeterMac earned 250 total points
ID: 18038929
Double entry of logon is normal if connect to OWA on server other than one account is located on - at least I never found any way of avoiding it.
0
 

Author Comment

by:rstuemke
ID: 18055912
Ok here is the update and I need an answer.......


First a little refresher.....

1) OLD Server (1730wexchgweb) and NEW (1730wexchgiis) Server both open for port 25 on firewall
   (by their IP address).      Both open for port 80, also.

2) OLD Server has all email accounts but 1 test account.  NEW server has 1 test account.

3) Each Exchange System Manager (for both servers) has the SMTP Virtual Server configured with same
    External DNS servers (2 in house local servers).  These 2 local DNS servers have forwarders to real external
    DNS servers from our ISP.
   
When I went outside the firewall and tried here is what happenend:

1) Tried OWA for 1 test account on new server - works
2) Tried OWA for regular account on old server - fails, says 1730wexchgweb.calvaryspringfield.org not found
3) Disabled firewall port 25 and 80 for new server, old server still open
4) Tried OWA for 1 test account on new server - fails, says 1730wexchgiis.calvaryspringfield.org not found
5) Tried OWA for regular account on old server - works

Seems I can not have port 25 (maybe 80 also) enabled for new server and old server, because it then can not find the old server, which is alphabetically after the new server.

I also have DSN MX records for both servers.  OLD server priority 0, new server priority 9.

I would like to have both servers be able to service OWA for awhile, until I am able to get all the mailboxes moved from old server to new server.....what must I do to allow both to handle OWA.  Please advise.  Thanks.
0
 

Author Comment

by:rstuemke
ID: 18056004
also when I diasable old server in firewall, the 1 test account works and regular accouts do not....same as item #1 & #2.


some sort of DNS problem?????
0
 
LVL 10

Accepted Solution

by:
MATTHEW_L earned 250 total points
ID: 18063990
What is happening is you are connecting to OWA on one of the servers.  If the mailbox is located on that server it will work.  If the mailbox is on the other server, it redirects you to that server via its internal FQDN which will not work.  You will either need to use a Front-End server for this.  This will allow you access mailboxes on any backend server and only authenticate once.  Or as suggested in your other open question, you can port forward different ports to each exchange server and have users access the correct one depending on where their mailbox is.

http://domain.com/exchange -- one mailbox server

http://domain.com:8000/exchange -- another mailbox server.

The front end / back end solution will work the best and be the most scaleable.
http://www.microsoft.com/technet/prodtechnol/exchange/Guides/E2k3FrontBack/3beec46b-188a-4067-9f1e-c9fe17e1cb9f.mspx?mfr=true
0
 
LVL 10

Expert Comment

by:MATTHEW_L
ID: 18063993
MX records have nothing to do with OWA also.  They are simply for incoming SMTP traffic.  
0
 
LVL 9

Expert Comment

by:PeterMac
ID: 18113932
Sorry had a bout of Flu, and just picking up again.

Information from Mathew L is good, there are only two ways to avoid double login to second exchange server.

1) deploy front end server as described in article above - Expensive though.

2) provide seperate external IP and DNS for second server so that users can access directly - users will need to know which server their mailbox is on, so that they can access correct server - this is route we have taken, works OK as long as you don't move mailboxes very often. - Access is always available through other server, just with multiple login requirement.
0
 
LVL 10

Expert Comment

by:MATTHEW_L
ID: 18114474
Solution 2 will still not work.  When Exchange redirects you to the appropriate mailbox it does so with it's internal FQDN, so you still will not get redirected externally.  You would have to have two external IP's for your exchange servers, say mail1.domain.com and mail2.domain.com and tell users which one they should use.  You would be better off spending the money now and getting another exchange server and use as a front end.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

PRTG Network Monitor lets you monitor your bandwidth usage, so you know who is using up your bandwidth, and what they're using it for.
This article will inform Clients about common and important expectations from the freelancers (Experts) who are looking at your Gig.
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
Suggested Courses
Course of the Month11 days, 5 hours left to enroll

628 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