I'm have a couple of problems that appear to be related, Running Exchange 2003 on the server with the "problem" clients running XP SP3. Some users are being asked for credentials when they open outlook, one of the users only has it happen after a computer reboot. These same users will from time to time (no discernible pattern to the timing or potential cause) are unable to access several mapped network drives we have, they get an error something to the effect of "Windows cannot access the network drive. The name is already in use" They can find the folders in My Network Places but when they try to open they are asked for credientals and then given "Unable to connect to the network resource that authenticated you" error. I have tried several solutions to the Outlook problem that were outlined in a MS support article that included a registry tweak, and renaming the folder in appdata\microsoft\protect. I also verified that the account setting in outlook was set to remember username and password. The only progress was of the 3 users that had to log in every time outlook was opened, one is now the one that only needs to sign in after a reboot. For the network drives the only thing that has worked is to reboot the computers. I have been working with computers for the better part of 16 years, but I haven't touched exchange until 5 months ago when as part of my new job I "inherited" a 7 year old network that was last upgraded about 4 years ago to server 2003 with exchange 2003. Every thing appeared to be working fine until a week ago, when a third party provider had some problems updating the anti-virus on the server. Now it is my "problem" to fix it.

There can be a lot of troubleshooting to this. #1 is there anything weird in the server logs? ERRORS??? Clear the logs and review them after the problem happens. #2 Make sure your server license has enopugh user licenses as users on the network. If you run out of licenses this can happen. #3 Verify permissions are setup correctly for the shared folders and reconfigure sharing and permissions if necessary. After all you inherited a neglected network and who knows if the previous admin or whomever set this up did so correctly. #4 Write a log on script that maps users to their assigned shared folders - drives. It wouldnt hurt to throw this in your script for good measure. ipconfig /flushdns nbtstat -R Note these are just a few things to check at first. Obviusly the troubleshooting can be extensive but this is a good place to start. If you are still stuck shoot me an email and I will help you out. Chris Ondo CFCEcorp.com

Hi Odysimus, Any update for your issue? Agree with Chris, please confirm those first. Other information for you, Per your description, some of the users have the issue, so please compare those with the users who work well. Does the issue related with the network for those users? Can the users use OWA work well on the issue client? Is there any some third party antivirus soft ware on the issue client, make a test after uninstall it. Do the issue client all join into the domain? Or post more infomation, we could do more research aobut it. Regards! gavin