• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 493
  • Last Modified:

OWA routing problem

I'm trying to diagnose a problem with mailbox access via OWA on a network. The client has a DC running Windows 2000 and Exchange 2003 SP2 and a Windows 2003 terminal server. The strange thing is there are 2 routers on the network - the gateway for the Terminal server is an SDSL router (192.168.1.200) and the gateway for Exchange server is an ADSL router (192.168.1.1). OWA can be accessed from within the network but not from without. Not at DNS problem as TS works fine using the FQDN and port 80 is open on both routers. SSL not being used yet.
Any suggestions why this should be so?  Cheers.
0
ramick
Asked:
ramick
  • 4
  • 4
1 Solution
 
vico1CIOCommented:
What error message do you get when you try to access?
0
 
ramickAuthor Commented:
In IE7 I get "Internet Explorer cannot display the web page" and when trying to use ActiveSync with a Windows mobile 5 device it just says "waiting for network"  and no sync happens - can't see any log in the windows\activesyc folder either.
 
Didn't mention before, but the domain name being used resolves to the external IP address of the router that is the default gateway of the Terminal Server and not the Exchange server.
0
 
vico1CIOCommented:
Do you have the gateways sepecified on the external network cards?
That may not be a problem for TS But for HTTP access it will be.

So you will need to add the following gateways to the external card:
192.168.1.1 and 192.168.1.200

Let me know if that works.
0
Granular recovery for Microsoft Exchange

With Veeam Explorer for Microsoft Exchange you can choose the Exchange Servers and restore points you’re interested in, and Veeam Explorer will present the contents of those mailbox stores for browsing, searching and exporting.

 
ramickAuthor Commented:
Only room for one IP address as the gateway for each network card but I've set the first gateway in the DHCP settings on the DC to 192.168.1.200 and re-started the service but this doesn't seem to make any difference. 'ipconfig' on the DC is still showing 192.169.1.1. as the gateway and I can't get to the network properties on this machine - when I try and go to the properties page  it just dissappears before the network components are shown!
0
 
vico1CIOCommented:
That is your problem.
The gateway shown on the  DC is on a complete different Subnet IP, will be therefore impossible to communicate with the router or gateway.

Don't you have admin priviledge, what do you mean you can't get to network properties?

And yes you can add more than 1 gateway, This is how you do it:

1.-On your Windows 2000 Desktop, Right click on "My network places" then left click on properties

2.-Right click on the Connection that is your external NIC card then left click on properties

3.-Select  (Highlight) "Internet Protocol TCP/IP" then click on properties located on the bottom

4.-Under General tab click on "Advanced" on the bottom

5.-Under IP Settings tab, Under default gateway Widows, Click on add (You could add as many gateway as you like)
    then click ok 3 times.

Now you have to  find you way to get access to the properties to enter a valid static IP and the gateways.

I hope that helped!

vico1!
0
 
ramickAuthor Commented:
thanks vico1.  Unfortunaltely can't test your answer as there must be something wrong with the network properties or the NIC. I am logged on as administrator but I can't get the properties page of the network connection to display on screen. All the network properties windows just close down a few seconds after I click on Properties for the LAN. The window showing the components starts loading (with no components listed) then shuts down. NIC properties look OK in device manager.
0
 
vico1CIOCommented:
How can you be the admin and not beeing able to access properties for a network connection?
Do you mean that all options are grayed out?
Did you implement any local policy of such?
It's time to do a complete backup of the system or clone it before trying anything further.

Then uninstall the the card then reintall it to see if that changes the status.
or If possible, uninstall the protocols and reinstall.

Vico1
0
 
ramickAuthor Commented:
There is obviously a problem here as the page just disappears from the sreeen! thanks for your help.
Ramick
0

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

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