Outlook not logging on to Exchange 5.5 with router switched off

ITeC · Post by **ITeC** » Thu Mar 15, 2001 10:04 am

I have set up an exchange 5.5 server. I am using Outlook 2000 to connect to the server. However when the router is switched off Outlook will not log on.

Thorazine · Post by **Thorazine** » Thu Mar 15, 2001 3:33 pm

Your question is a little vague. How is your network setup? If the traffic from the client (Outlook 2000) is going to the server (Exchange 5.5) through the router, then yes, everytime you turn off the router the client(s) will not be able to contact the server.

Explain a little about your setup and maybe I can help you.

glc1 · Post by **glc1** » Thu Mar 15, 2001 3:40 pm

Why are you truning your router off anyway?
Which router do you have?

ITeC · Post by **ITeC** » Thu Mar 22, 2001 4:23 am

No the Clients are not connecting through the router. The router is just used for the internet connection.
(It is a Cisco 801 router). Ingoing and out going mail is working ok.

cyberskye · Post by **cyberskye** » Thu Mar 22, 2001 1:09 pm

How do you connect your clients to the server? Through the router, through another sitch, multiple NIC's...?

ITeC · Post by **ITeC** » Fri Mar 23, 2001 6:50 am

There are about 30 computers connecting to 4 hubs. The router and the exchange server are also connected to these hubs.

ITeC · Post by **ITeC** » Fri Mar 23, 2001 7:06 am

This is a fairly basic setup. The server does not have to go through the router. Each terminal can ping the exchange server when the router is either on or off. The router is using NAT. There is a static route set up to the exchnage server nad this works perfect. But when the router is switched off Outlook cannot connect to the server.

twwabw · Post by **twwabw** » Fri Mar 23, 2001 7:21 am

I'm confused... what clients can't connect to the ES? Internal LAN clients, or external Internet clients? If the situation concerns external clients, there are many possibilities.

First, is your ES multi-homed? ie: wan nic, and lan nic, with IP forwarding enabled? Is your public ip on the wan side of the router? If it is, then of course you can't connect. The connection to that public IP no longer exists.

Or, do you have multiples IP's with the router having it's own IP, and the ES it's own ip (public)?

If you are multihomed, and have a public IP for the ES, then use a hosts file on the remote clients, to resolve server name to its internal non-routable IP.

More info please!

ITeC · Post by **ITeC** » Fri Mar 23, 2001 7:50 am

The Internal clients have private ip addresses. (ie 10.0.0.1). The mail server has and internal ip address of 10.0.0.104 and a static route set up on the router to the external address. All the clients that are tring to connect to the server are internal clients with private ip address connecting to the private ip address of the mail server. The server has a static assigned ip (ie 10.0.0.104). All other clients recieve an ip from DHCP.

twwabw · Post by **twwabw** » Fri Mar 23, 2001 9:44 am

In the client service setup, what do you have listed as the exch. server name? Is it a netbios name, or ip? What is the def gateway setting for clients? (IP)

Alteon · Post by **Alteon** » Sat Mar 24, 2001 7:21 pm

this depends if your exchange server is receiving all the mail first. if you have a static ip and the exchange server is setup as your internal mail server for all the mail for you domain or whatever, then you have to configure exchange to be able to work offline as well. if exchange server has lost internet connection then it cannot check for mail automatically(as it usually does) and it will not respond. its a simple problem. plus your on the wrong forum for that. go to technet at microsoft.com. theres a solution for your problem. i just dont know the link. sorry