Strange behavior after workstation re-install
 

Environment: Small Windows Server domain with AD and Exchange 2003, fully
patched and SP'd, all workstations are PCs running fully patched and SP'd XP
Pro and Office 2003 in Cached mode, fully patched via Microsoft Update.
Workstations are connected to a Linksys router and through this to a DLS
Modem for Internet access.

Problem. Reformatted user's drive and reinstalled XP Pro and tried to
reconnect to the domain. Seems to take an inordinate amount of time for this
machine to boot up and shut down, like something is being attmpted in the
background unsuccessfully. Eventually it goes to the desktop. Now, if user
accesses Outlook, the status bar reports that Outlook is "Trying to
Connect". It stays like this for some time and eventually puts up the
authentication dialog, requiring the user to enter his domain login
credentials, every time, and then all the mail folders are updated.

Question: Why is this happening? It seems like there is something going on
in the background that shouldn't be. Every time this user logs into Outlook
he has to re-enter his credentials. And the long bootup and shutdown times
suggest something going on.

Do I have to do something on the server side to eliminate references to the
user's old machine and re-establish credentials for the new machine?

Any other idea? Many thanks.

(Sorry for the cross-posting, wasn't sure where this should be directed)

Strange behavior after workstation re-install
 

In ,
Robert Perez stated, which I commented on below:
Environment: Small Windows Server domain with AD and Exchange 2003,
fully patched and SP'd, all workstations are PCs running fully
patched and SP'd XP Pro and Office 2003 in Cached mode, fully patched
via Microsoft Update. Workstations are connected to a Linksys router
and through this to a DLS Modem for Internet access.

Problem. Reformatted user's drive and reinstalled XP Pro and tried to
reconnect to the domain. Seems to take an inordinate amount of time
for this machine to boot up and shut down, like something is being
attmpted in the background unsuccessfully. Eventually it goes to the
desktop. Now, if user accesses Outlook, the status bar reports that
Outlook is "Trying to Connect". It stays like this for some time and
eventually puts up the authentication dialog, requiring the user to
enter his domain login credentials, every time, and then all the mail
folders are updated.
Question: Why is this happening? It seems like there is something
going on in the background that shouldn't be. Every time this user
logs into Outlook he has to re-enter his credentials. And the long
bootup and shutdown times suggest something going on.

Do I have to do something on the server side to eliminate references
to the user's old machine and re-establish credentials for the new
machine?
Any other idea? Many thanks.

(Sorry for the cross-posting, wasn't sure where this should be
directed)

/Guesswork in play since you didn't provide any specific configuration info/

My first take on this is that your workstations and possibly servers (DCs
and other servers) are not ONLY using the internal DNS server that is
hosting the AD zone. This is a classic issue when providing the ISP's DNS in
a machine's IP properties, for it is asking the ISP's DNS, "Where is a
domain controller in my domain?" and of course, they don't have that answer.
If you are mixing ISP and internal DNS, the DNS resolver algorithm may still
be asking the wrong DNS. If the server has the loopback (127.0.0.1), change
that to the actual IP of the server.

If the above is the case, make sure that ONLY the internal DNS is specified
If need be, adjust your DHCP Option (Scope or Global) 006 to only specify
the internal DNS. Configure a forwarder for more efficient resolution to
your ISP. The articles below, depending on what OS you have, will help to
show you how to configure a forwarder.

323380 - HOW TO Configure DNS for Internet Access in Windows Server 2003
(forwarding) :
http://support.microsoft.com/?id=323380

300202 - HOW TO Configure DNS for Internet Access in Windows Server 2000
(forwarding) :
http://support.microsoft.com/?id=300202

Now, if the DC is multihomed, then that's a whole other ballpark that causes
numerous issues, along with using the wrong DNS addresses and requires
modifications, including reg changes to FORCE it to work properly. If
multihomed, my easiest recommendation is to use a non-DC for multihoming, or
if it is a NAT device, I would suggest to disable one of the NICs and
acquire an inexpensive Linksys router to perform that function instead of
making all those modifications. If it is multihomed and you would like to
keep it that way, I can post the necessary 10 or so steps to make it work.

I hope that helped.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.

It's easy:
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Assimilation Imminent. Resistance is Futile
Infinite Diversities in Infinite Combinations

"Very funny Scotty. Now, beam down my clothes."

The only thing in life is change. Anything more is a blackhole consuming
unnecessary energy.