R2 in-place upgrade bug ? ..HELP

Morning to all -

I just spent the last 6 hours with dell gold software support team trying to
figure out the following occurrence:

The upgraded R2 DC does not accept incoming connections, but it appears it
accepts certain connections. Particularly those related to directory services.
e.g. telnet server ip 389 from the mail server works. \\serverip or
servername brings up the shared printers and folders perfectly.

outbound traffic and icmp works fine, inbound icmp returns a time out.

scenario:

Windows 2000 SP4 DC in-place upgrade to windows 2003 SP1 then upgrade to R2.
connections to and from box were fine on 2003 sp1.
downgraded NIC drivers to match other r2 DC on identical server
hardware/model
installed new nic drivers and proset
upgraded to R2.
rebooted and noticed a ton of errors with services hanging upon boot.
checked connection to the box from workstations and servers, but all requests
timed out.
i made sure ICF was disabled.
i disabled IPSEC and entered dword value for ProhibitIpSec - nothing
i then enabled ICF configured exceptions - explicitly allowing ICMP, and
still nothing.
reset the TCP/ip stack and winsock using netsh, nothing
servers has two nics, one of which is disabled. changed binding order so
active is on top -- nothing
reinstalled the binaries of windows 2003 sp1 and upgraded to r2 again --
nothing.

i'm at a lost of ideas and sure could use the vast resources the contributors
of this group may have or know of.

**To make matters even more confusing, workstations located outside of this
main office site that are connected via ipsec vpn can ping this server!!!

HELP

Thanks,

--
---
I do what i got to do in order to do what i want to do...

Message posted via http://www.winserverkb.com

.

Relevant Pages

  • Re: SBS 2003 IIS BASED SERVICES FAIL INTERMITTENTLY
    ... If I read your post correctly, you have a switch where the SBS ... Run DHCP server on your SBS, and set all client machine nics to dynamic. ... Once you have your nics configured, run the Connect to the Internet wizard, ... QUESTION1 - what is REFUSING CONNECTIONS? ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS Exchange 2003: too many "Current Sessions" opened
    ... So far everything is good and now I'm just monitoring my exchange. ... get the SMTP service to stop hanging in the first place. ... won't have dead connections. ... work for now until I put into production new server hardware with sbs 2003 ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS Exchange 2003: too many "Current Sessions" opened
    ... You really should go through the steps I posted and get the SMTP service to stop hanging in the first place. ... You'll be happier, you won't be clubbing your server every day with a kill script, and you won't have dead connections. ... You do *not* need to restart the server, ...
    (microsoft.public.windows.server.sbs)
  • Cant Ping R2 server in same subnet, but can ping outside subnet.!!
    ... The upgraded R2 DC does not accept incoming connections, ... e.g. telnet server ip 389 from the mail server works. ... outbound traffic and icmp works fine, inbound icmp returns a time out. ... downgraded NIC drivers to match other r2 DC on identical server ...
    (microsoft.public.security)
  • Access 2007->SQL Server2005 "connection was forcibly closed",GNE 1
    ... I have a very big problem connecting an SQL ... changing number of clients using the SQL Server with this frontend at the ... connection pooling or if these connections are separated connections). ...
    (microsoft.public.sqlserver.connect)