Re: Diagnosing client connection problems

Thanks. I will try that.

"John Oliver, Jr. [MVP]" wrote:

I have seen this in other cases regarding MTU size in hardware VPN's between
sites so this is why I mentioned it. I would match the MTU setting at Corp
for both remote site Routers.

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2007
Microsoft Certified Partner


"Brian" <Brian@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:77C7AF94-49E2-499A-B147-512AACF55D75@xxxxxxxxxxxxxxxx
One more MTU. Ping of corp router's WAN address from remote workstation:
1444.

And, I see that the remote routers were set to 1500, which should
represent
1472 + IP (20) + ICMP (8). I reset one of them to 1468 to match the corp
side, and was able to get onto Exchange remotely on the first try (first
time
tonight). I don't know if that is a permanent fix, but it appears that you
may well have pinpointed the cause. I've never really given MTU's a second
thought, as all these routers seemed to have worked correctly as they were
factory configured.

Do I need to match the lowest one that works and set it for all the
routers?

"John Oliver, Jr. [MVP]" wrote:

Brian,

Have you tried rebuilding the VPN Tunnel? What is the MTU setting on
your
VPN tunnel? Very possible you are seeing fragmentation across your VPN.
You might try lowering it. What type of hardware are you using for your
VPN?

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2007
Microsoft Certified Partner


"Brian" <Brian@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:20BFD1CC-FFB7-4BE5-A525-2BC942AB9F70@xxxxxxxxxxxxxxxx
...one more thing. Users can generally reconnect after clicking Retry a
few
times. As of this moment, computers in one remote office can open on
the
first try, but computers in the other office must click Retry at least
once
(limited test of a couple of PC's in each office).

"John Oliver, Jr. [MVP]" wrote:

Sounds like a WAN issue. Can you successfully login with OWA over the
VPN
when Outlook users start having issues? Do the Outlook users at the
main
location have issues with Outlook when the Remote office is having
problems?
You need to narrow the issue down to Exchange at main location or VPN
issues
with remote offices

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2007
Microsoft Certified Partner


"Brian" <Brian@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AFEB6841-21C2-4B7E-AB8B-D9FBD8E859C2@xxxxxxxxxxxxxxxx
Corporate office
-Exchange 2000 as part of SBS 2000
-Full T-1
-hardware VPN

Remote offices (2)
-Outlook 2003
~1 MB DSL
-hardware VPN to corporate office

Everything has been working fine until about three weeks ago.
Suddenly,
users at both remote offices start receiving "Your Microsoft
Exchange
Server
is unavailable" messages and have to Retry three or four times or
more,
sometimes unsuccessfully, before they can get Outlook to start.

The problem appears to be intermittent. The users reported it over a
few
days a few weeks back, so I logged on remotely to a station in the
evening,
and Outlook opened no problem.

However, I just tested now on a Saturday evening with very few users
logged
onto the Exchange server, and it is is consistently failing. I
rebooted
all
the routers as a first step a couple of weeks ago. I also flushed
the
DNS
cache when I noticed that the PC I was testing, when pinging the
server's
internal DNS name, returned the public IP address of the Exchange
server
(it
has dual NIC's - on on the LAN, on on the WAN).

Ping of the Exchange server by its internal (LAN) DNS name is
successful
at
about 25ms. Restart of Exchange services on server had not effect.

I'm lost on how to logically work my way down to the cause. Ideas?



.

Relevant Pages

  • Re: Diagnosing client connection problems
    ... Ping of corp router's WAN address from remote workstation: ... and was able to get onto Exchange remotely on the first try (first time ... Have you tried rebuilding the VPN Tunnel? ... Remote offices ...
    (microsoft.public.exchange.connectivity)
  • RE: Accessing Exchange 2000 Remotely
    ... Subject: Accessing Exchange 2000 Remotely ... web servers in the same DMZ with it. ... perhaps a better alternative would be to put your exchange server ... Our remote users have ...
    (Focus-Microsoft)
  • Re: Errors after a clean install of SBS2K3
    ... I meant Exchange 2K3 SP1. ... > I had to reinstall SBS 2K3 because of a faulty motherboard. ... > The following settings were successfully configured by the Remote Access ... > server provided with Windows Small Business Server 2003. ...
    (microsoft.public.windows.server.sbs)
  • Re: Ask your opinion on this
    ... The remote site does not access any resource from this company. ... just manage and set up exchange server and second domain controller ... install exchange on DC and it's not supported? ... one domain controller windows 2003 standard. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Cannot shutdown server
    ... Doesn't shutdown remotely either. ... Exchange problems off and on - the hardware is rubbish. ... > You could try shutting down from a remote desktop connection, ... > server and maybe even doing an offline Exchange Server backup. ...
    (microsoft.public.backoffice.smallbiz2000)
Quantcast