one other thing that I know we had run into here a long while ago was the
issue of the RPC binding order on machines causing clients to hang on
launch.. I can't remember the QFile right now but the key name is
HKLM\SOFTWARE\Microsoft\Exchange\Exchange Provider and the Value to look at
is Rpc_Binding_Order in which we would sometimes have ipx and spx ahead of
tcp and rpc when our Exhange server had no ipx or spx bindings.. I suppose
as a long shot you could check this on those machines but again since it's
just over the VPN connection I don't know if this would be a solution or
not... again my experience is completely with Exch 5.5/NT 4 so use at your
own risk and remember editing the registry could cause temporary blindness,
premature baldness and severe cases of depression... ;)
Charles
Charles F. McKnight
PC/Lan Specialist
Mercy Health System - NWA
[EMAIL PROTECTED]
> -----Original Message-----
> From: Michael Marchiondo [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, September 06, 2001 3:53 PM
> To: Exchange Discussions
> Subject: RE: E2K Windows-98 VPN Connection Problem
>
>
> Folks,
>
> Thanks for all the suggestions. The client is a Microsoft VPN PPTP
> connection.
>
> We have verified the DNS and WINS settings are correct on both servers
> (Exchange 5.5 and Exchange 2000). We have verified the DNS and WINS
> settings on the client after the VPN connection comes up. We
> can from the
> client:
>
> ping e55.domain.com successfully (e55 = exchange 5.5 server)
> ping e55 successfully
> ping e2k.domain.com successfully (e2k = exchange 2000 server)
> ping e2k successfully
> RPingc e2k Rping successfully
> RPingc e2k Store successfully
> Rpingc ek2 Admin successfully
> ping ad.domain.com successfully (ad = active domain controller)
> ping ad successfully
>
> If I point the Windows-98 profile at the e55 server, the profile is
> automagically updated to point to the e2k server but then it
> hangs. It
> hangs forever by the way.
>
> I noticed that the registry entry in the profile on a Windows
> 2000 box gets
> updated to point to ad.domain.com (the 01e6602 string value in the
> \dca740c8c042101ab4b908002b2fe182 key) like it is supposed to
> but this isn't
> happening on the VPN 98 box. I tried adding the value with
> no such luck.
>
> I follow the logic and I keep thinking name resolution
> problem but when I
> try all the above it doesn't make sense.
>
> Michael
>
> > -----Original Message-----
> > From: Michael Marchiondo [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, September 06, 2001 1:35 PM
> > To: Exchange Discussions
> > Subject: E2K Windows-98 VPN Connection Problem
> >
> >
> > Hello Folks,
> >
> > This one has me stumped and my next stop is PSS but I thought
> > I would try
> > here first.
> >
> > We have been running Exchange 5.5 in our Windows 2000 domain
> > for quite some
> > time with the ADC. When E2K SP1 was released we started
> planning our
> > migration. We installed the E2K server in the same site and
> > moved all the
> > mailboxes to the new server. We setup our cc:Mail
> connector and SMTP
> > connector on the new server and disabled the old ones.
> >
> > Despite a few bumps it is working fairly well. We have a
> > mixture of Windows
> > 2000, NT 4.0, 98, and one ME client all using Outlook 2000.
> Everybody
> > connects fine on the LAN.
> >
> > Some clients connect to the LAN via a VPN connection. All
> > Windows 2000
> > clients connecting this way work fine. The Windows 98 and
> > one ME client do
> > not. When starting Outlook these clients just hang forever.
> >
> > When looking at the profile we see that the server name has been
> > automatically switched as usual. However, if we rebuild the
> > profile and try
> > to resolve the mailbox name, that too hangs forever. If we
> > create a mailbox
> > on the Exchange 5.5 server and try to resolve that it all
> > works fine. Any
> > attempt to contact the Exchange 2000 server instead results
> > in the process
> > hanging - only on 98 and ME. Win2K works fine.
> >
> > We can map shares, ping, and do all kinds of other network
> > things from these
> > Windows-98 clients via VPN to the Exchange 2000 server. The
> > connectivity
> > seems to be there. We have tested with RPCPing and so on as
> > well and that
> > all works.
> >
> > I can't figure out what VPN would have to do with it and why
> > it works fine
> > for Windows 2000 clients. All work fine on the LAN. We have
> > only seen this
> > problem with VPN and only to the Exchange 2000 server - not
> > the Exchange 5.5
> > Server. We also tried installing the Active Directory client
> > add-on for
> > Windows 9x (DSCLIENT) and that didn't fix it either.
> >
> > Any thoughts?
> >
> > Thanks,
> >
> > Michael
> _________________________________________________________________
> List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
> Archives: http://www.swynk.com/sitesearch/search.asp
> To unsubscribe: mailto:[EMAIL PROTECTED]
> Exchange List admin: [EMAIL PROTECTED]
>
> _________________________________________________________________
> List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
> Archives: http://www.swynk.com/sitesearch/search.asp
> To unsubscribe: mailto:[EMAIL PROTECTED]
> Exchange List admin: [EMAIL PROTECTED]
>
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
