RES: RE: Cannot connect Outlook to Exchange through VPN (Resolved)
- From: "itelephone" <itelephone@xxxxxxxxxxx>
- To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
- Date: Fri, 1 Oct 2004 10:13:51 +0800
----- Original Message -----
From: "itelephone" <itelephone@xxxxxxxxxxx>
To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
Sent: Friday, October 01, 2004 9:58 AM
Subject: Re: [exchangelist] Re: RES: RE: Cannot connect Outlook to Exchange
through VPN (Resolved)
> Hi Danny
>
> Thanks for the info. However, I have pix fw and my dns server & exchange
> server are ruuning on AD domain controllers and my DNS zone file is hosted
> with ISP dns server and I am using PPTP & L2TP on w2k server. I am using
> NAT.
>
> Remote users are using xp vpn client to connect ... having no problem with
> exchange server. But if you use Cisco VPN client & and cisco vpn network
> appliences then probably there could be some configuration issue that
> require you to put static mapping for dns.
>
> Regards
> /it.
>
>
>
>
> ----- Original Message -----
> From: "Danny" <nocmonkey@xxxxxxxxx>
> To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
> Sent: Thursday, September 30, 2004 10:13 PM
> Subject: [exchangelist] Re: RES: RE: Cannot connect Outlook to Exchange
> through VPN (Resolved)
>
>
> > http://www.MSExchange.org/
> >
> > On Thu, 30 Sep 2004 14:38:01 +0800, itelephone <itelephone@xxxxxxxxxxx>
> wrote:
> > > http://www.MSExchange.org/
> > >
> > > hi denny
> > >
> > > I do not think itis the right way to make it work .. if you have a dns
> > > server and your dns record pointed & hosted in your local server then
it
> > > should work without doing all these static route, all should come
from
> your
> > > DHCP server, if you have any.
> >
> > If you are at a remote location, you would receive their TCP/IP
> > settings either through DHCP or manually based on their network
> > configuration. Given that, now you should be able to access the
> > Internet, and then your corporate VPN (which has different network
> > settings).
> >
> > My VPN client creates a virtual adapter, which, once authenticated to
> > the VPN server, receives the appropriate TCP/IP information to then
> > communicate with the corporate network through the VPN.
> >
> > However, if you were a Windows application, which TCP/IP information
> > would you rely on, the real network adapter in or some third party
> > virtual adapter.
> >
> > For these reasons, this is why our internal DNS server has to be
> > manually specified in the TCP/IP settings of the real (non-virtual)
> > network adapter.
> >
> > I will be in communication with my VPN vendor.
> >
> > Future communication on this topic should be directed off-list,
> > because this has nothing to do with Exchange anymore.
> >
> > ...D
> >
> > ------------------------------------------------------
> > List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
> > Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
> > Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
> > ------------------------------------------------------
> > Other Internet Software Marketing Sites:
> > World of Windows Networking: http://www.windowsnetworking.com
> > Leading Network Software Directory: http://www.serverfiles.com
> > No.1 ISA Server Resource Site: http://www.isaserver.org
> > Windows Security Resource Site: http://www.windowsecurity.com/
> > Network Security Library: http://www.secinf.net/
> > Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
> > ------------------------------------------------------
> > You are currently subscribed to this MSEXchange.org Discussion List as:
> itelephone@xxxxxxxxxxx
> > To unsubscribe visit
> http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
> > Report abuse to listadmin@xxxxxxxxxxxxxx
> >
>
Other related posts:
