Re: migrated 2003 domain causing Dell servers to hang

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

Date: 29 Nov 2004 01:14:28 -0800

Hi Rebecca,

I am sorry elements of my posting may have not been articulated
properly.

In your kind response you said:

Hi Alex,

This issue seems uncommon. I have a couple of questions regarding to
this issue:
1. Do you mean the win2k3 server DC migrated from NT shutdown very
slowly if you join Dell 1850s and 750s into win2k3 domain?

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Our problem is that the two new member servers, the 750 and then the
1850 take over 3 and a half minutes to shut down when they are made
members of our migrated NT4 to Windows 2003 domain. Prior to being
joined to the domain as member servers, the two Dell products take
just 2-3 seconds to shut down

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

2. Are Dell 1850s and 750s member servers or you have promoted them
to be an additional DC?

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

No these servers are member servers. They are currently not running
any applications as we have never got far enough into the build to
install any applications because of the problems with the shutdown
issues

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

3. Does this issue immediately disappear if you disjoin Dell 1850s
and 750s from Win2k3 domain?

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

No it can take up to two reboots to restore the server to normal
behaviour, once it has been removed from the domain

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Many Thanks for your reply

Alex Tanner

bladeraptor@hotmail.com (bladeraptor) wrote in message news:<b65f1e85.0411260231.6eb5b42f@posting.google.com>...
> 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: Dcidag errors
    ... Port blockage between servers ... Other sorts of networking issues (lack of connectivity between the points ... These errors are typically a result of a network connectivity issue of some ... > replicating this nc. ...
    (microsoft.public.windows.server.active_directory)
  • Re: I need Job Blobb
    ... > Windows and Network administratation. ... > In a job I would like to administrate servers, ... > Title: ISP Network Administrator ... > o Building, installation, configuration and tuning ...
    (microsoft.public.cert.exam.mcse)
  • Re: I need Job Blobb
    ... > Windows and Network administratation. ... > In a job I would like to administrate servers, ... > Title: ISP Network Administrator ... > o Building, installation, configuration and tuning ...
    (microsoft.public.cert.exam.mcse)
  • Event Viewer Networking Connectivity
    ... What we need is a very solid working network. ... Here's what lead up to this scenario of BDC replacement. ... On the corporate side I can see our servers. ... Registration of the DNS record ...
    (microsoft.public.windows.server.networking)
  • Help with initial small org AD setup convention when using DMZ network
    ... firewall which then connects the public IP dmz network to a private IP ... domain name for such subnets based on the nearest airport code, ... Yahoo to manage my externally-visible DNS names on the acme.com domain. ... and servers that use this domain, ...
    (microsoft.public.win2000.active_directory)
Loading