Hi Guys,
Running an exchange box here, and have clients connecting via outlook - seems to take ages to get connected - is this due to the size of the mailboxes or what?
Can I speed this up? if so how
David
Also - OwA for PDAs - how can I use this?
Hi Guys,
Running an exchange box here, and have clients connecting via outlook - seems to take ages to get connected - is this due to the size of the mailboxes or what?
Can I speed this up? if so how
David
Also - OwA for PDAs - how can I use this?
How big are the mailboxes?
How are they connecting? Direct over a Lan, VPN or RPC over HTTPS?
OWA (outlook web access) is accessible internally by doing http://servername/exchange. Externally you'd enter you external DNS name for the server instead of its hostname.
OMA (outlook mobile access) is great for phones or PDA's. Access it the same way as the above, but change the /exchange to /oma
Over Lan - via my WiFi - all 54Mbit at least
OmA - will try
MB - 1GB I think (how can I check?)
Hmm oma - and serving webpages is really slow on the server - and I have no idea why - even when on the local domain.
Yet /exchange works...Your user account has not been enabled for wireless access. Please contact your system administrator for additional assistance.
depends on config also
had this with my own until I tweaked the settings. presume it's exchange 2003?
Also - is it exchange full - or sbs?
OMA isn't enabled by default - you can check in a standard web browser. You'll need to use your e-mail address to login, as this is set in the configuration for OMA.
Also - are you using rpc over http? Depending on the way this is configured, some changes may be required on the server.
Is the client outlook machine a member of the domain? I find non-domain password authntication pretty slow compared to NT authentication.
Might be better to use an IMAP based webmail client like squirrelmail - dead easy to set up, very fast, and free (linux oinly though)
Robert
nah - not for exchange. don't get calendar, contact or gal.
back to basics I suppose.
1) Are all clients connecting within the office
2) hardwired or wireless?
3) using which versions of outlook?
4) cached copy enabled
5) not using roaming profiles
external use (rpc over http if exchange 2003 and outlook 2003):
1) running xp sp2
2) fully patched outlook 2003
3) set to use tcp as default over both fast and slow connections
4) encrypted channel in use
5) if sbs - were clients configured for rpc over http in office, or out of office (makes a difference to how registry was configured)
OWA or OMA:
1) using DOMAIN\UserName rahter than DOMAIN\username or logon e-mail address (username@domain.local) or public e-mail address (nickname@domain.com) - in fact applies for all connection modes.
2) IE6 SP1 - test on ffox also, for basic interface (speed of connection/response)
3) forms-based authentication enabled (provides full logon screen, where can choose full/basic and security settings)
4) gzip compression enabled
5) alternate exchangehttp configured to override rpc and http specific settings, and enable tuned settings for OMA (I use one of each for http and oma to make sure that if OMA crashes - it doesn't bring down rest of connection modes)
There are currently 1 users browsing this thread. (0 members and 1 guests)