First a little bit of background. We have a single location where our servers are housed and most of our clients work from. We recently opened a new location which we are directly connected to via a T1 line. ALL of the users at the new location are running XP SP2 and connect to the domain controller (Win 2003 server) via the T1.
We are currently experiencing two problems. First when a user without a roaming profile cold boots their machine in the morning and opens outlook they are prompted in outlook for their username and password. No matter what they put in outlook will not take it and they have to log out, log back in, and everything is fine. If they log in, log out, and then log back in before opening outlook everything works fine. Second users with roaming profiles receive the error "Windows did not load your roaming profile...etc" when they log on from a cold boot. Their cached profile is loaded, but if they log off and back on everything loads up fine.
In the application log of ALL computers at the remote site we have the following event ID's. These errors do not occur on ANY of the machines at the local site.
Event 1054: Can not obtain DC computer name...etc.
Event 15: Failed to contact AD....etc.
There are other errors in the application log sporatically, but these are the only consistent errors. These errors only appear at the first logon after a cold boot, and do not reappear until the machine is shut down and cold booted again. I can provide more details if needed, I appreciate any help with this matter. I believe it is an error relating to the remote location PC's not being able to contact the DNS server (primary on DC, secondary on exchange) quick enough on a cold boot.