migrated 2003 domain causing Dell servers to hang

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: bladeraptor (bladeraptor_at_hotmail.com)
Date: 11/26/04 

Date: 26 Nov 2004 02:31:38 -0800

Hi

We have bought in a clutch of new dell servers (1850s and 750s) into
our environent and something weird happens when we join them to our
migrated Windows NT4 - 2003 domain.

Usualy on our network, our existing collection of Dell servers running
SQL, file shares etc. take between 2 seconds and a minute to shut
down.

With these new servers, once we join them to the migrated domain they
go from taking 2-3 seconds to shutdown to up to 5 minutes to shutdown.

We have been bashing this backwards and forwards wih Dell for weeks
now - we inititally said it was problems with their architecture, then
with the Intel NICs on the servers and they in return said it was
incompatibilities with our 'vanilla' Cisco network environment.

Our partner Omnetica who is providing our Cisco Approved support have
verifed that as far as they can see it is not the physical network.

This is backed up by the fact that the servers behave normally when
physically connected to the network, i.e. accessing file resources and
ODBC connections into the domain (while not joined to it - but logged
on as local administrator n the server in question) The servers begin
this problem of not shutting down only when actually joined to the
domain.

We also tested creating a fresh 'vanilla' Windows 2003 domain and
added the problem servers to this. In this 'vanilla' Windows 2003
domain environment running over the same Cisco physical network. The
servers shut down normally

So as far as we can see the problem is around our migrated Windows2003
domain. Are you aware of any issues with for example Wins vs DNS in a
migrated environment causing network problems?

The consesnus now is that there must be some protocol traffic flying
arround that is leaving a session or something else open on these new
dell servers so they are unable to shut down normally

Any help or thoughts would be greatly appreciated

Kind regards

Alex Tanner

Relevant Pages

  • Re: Windows 2008 IPv6
    ... But for future planning i think you should always start the better way, to prevent yourself to reconfigure everything, when it comes to the point that your network grow up. ... So in the new environment I have 2 dell poweredge servers running ... I building the 2008 environment from scratch.. ... with that subnet mask you have a really big broadcast domain ...
    (microsoft.public.windows.server.networking)
  • I need Job Blobb
    ... I am a systems and network administrator looking for a ... Windows and Network administratation. ... In a job I would like to administrate servers, ... environment, creation ...
    (microsoft.public.cert.exam.mcse)
  • Re: [fw-wiz] Pix 535 Logging
    ... environment you should be able to. ... Have you thought about just blocking all outbound port 25 ... connections except for your authorized MX and mail servers? ... A Cisco Systems, Inc., Certified Network Associate ...
    (Firewall-Wizards)
  • Re: Understanding Mac OS X Open Directory
    ... relies on shared Open Directory domains to provide network user accounts ... other servers that are bound to the domain. ... XEROX Parc for the Smalltalk-76 programming environment, ...
    (comp.sys.mac.advocacy)
  • Re: Understanding Mac OS X Open Directory
    ... relies on shared Open Directory domains to provide network user accounts ... The shared domain can also allow users to access resources on ... other servers that are bound to the domain. ... XEROX Parc for the Smalltalk-76 programming environment, ...
    (comp.sys.mac.advocacy)