Exchange 5.5, Outlook98 connection via Internet

[James Porter]

I would like Outlook98 users at a remote site to access my Exchange Server via the Internet. For most sites, this seems to be impossible, and the problem seems to be with hop count. Users physically close (less than 6 hops) to the Exchange Server are able to connect to their server-based Exchange mailbox without incident. However, with users for which a traceroute shows more than 6 hops, configuration as an Exchange client isn't possible.

I'm working around this by configuring remote users to be POP clients. However, I would like to maintain all on the server, and present a consistent solution. I might also add that these remote users are connecting to the Internet with AT LEAST 128K of bandwidth.

What can I do to allow remote users connect to the Exchange server as clients?

[Michael Ebbert]

If the IP address of the Exchange server is static, would it help you to add an entry to the LMHOSTS file to aid in name resolution? From your notes on hop counts below, it appears that you may have a timeout issue, and decreasing the time needed to resolve the name to IP might help.


------------
James Porter at 5/11/99 10:29:23 AM

I would like Outlook98 users at a remote site to access my Exchange Server via the Internet. For most sites, this seems to be impossible, and the problem seems to be with hop count. Users physically close (less than 6 hops) to the Exchange Server are able to connect to their server-based Exchange mailbox without incident. However, with users for which a traceroute shows more than 6 hops, configuration as an Exchange client isn't possible.

I'm working around this by configuring remote users to be POP clients. However, I would like to maintain all on the server, and present a consistent solution. I might also add that these remote users are connecting to the Internet with AT LEAST 128K of bandwidth.

What can I do to allow remote users connect to the Exchange server as clients?

[ramkaran]

you can use a small $1000 VPN box in a IPSEC tunnel mode
on your site and let remote side also have a similar box.
now your both networks are like in a lan. Remote site can now
share you local nt server and exchange server over the tunnel(no hops)
in tunnel mode.

Preferably setup IMAP4 on Outlook 98 for best performance over VPN.

ramkaran


------------
James Porter at 5/11/99 10:29:23 AM

I would like Outlook98 users at a remote site to access my Exchange Server via the Internet. For most sites, this seems to be impossible, and the problem seems to be with hop count. Users physically close (less than 6 hops) to the Exchange Server are able to connect to their server-based Exchange mailbox without incident. However, with users for which a traceroute shows more than 6 hops, configuration as an Exchange client isn't possible.

I'm working around this by configuring remote users to be POP clients. However, I would like to maintain all on the server, and present a consistent solution. I might also add that these remote users are connecting to the Internet with AT LEAST 128K of bandwidth.

What can I do to allow remote users connect to the Exchange server as clients?

[jimmy]

install microsoft PPTP or OWA (Outlook Web Access) or install a second Exchange server at the remote site. 6 hops should not be a problem. Do a trace route to Microsoft.com or any popular site and see how many how you get ( > 6, I'm sure). I think you have a routing issue in you WAN.




------------
Michael Ebbert at 5/13/99 8:38:57 AM

If the IP address of the Exchange server is static, would it help you to add an entry to the LMHOSTS file to aid in name resolution? From your notes on hop counts below, it appears that you may have a timeout issue, and decreasing the time needed to resolve the name to IP might help.


------------
James Porter at 5/11/99 10:29:23 AM

I would like Outlook98 users at a remote site to access my Exchange Server via the Internet. For most sites, this seems to be impossible, and the problem seems to be with hop count. Users physically close (less than 6 hops) to the Exchange Server are able to connect to their server-based Exchange mailbox without incident. However, with users for which a traceroute shows more than 6 hops, configuration as an Exchange client isn't possible.

I'm working around this by configuring remote users to be POP clients. However, I would like to maintain all on the server, and present a consistent solution. I might also add that these remote users are connecting to the Internet with AT LEAST 128K of bandwidth.

What can I do to allow remote users connect to the Exchange server as clients?