Re: Outlook Connecting Via a Firebox VPN
From: todd (fatheree21_at_NOcomcastSPAM.net)
Date: 03/27/04
- Next message: todd: "Re: Mail relaying"
- Previous message: Mike McStravick: "Re: Outbound SMTP failing"
- In reply to: Shannon Sears: "Outlook Connecting Via a Firebox VPN"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 27 Mar 2004 00:09:16 -0600
With basically any VPN solution, not just Watchguard, I've always had to add
an entry into the HOSTS file of the remote systems for the mail server in
order to get the mail server name to resolve correctly in Outlook. Browsing
the network might eventually default to Netbios name resolution, but Outlook
doesn't seem to like anything but DNS or HOSTS. Often, the remote clients
use their ISP's DNS servers, which obviously don't have an entry for the
Exchange server's LAN address.
todd
"Shannon Sears" <anonymous@discussions.microsoft.com> wrote in message
news:12d7c01c411e0$4a450400$a401280a@phx.gbl...
>
> We have 12 remote users connecting to our corporate
> servers via a Firebox VPN from either dial up or high
> speed dsl connections.
>
> We can browse the network and conduct file transfers
> without issue but the connect of Outlook to Exchange is
> inconsistent.
>
> If the user is unable to connect on the 1st attempt... it
> often will not connect until the system is shutdown and
> restarted. Even this sometimes doesn't work.
>
> If the connection fails... exchange sometimes gives a
> message box that the user password is invalid.
>
> Switch the NETBois over TCP on (normally off) seems to
> make it work... but only temporarily.
>
> I have read several tech notes that mention using static
> ports.
>
> Any input would be appreciated... as Watchguard tells us
> its a Windows Connectivity issue.
>
> Shannon
- Next message: todd: "Re: Mail relaying"
- Previous message: Mike McStravick: "Re: Outbound SMTP failing"
- In reply to: Shannon Sears: "Outlook Connecting Via a Firebox VPN"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|