General discussion

Locked

Gateway IP & Outlook to Exchange Connect

By Kerry ·
I have my Win2000 desktops on NT LAN using the inside IP (private) address on Cisco firewall for gateway and when Outlook XP opens I get message indicating that Exchange Server 5.5 (SP4) is not responding, plus I usually get a prompt to retry or work offline. I usually only have to click retry once and then Outlook will connect. When I change my gateway to the public or outside address on my firewall, I don't get the 'not responding' message or even retry prompt, in fact, Outlook starts up rather quickly. But then Internet Explorer doesn't work--can't find any Web sites (whereas it did before with the private IP or inside address of firewall as gateway). I don't get it--it makes not sense to me. Anybody have an idea what's going on?

This conversation is currently closed to new comments.

14 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Gateway IP & Outlook to Exchange Connect

by curlergirl In reply to Gateway IP & Outlook to E ...

Without more specific info, it's hard to tell, but here's a guesstimated theory: If you don't have an internal DNS server, then your workstations must be using some other form of name resolution for internal processing, and whatever it is is slowerthan DNS (i.e., WINS). When you set the gateway to the external IP, they are querying an external DNS server first and finding the MX record for the public IP there, so it resolves more quickly. Admittedly a bit cockeyed, but does it make any sense to you?

Collapse -

Gateway IP & Outlook to Exchange Connect

by Kerry In reply to Gateway IP & Outlook to E ...

Poster rated this answer

Collapse -

Gateway IP & Outlook to Exchange Connect

by Kerry In reply to Gateway IP & Outlook to E ...

I'm have a DHCP and WINS server(s) on my LAN, but no DNS server.

Collapse -

Gateway IP & Outlook to Exchange Connect

by lee.read In reply to Gateway IP & Outlook to E ...

Outlook does'nt find the Exchange server by DNS therefore its not possible for it to find an MX record and use that (its only for SMTP mail). WINS and netbios broadcast is the only way Outlook will find the Exchange server, on this basis I would check your resolution, for example try creating a lmhosts file and see whether anything changes. You don't say whether your LAN has any separate subnets. It sounds to me as though somehow your desktops are getting the impression that the Exchange server is not on the local network and therefore passing the packets straight to the default gateway.

Hope this points you in the right direction.

Collapse -

Gateway IP & Outlook to Exchange Connect

by Kerry In reply to Gateway IP & Outlook to E ...

Yes, I figured that an LMHOSTS would solve the problem and put one on ALL computers on the LAN right after installing the firewall three months ago, but doesn't seem to make a difference. LMHOSTS is on all desktops, even all servers, reflecting allcomputers on the LAN. Do I need to show the private IP of the inside portion of the firewall in the LMHOSTS file?

Collapse -

Gateway IP & Outlook to Exchange Connect

by lee.read In reply to Gateway IP & Outlook to E ...

No the lmhosts file is used purely for netbios resolution. If you want the firewall to be referenced by its name then you want a hosts file. I don't suggest using either lmhosts or hosts files as permanent fixtures, use WINS and DNS for that. However they do provide a way of isolating the problem. First thing to check is whether you have an entry in the lmhosts file for your exchange server followed by its IP address?

If you don't then add one, use the lmhosts.sam as reference guide. Failing that I'm going to need some more information to be able to help you further.

1) Whats your Private IP address range(s) and subnet mask? ie 192.168.100.x / 255.255.255.248.0
2) Do you have WINS and DNS at present?
3) Whats the internal IP address of your exchange server and firewall?
4) What type of clients do you have 95,98,NT,linux and how many?

Get me this info and we'll see if we can get a bit further.

Ta
Lee

Collapse -

Gateway IP & Outlook to Exchange Connect

by Kerry In reply to Gateway IP & Outlook to E ...

I have WINS and DHCP on my LAN, only using LMHOSTS temporarily for troubleshooting this problem and for my WAN/VPN clients primarily. I assign static addresses to ALL my permanent LAN clients and printers, using DHCP only for mobile clients. I havethe Exchange Server computer name and IP address in LMHOSTS(and ALL staticly assigned IP addressed computers on LAN in LMHOSTS on ALL computers)

1) IP range: 192.168.10.0/127 255.255.255.128
2) I have WINS (DHCP), but no DNS on the LAN servers--DNS only external to LAN on ISP
3) Exchange Server is 192.168.10.27, firewall is 192.168.10.10
4) LAN clients are NT and Win2K, mostly Win2K
5) Exchange Server is 5.5 SP4 on NT Server SP6a which is also a WINS server
I've suspected a problem with WINS, but cannot determine what it is or for certain that one exists. For example, I've been showing an old WINS server in the database after it's been deleted (WINS service stopped on the old server and removed from WINS database--both WINS servers with old one no longer a replication partner). I also show another unknown server--both the former WINS server and this ghost server appearing in WINS database with //??(192.168.10.25) and //??, respectively.

Thanks for the help.

Collapse -

Gateway IP & Outlook to Exchange Connect

by shmaltz In reply to Gateway IP & Outlook to E ...

Where is the Exchange Server located? on the inside or outside? Is it on the same subnet as the workstation? If not, do route exist for the Exchange Server?
It looks to me more like a routing issue than anything else.
Email me with the answers to my questions and I'll try to answer it.

Collapse -

Gateway IP & Outlook to Exchange Connect

by shmaltz In reply to Gateway IP & Outlook to E ...

Is your DNS/WINS server located on the inside or outside?

Collapse -

Gateway IP & Outlook to Exchange Connect

by Kerry In reply to Gateway IP & Outlook to E ...

Exchange Server is on same subnet with ALL servers and LAN clients, e.g., 192.168.10.0/127 255.255.255.128. A private network scheme.

Back to Windows Forum
14 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums