KirkM
Tue May 06 08:26:07 PDT 2008
I didn't specify which system to run dfsutil on but did you run dfsutil on
the XP workstations?
You may also want to check the workstations for any \\oldserver UNC mappings
(network printers, network shares, my network places history), delete any
references to the old server.
"cef" wrote:
> I ran dfsutil /purgemupcache - no change.
>
>
>
> "Kirk M" wrote:
>
> > You may also want to run dfsutil /purgemupcache
> > Many IT people said they have experienced better network performance after
> > they run it.
> >
> > You can find dfsutil in supporttools.msi on the Server 2003 CD.
> >
> >
> > Kirk
> >
> >
> > "cef" wrote:
> >
> > > Thanks for DNSLint. It's a good utility. Unfortunately, it didn't show any
> > > issues with DNS. I would have thought that this was a DNS issue too, but I
> > > can't find anything wrong. This is a very frustrating problem! All machines
> > > (all servers and desktops) have been rebooted several times. I do have all
> > > HP Proliant servers but each has only one NIC enabled with a single IP
> > > address bound.
> > >
> > > I appreciate your thoughts, though!
> > >
> > > If anyone knows where I can find the steps Outlook takes when it starts up
> > > and attaches to Exchange, I would appreciate it.
> > >
> > > "Kirk M" wrote:
> > >
> > > > Since the server you are shutting down was originally a DC I'm going to
> > > > assume it ran DNS as well. This sounds like a definite DNS issue where your
> > > > Exchange server still wants to use the old DNS server for resolution.
> > > > Try using DNSLint to help diagnose DNS name resolution issues.
> > > >
http://support.microsoft.com/kb/321045
> > > >
> > > > You may also want to try and flush/register dns on the Exchange box.
> > > >
> > > > Just out of curiosity, is the Exchange box a HP Proliant system? If so does
> > > > it have 2 or more network cards?
> > > >
> > > >
> > > >
> > > > "cef" wrote:
> > > >
> > > > > Thanks for the idea but this network has never used WINS. Should have
> > > > > mentioned that earlier.
> > > > >
> > > > > I'll try creating a new user with the server unplugged to see what happens,
> > > > > but that wouldnt be a pracitical solution for existing users. This is an
> > > > > environment where it's unacceptable for people to lose and have to recreate
> > > > > their settings.
> > > > >
> > > > > "Hal Hostetler [MVP P/I]" wrote:
> > > > >
> > > > > > Long shot, but maybe WINS? Have you tried re-creating the Outlook profile
> > > > > > with the old DC turned off?
> > > > > >
> > > > > > Hal
> > > > > > --
> > > > > > Hal Hostetler, CPBE -- hhh@kvoa.com
> > > > > > Senior Engineer/MIS -- MS MVP-Print/Imaging -- WA7BGX
> > > > > >
http://www.kvoa.com -- "When News breaks, we fix it!"
> > > > > > KVOA Television, Tucson, AZ. NBC Channel 4
> > > > > > Live at Hot Licks - www.badnewsbluesband.com
> > > > > >
> > > > > > "cef" <cef@discussions.microsoft.com> wrote in message
> > > > > > news:BA2F5A64-0418-471E-BBCE-38302589794B@microsoft.com...
> > > > > > > Problem - when I shut down an old Windows 2000 server that USED TO BE a
> > > > > > > domain controller, though NEVER an Exchange server, Outlook 2003 becomes
> > > > > > very
> > > > > > > slow to open on every machine on the network.
> > > > > > >
> > > > > > > Environment:
> > > > > > > -single Exchange 2003, fully patched with all Microsoft updates / Outlook
> > > > > > > 2003, also fully patched with all available updates.
> > > > > > > - Network of about 40 users
> > > > > > > - NO RPC over HTTP
> > > > > > > - NO cached Exchange mode
> > > > > > > - NO .pst or .ost files permitted
> > > > > > > - no IMAP or POP3 connections are permitted
> > > > > > > - No ActiveSync connections are permitted
> > > > > > > - single Exchange server, no front end/back end configuration.
> > > > > > > - Currently, there are 2 domain controllers on the network, both
> > > > > > functioning
> > > > > > > without error (the Exchange server and another server).
> > > > > > > - Domain is in mixed mode.
> > > > > > > - No firewalls, Windows or otherwise, between desktops and Exchange.
> > > > > > > - No related errors in event logs of servers or desktops
> > > > > > > - No AD errors on domain controllers
> > > > > > > - No DNS issues
> > > > > > >
> > > > > > >
> > > > > > > Issue:
> > > > > > > We have an old Windows 2000 server, that was the original domain
> > > > > > > controller/file print server for the domain. About 3 years ago, we
> > > > > > installed
> > > > > > > a new Windows 2003 server and moved all of the AD rolls, DNS and DHCP off
> > > > > > of
> > > > > > > the old server and onto the new server. This server was NEVER an Exchange
> > > > > > > server. We disabled DNS and DHCP serivces at that time and ran DCPromo to
> > > > > > > remove the old server from the domain. All went well. There were no
> > > > > > issues
> > > > > > > or errors. Unfortunately, we left the old server up and running just in
> > > > > > case
> > > > > > > there was a file that someone needed. The old server was left running in
> > > > > > the
> > > > > > > rack and was forgotten about.
> > > > > > >
> > > > > > > Now, we need to install some new servers and we need the rack space, so we
> > > > > > > have to fully decommission the old server. Everything works fine when we
> > > > > > > shut it down, EXCEPT for Outlook 2003. If the old server is shut down,
> > > > > > > Outlook takes over 3 minutes to open on every desktop on the network. The
> > > > > > > minute the server comes back up, Outlook opens normally.
> > > > > > >
> > > > > > > We moved from Exchange 2000 to Exchange 2003 (fresh install on new server,
> > > > > > > used Exmerge to move contents of mailboxes) about 2 years ago. The old
> > > > > > > Exchange server has been off of the network since the upgrade.
> > > > > > >
> > > > > > > If I open Outlook with the /rpcdiag switch with the old server down, the
> > > > > > > first 2 connections are made immediately, with normal speed. The delay is
> > > > > > > between the second and third connection.
> > > > > > >
> > > > > > > The Outlook web client continues to function normally, whether or not the
> > > > > > > old server is on.
> > > > > > >
> > > > > > > I have tried all the safe mode switches. /safe:1, safe:3 and safe:4 do
> > > > > > not
> > > > > > > affect startup speed. If I start in /safe:2 (starts Outlook without
> > > > > > checking
> > > > > > > mail at startup), Outlook opens at normal speed. I have also tried the
> > > > > > > /cleanprofile switch, which had no effect.
> > > > > > >
> > > > > > > Other than the issue with Outlook, all logins/network applications and
> > > > > > > resources function normally, whether the old server is up or not.
> > > > > > >
> > > > > > > I searched through the registry of one of the desktops. I do not see any
> > > > > > > references to the old server by either name or IP address.
> > > > > > >
> > > > > > > I would appreciate any ideas on how to resolve this problem.
> > > > > > >
> > > > > >
> > > > > >
> > > > > >