Re: Outlook 2003 over VPN to Exchange 2003

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Ray (reply_in_at_newsgroup.only)
Date: 05/04/04 

Date: Tue, 4 May 2004 10:01:39 -0400

There's a KB from MS that discusses this. It changes Kerberos to use TCP or
UDP or the opposite of whatever it's using now. Can't remember offhand.

Ray

"Digitus" <digitus@hotmail.com> wrote in message
news:u1$lwa5LEHA.1388@TK2MSFTNGP09.phx.gbl...
> Well after a lot of investigating and packet sniffing we have finally
found
> the cause of this problem. It turned out that our VPN solution was the
cause
> of the problem and it was dropping Kerberos packets. Outlook 2003
obviously
> utilises Kerberos as the preferred method, whereas Outlook 2000 used NTLM.
> I've now built up a Windows 2000 VPN server and it works fine over that.
> There also seems to be some discrepency in the implementation of the
> Kerberos RFC protocol causing different behaviour over different VPN
> solutions. In general if you have problems with connecting to internal
> resources over VPN, I would recommend that you try the same over W2K VPN,
> and see if that works..
>
> Best regards
>
> Digitus
>
>
> "Cameron" <anonymous@discussions.microsoft.com> wrote in message
> news:190601c426e0$4d133250$a501280a@phx.gbl...
> > We ran into a similar error at our location with VPN
> > connectivity. Our unrestricted VPN connection worked
> > perfectly but our restricted (specific IP addresses which
> > they could access) was failing. What we found was the
> > following needed to be available via VPN:
> >
> > Domain Controllers
> > Exchange 5.5 server (historical)
> > Exchange 2003 mailbox server
> > Exchange 2003 SRS server/ADC server - this was what was
> > causing our inability to send/receive email from the VPN
> > connection.
> >
> > >-----Original Message-----
> > >Out of curiosity, what VPN solution are you using? I've
> > managed to get it
> > >working by connecting through one of our satelite offices
> > that uses a
> > >different VPN solution than ours...
> > >
> > >Digitus
> > >
> > >
> > >
> > >"Joe_C" <jcorrigan@mdaturbines.com> wrote in message
> > >news:0f7501c42614$6e76fe30$a301280a@phx.gbl...
> > >> Also - Take a look at this:
> > >>
> > >> http://www.it-faq.pl/mskb/824/123.HTM
> > >>
> > >> Joe_C
> > >>
> > >> >-----Original Message-----
> > >> >Hi
> > >> >I've got some strange connectivety issues that I can't
> > >> seem to work out and
> > >> >that I'm desperate to resolve.
> > >> >
> > >> >Background:
> > >> >We are in the middle of migrating user from Exchange
> > 5.5
> > >> (running on W2K) to
> > >> >Exchange 2003 (running on W2K3). We have some clients
> > >> that are on Outlook
> > >> >2000 and some that are on Outlook 2003, but everything
> > >> is mixed. I.e. we
> > >> >have Outlook 2000 users on both Exchange 5.5 and 2003
> > as
> > >> well as Outlook
> > >> >2003 users on both Exchange 5.5 and 2003.
> > >> >We have a mixture of Windows 2000 Profeesional and
> > >> Windows XP.
> > >> >We are NOT using RPC over HTTP.
> > >> >
> > >> >Problem:
> > >> >Outlook 2000 always work fine both on the local LAN and
> > >> over VPN to both
> > >> >Exchange 5.5 and Exchange 2003.
> > >> >
> > >> >Outlook 2003 however is giving me some headache. For a
> > >> user that resides on
> > >> >Exchange 5.5, Outlook 2003 (cached mode) works
> > >> brilliantly, but after I've
> > >> >moved a user from Exchange 5.5 to Exchange 2003 that
> > >> user has difficulties
> > >> >connecting to the Exchange 2003 server over VPN. In the
> > >> office on the local
> > >> >LAN everything works fine, but when connected over VPN
> > >> the Outlook 2003
> > >> >client shows the status as "Trying to connect...". The
> > >> Outlook 2003 will
> > >> >stay in this status for a long time (normally about 8
> > >> minutes from my
> > >> >observations) and during this period the Outlook 2003
> > >> client seems "frozen".
> > >> >In the end it will finally connect (at least for me,
> > but
> > >> some of my users
> > >> >say it never connects) and everything will seem OK.
> > >> >
> > >> >Here is what I've tried so far:
> > >> >Creating a new Outlook profile.
> > >> >Changing the RPC binding order.
> > >> >(http://support.microsoft.com/default.aspx?scid=kb;en-
> > >> us;325930)
> > >> >Reinstalling TCP/IP on XP to make sure that everything
> > >> binds correctly.
> > >> >Reinstalling Office 2003
> > >> >Changing the DNS settings according to the newsgroup
> > >> posting "Outlook 2003
> > >> >over VPN on XP client delay" on the 10th of March by
> > >> JDTHREE [MVP].
> > >> >Any combination of the above.
> > >> >
> > >> >I'm not sure it is Outlook 2003 that is the problem,
> > but
> > >> rather a
> > >> >combination of Outlook 2003 and Exchange 2003.
> > >> >
> > >> >Does anyone have any idea how I can fix this as it has
> > >> stopped the migration
> > >> >to Exchange 2003?
> > >> >
> > >> >Thanks
> > >> >
> > >> >Best regards,
> > >> >
> > >> >Jan.
> > >> >
> > >> >PS. This is is posted on:
> > >> >microsoft.public.outlook.general
> > >> >microsoft.public.exchange.clients
> > >> >microsoft.public.exchange.connectivety
> > >> >
> > >> >
> > >> >.
> > >> >
> > >
> > >
> > >.
> > >
>
>

Relevant Pages

  • Re: Outlook 2003 with active VPN connection not sending
    ... I work remotely by VPN, but connect to my SMTP servers directly. ... There seems to be a lot of evidence that this is not a network connectivity ... To add to this, Outlook Express ... Is the Outlook associated to the VPN connection. ...
    (microsoft.public.outlook)
  • Re: Outlook Vs Outlook Anywhere
    ... We've many users who go overseas and hook up in hotels and then find that because the hotel LAN is on the same IP range as the office LAN they cannot resolve the Exchange server fqdn. ... outlook as though they were on the LAN. ... IIRC, prior to SBS 2003, VPN used to be the only way to allow remote ... > Anywhere type connection as opposed to regular Outlook connected to> Exchange ...
    (microsoft.public.windows.server.sbs)
  • Re: Help with user using POP acc, now hosting SMTP mail
    ... That's Outlook Web Access. ... connection isn't required. ... A VPN connection isn't ... If you're on a remote computer with an internet connection, and your SBS ...
    (microsoft.public.windows.server.sbs)
  • Re: Outlook 2003 client
    ... 2-factor for any inbound connection. ... about the benefits of RWW and OWA versus the pain in the neck of VPN. ... Then, when they're in the office, they can sync stuff like ... >> All of this is done in Outlook Send and Receive settings. ...
    (microsoft.public.windows.server.sbs)
  • Re: OL2007B2 - Cannot Connect To Exchange Through VPN
    ... Outlook FAQ, HowTo, Downloads, Add-Ins and more ... the VPN connection is on another non-routable subnet. ...
    (microsoft.public.outlook.installation)