Initial Client Access to ExchPubFolders

If you've recently changed the name of your exchange server, outlook/windoze remembers the last config, and tries this first, it took a lan analyser for me to figure it out.
The simplest way to look for outlook start problems, is to put a host filein your win directory (or in the winnt\system32\driver\etc).
If this works fine, you have a name resolving problem.
Remember that the order of looking up hostnames is: local machine, host file, dns server, Netbios remote name cache,wins server,Broadcast, lmhost.
So if you have configured client computers with dns servers, make sure the first one is a dns server in your network, and preferably using wins lookup.
If your not using dns, but are using wins, and a dhcp server, make sure the nodetype is set to 0x8, if you dont have one add one !
Remember if you have a good functioning dns server in your network, you will have the best responses.

If you set up your name services on you interna network right, you shouldn't have any "timing" problems.

Good luck, Ron.

Exchange will verify the credentials of the client against a domain controller, in order to authenticate him as a valid user of the public folders. Check you event log on the exchange server and the PDC/BDC for errors. Also, compare the timing of the access attempt against the Security Log on the DC for Succesful login reconrds (you can enable the auditing).
I had a similar problem when my first Exchange site over WAN connection came online.
You can also turn on the detailed logging of thePublic information store to get a clearer picture of what's going on. I'd say that there is an authentication time-out, where your Exchange server tries to contact the domain controller your user account is on.
I hope this helps.
Regards,
Radu