R
Robert Hedley
Hi,
Thanks for your suggestions. Unfortunately this did not
help.
Just incase it helps I have a bit more info on the
configuration of the laptops.
The network cards receive their configuration from an MS
DHCP server. The DHCP server settings have a default
gateway set to the ISA server, therefore making the
laptops a securenat client for ISA server.
We also have the ISA Firewall Client installed on them
which is turned on whilst in the office, but disabled
whilst out of the office.
Many thanks,
Robert Hedley
Thanks for your suggestions. Unfortunately this did not
help.
Just incase it helps I have a bit more info on the
configuration of the laptops.
The network cards receive their configuration from an MS
DHCP server. The DHCP server settings have a default
gateway set to the ISA server, therefore making the
laptops a securenat client for ISA server.
We also have the ISA Firewall Client installed on them
which is turned on whilst in the office, but disabled
whilst out of the office.
Many thanks,
Robert Hedley
..-----Original Message-----
Try turning off the "Instant Messaging"
Open the TOOLS menu
Select OPTIONS...
Select the OTHER tab
Turn off the check mark next to "Enable Instant Messaging
on Microsoft Outlook".
--
Nikki Peterson [MVP - Outlook]
Hi,
We have several laptop users who require full access to
the features of their Outlook XP mailbox whilst in and out
of the office.
Each laptop is running Windows XP Pro Sp1, Office XP Pro
Sp2, ISA Server Firewall Client, Internet Explorer 6.
The exchange server is running Windows 2000 Server Sp4,
Exchange 2000 Sp3, Internet Explorer 6.
The ISA Server is running Windows 2000 Server Sp4, ISA
Server 2000 Sp1 Fp1, Internet Explorer 6.
Each user within the network has an exchange mailbox which
Outlook is configure to use. When configuring the mail
profile of the user on the laptop the servername EXCHANGE1
was put in and it resolved fine. To open up access to
these facilities whilst out of the office I configured a
publishing rule on the ISA server which mapped Exchange
RPC from the public IP address of the network to the
Exchange1 server. So that the outlook profile worked when
out of the office I edited the c:\windows\system32
\drivers\etc\hosts file to include:
xxx.xxx.xxx.xxx EXCHANGE1 (i entered the public ip
address of the network as the ip address.
When some users connect into the system it is quite quick,
however for others it can be extremely slow. The same
problem exists when they are in the office too. I
understand that because of the hosts file they will be
going via the ISA server to get access to EXCHANGE1
however as it is local it should be quick. For some it is
quick and others very slow.
My users are starting to complain and I cannot find
anything that relates to this kind of problem on the
support pages or on google.
Any suggestions to resolve this issue or any better
methods wouyld be appreciated.
Kindest Regards,
Robert Hedley
.