We are migrating from exchange 2000 to 2007. We have about 15 mailboxes moved from the 2000 server to the 2007 server. My question is, the users who have been move over to the new server are unable to check email via owa remotely. For example, it they go to. mail2.company.com/exchange - they get an error saying "HTTP Error 404 - File or Directory Not Found. However, the users who have not been migrated to the new server are still able to access their OWA remotely without a problem. OWA for the new server works fine internally - if I go to server2007/owa it works fine. We just need to know how to get it working externally. I thought this was all part of the migration where the old server just knew to send the request to the new server if the mailbox was located on the new server.

Your 2007 CAS should be the only point of ingress. That said, IIRC, if you have MBXs on a combined 2007 CAS/MBX box you can't use it as a CAS to the 2000 box. "calibertech99" wrote in message news:133d4e74-255c-444f-9fe8-9f10ba2e86a1... We are migrating from exchange 2000 to 2007. We have about 15 mailboxes moved from the 2000 server to the 2007 server. My question is, the users who have been move over to the new server are unable to check email via owa remotely. For example, it they go to. mail2.company.com/exchange - they get an error saying "HTTP Error 404 - File or Directory Not Found. However, the users who have not been migrated to the new server are still able to access their OWA remotely without a problem. OWA for the new server works fine internally - if I go to server2007/owa it works fine. We just need to know how to get it working externally. I thought this was all part of the migration where the old server just knew to send the request to the new server if the mailbox was located on the new server.Mark Arnold, Exchange MVP.

My apologies - I'm not totally following your post. Could you explain in another manner?

On Tue, 15 Jun 2010 14:10:59 +0000, calibertech99 wrote: >We are migrating from exchange 2000 to 2007. We have about 15 mailboxes moved from the 2000 server to the 2007 server. My question is, the users who have been move over to the new server are unable to check email via owa remotely. For example, it they go to. mail2.company.com/exchange Try https://mail2.company.com/owa instead. > - they get an error saying "HTTP Error 404 - File or Directory Not Found. However, the users who have not been migrated to the new server are still able to access their OWA remotely without a problem. OWA for the new server works fine internally - if I go to server2007/owa it works fine. Why would you use a different virtual directory when you connect "externally"? Use the same one that works from inside your LAN. >We just need to know how to get it working externally. I thought this was all part of the migration where the old server Ahhh . . . you're trying to use the Exchange 2003 Front-End server, or the Exchange 2003 mailbox server, to connect to Exchange 2007? That's not going work. >just knew to send the request to the new server if the mailbox was located on the new server. It works the other way. :-) The Exchange 2007 CAS will send the connection to Exchange 2003. But Exchange 2003 knows nothing of Exchange 2007. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Thanks for the reply. We installed our new 2007 server the other day and we started migrating mailboxes over to it. My boss told me to make sure that users who have been migrated to the new server could check their email via owa. So basically it sounds like this is not possible until we decomission the old server?

On Wed, 16 Jun 2010 02:48:09 +0000, calibertech99 wrote: >Thanks for the reply. We installed our new 2007 server the other day and we started migrating mailboxes over to it. My boss told me to make sure that users who have been migrated to the new server could check their email via owa. So basically it sounds like this is not possible until we decomission the old server? No, you just have to to stop using the Exchange 2003 server as the "OWA server". Use the Exchange 2007 CAS role for that purpose. Unless you've installed the Exchange 2007 CAS on the Exchange 2007 mailbox server machine that'll work. If the CAS is on the same machine as the Mailbox role then Exchange 2007 users should use the Exchange 2007 CAS for OWA and the Exchange 2003 users should use the Exchange 2003 server (as they do now). --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi, Is the mail2.company.com a external URL? Is your external URL associated with exchange 2003 server? You can change your external URL to exchange 2007 server and then use exchange 2007 OWA to access the users' mailboxes from Internet. When you access the mailboxes in exchange 2007 by using exchange 2003's OWA, it will internally redirect this request to exchange 2007 CAS server. The problem is that Internet users cannot access the internal URL of exchange 2007. For example: Https://mail.domain.com/ is the external URL of exchange 2003 OWA. https://ex2007.domain.com/owa is the internal URL of exchange 2007 OWA. When you access Https://mail.domain.com/ and then enter your credential , exchange 2003 OWA detect your mailbox is in exchange 2007. Then it will redirect you to https://ex2007.domain.com/owa. This URL is a internal URL, so the you cannot access it from Internet. If you want to use exchange 2003 OWA to access the mailboxes in exchange 2007, you need to set up a external URL for Exchange 2007's OWA. More information, you can refer the following links: How to set up a External URL for Exchange 2007 http://technet.microsoft.com/en-us/library/bb691323(EXCHG.80).aspx Outlook Web Access and Exchange 2007, 2003 and 2000 coexistence http://msexchangeteam.com/archive/2007/02/07/434523.aspx

Yikes. Seems you got the answer to a totally different question. I wonder what answer got put into their question "calibertech99" wrote in message news:3ef87642-c7bb-4b9f-a0ae-bc0dc06770ef... My apologies - I'm not totally following your post. Could you explain in another manner?Mark Arnold, Exchange MVP.