J
Junior
Greetings,
First let me get the platform layout out of the way.
Client: Windows 2000 laptop running Office 2003. Outlook 2003 w/o BCM
installed.
Running in Exchange Cached Mode. Remote laptop connecting via
VPN from NC
(PPTP). Runs Zone Alarm firewall software on laptop.
Server: Windows 2000/Exchange 2000 with latest SP and April 04 security
rollup patch.
Located in TX.
Firewall :Watchguard Firebox 1000. Acts as VPN server. Client connects to
firewall via PPTP
VPN connection. Access provided to internal network.
Ok so now that I have the basics out of the way. Here is what is occurring.
My client is using BellSouth DSL in NC. He started having trouble
connecting to our Exchange server Tuesday night of this week.
He has already made contact with his ISP and has gone through all the
checks.
Internet access is readily available and user is able to login to OWA via
http. This eliminates his password having expired
When the user opens Outlook 2003, he is prompted for his domain credentials
which he supplies and in the lower right hand corner, the display reads
"Trying to connect" and shows activity with the Outlook icon in the system
tray.
It reads that "Send/Receive is 50% complete" Then he receives an error that
the server is unavailable when trying to receive and that "Outlook must be
online in order to complete the connection".
I have had the user turn off his Zone Alarm thinking it had blocked the
application, but this did not yield a different result. I went through all
the profile settings and everything was checked out. I even went into the
Internet Options to make sure his connections settings were not fouled up,
they were all fine.
Again, no changes were made to how he or the other remote users are able to
connect via our corporate firewall, which I feel confident then in
eliminating that piece of the puzzle. He has internet access and is able to
authenticate with our firewall and gain access into our network.
The last time I encountered something this strange was back when Blaster ran
wild and ISP' s blocked the ports 135-139 to limit spread and thus caused
this user to have to move to DSL from his previous broadband connection.
Does this sound like a problem with Cached Mode Outlook 2003? I have not
had an opportunity to dive into it and am wanting direction as to where I
should check from here. This all came crashing down for this user on
Tuesday night/Wednesday Morning of this week, so there must be something
that I am missing and need checking.
First let me get the platform layout out of the way.
Client: Windows 2000 laptop running Office 2003. Outlook 2003 w/o BCM
installed.
Running in Exchange Cached Mode. Remote laptop connecting via
VPN from NC
(PPTP). Runs Zone Alarm firewall software on laptop.
Server: Windows 2000/Exchange 2000 with latest SP and April 04 security
rollup patch.
Located in TX.
Firewall :Watchguard Firebox 1000. Acts as VPN server. Client connects to
firewall via PPTP
VPN connection. Access provided to internal network.
Ok so now that I have the basics out of the way. Here is what is occurring.
My client is using BellSouth DSL in NC. He started having trouble
connecting to our Exchange server Tuesday night of this week.
He has already made contact with his ISP and has gone through all the
checks.
Internet access is readily available and user is able to login to OWA via
http. This eliminates his password having expired
When the user opens Outlook 2003, he is prompted for his domain credentials
which he supplies and in the lower right hand corner, the display reads
"Trying to connect" and shows activity with the Outlook icon in the system
tray.
It reads that "Send/Receive is 50% complete" Then he receives an error that
the server is unavailable when trying to receive and that "Outlook must be
online in order to complete the connection".
I have had the user turn off his Zone Alarm thinking it had blocked the
application, but this did not yield a different result. I went through all
the profile settings and everything was checked out. I even went into the
Internet Options to make sure his connections settings were not fouled up,
they were all fine.
Again, no changes were made to how he or the other remote users are able to
connect via our corporate firewall, which I feel confident then in
eliminating that piece of the puzzle. He has internet access and is able to
authenticate with our firewall and gain access into our network.
The last time I encountered something this strange was back when Blaster ran
wild and ISP' s blocked the ports 135-139 to limit spread and thus caused
this user to have to move to DSL from his previous broadband connection.
Does this sound like a problem with Cached Mode Outlook 2003? I have not
had an opportunity to dive into it and am wanting direction as to where I
should check from here. This all came crashing down for this user on
Tuesday night/Wednesday Morning of this week, so there must be something
that I am missing and need checking.