Remove and Reinstall TCP/IP on a Windows 2000 DC

  • Thread starter Thread starter Blaze
  • Start date Start date
B

Blaze

http://support.microsoft.com/default.aspx?scid=kb;EN-US;299451

I believe I have a corrupt TCP stack.... or so the Tech from Microsoft
believes

I am getting BSOD's after installing SP4 and I cant restore or roll back.

Has anybody done this and is there much risk involved ?
I says remove the DNS, DHCP and WIN's servers,

1/ when I reinstall the services will I have to redo the DHCP scope and DNS
or will it be stored and automatically re configure.

2/ The previous Network guy did not keep documentation, so I don't really
know the IP's of the printers around the site, will these IP's still be
saved

3/ also it says the shares will be lost... now I have over a thousand users
with shared home directories... would I have to re share ALL of these ?

4/ This little sentence scares the willies out of me "and then add back DNS
and any other components that had been previously configured"
How difficult on a scale of 1 to 10 would this be?

4/ Is there some easier way?

thanks
 
RussS said:
Hmmm - and you are in charge of this network?
Click to expand...

Mmm sarcasm the lowest form of wit....... You know RussS.. we all have to
start somewhere... At least I identified the cause of the problem and just
want to bounce this off of some people on the newsgroups before I do this
for the FIRST time....

Yes I am in charge its not a big network it has 5 servers and a couple
hundred PC', as I said the previous Network manager was a bit lax in the
documentation area

OK smarty-pants
 
First off - if I was gonna be sarcastic I sure as hell would have been a
whole bunch more sarcastic than that. What I wanted to know was if you were
in charge of maybe a junior who wanted to provide the 'silver bullet' answer
for his boss.

"I believe I have a corrupt TCP stack.... or so the Tech from Microsoft
believes"
This is based on the info below or did you supply further info to him?

"I am getting BSOD's after installing SP4 and I cant restore or roll back."
Why can you not roll back?
Error messages?

"Has anybody done this and is there much risk involved ?
I says remove the DNS, DHCP and WIN's servers,"
Not entirely certain of what you mean there?

"1/ when I reinstall the services will I have to redo the DHCP scope and
DNS
or will it be stored and automatically re configure."
Chances are that you will have to restore the DHCP & DNS - providing of
course it is hosted on that server. If not then it wont be a problem.

"2/ The previous Network guy did not keep documentation, so I don't really
know the IP's of the printers around the site, will these IP's still be
saved"
That depends on where they are hosted etc? Are they on printservers or do
they have direct TCP/IP capability?

"3/ also it says the shares will be lost... now I have over a thousand users
with shared home directories... would I have to re share ALL of these ?"
Not necessarily. If those shares are on the server you are going to be
working on then if that server has the same name and IP address then it
shouldnt be a biggie.

"4/ This little sentence scares the willies out of me "and then add back DNS
and any other components that had been previously configured"
How difficult on a scale of 1 to 10 would this be?"
Sounds like fairly high on the scale for your experience, however it is most
certainly doable.

"4/ Is there some easier way?"
Yes - find out why you can not roll back your service pack.

Ok - firstly I suggest you document EVERYTHING asap. If you are getting
blus screens then your users will be having issues and will get pissed
rapidly.
Try http://www.aida32.hu/aida-features.php for auditing your users machines.


Next - add this site to your favourites http://www.experts-exchange.com

Thirdly - did I say document all changes? Well do that at each and every
change.

Last - a little hint ... Never, and boy do I mean NEVER ... install a
service pack on a live machine unless you have either
1 - Tried it on a lab machine (not always possible on an equivalent server,
but a box with the same OS patched to the same level and running the same
services and apps can be a great help).
2 - Have done a full backup first.
3 - Have an option to replace or roll back that server if it all turns to
custard.
4 - Have seriously read up on any possible issues.


BTW - I would love to hear how you get on.

Russ
 
No problemo

Another Q for ya?
The Micrososoft tech wasn't just talking about your LOCAL TCP/IP by any
chance was he?
 
RussS said:
No problemo

Another Q for ya?
The Micrososoft tech wasn't just talking about your LOCAL TCP/IP by any
chance was he?
Click to expand...
http://support.microsoft.com/default.aspx?scid=kb;EN-US;299451

http://www.experts-exchange.com/Operating_Systems/Win2000/Q_20878948.html

The Server that this needs to done on is a DC with AD, DHCP. DNS, and is
also the main file server with 1000 home directories, I have a second DC
which hosts the ISA and Exchange servers..and of course the AD replication

the reason that I cannot switch servers is that there is security software
called Ranger on the main DC and users cannot log on unless the main DC is
working and Ranger authenticates them.

the reason that I cannot roll back is that the Tech that put SP4 on did not
archive, I had put SP4 onto 50% of PC's on site before doing the servers

As you see from the Experts-Exchange question only the DC server is BSOD'ing

As for a backup restore....the SP4 was installed 6 months back and BSOD'ed a
few times before I thought was stable again, but 2 weeks ago it collapsed,
and we have no backup for this server further back than a month, also
nothing else has been installed on the server for 6 months....
there are no viruses..
 
hmmmm - I would think that SP4 was past causing issues by now.

Another Q for ya .... when the server comes up with the BSOD is there major
disruption for the network users or is it localised?
 
RussS said:
hmmmm - I would think that SP4 was past causing issues by now.

Another Q for ya .... when the server comes up with the BSOD is there major
disruption for the network users or is it localised?
Click to expand...
No user that has ranger security installed can log on... 90% of users LOL
 
Sounds like a very localised problem and possibly if it is in the TCP/IP
stack, then just in the local one for that server.
Have you tried just removing the TCP/IP stack for that machine and
reinstalling it?
 
RussS said:
Sounds like a very localised problem and possibly if it is in the TCP/IP
stack, then just in the local one for that server.
Have you tried just removing the TCP/IP stack for that machine and
reinstalling it?
Click to expand...

No Not yet... good idea.. I'll try that on Monday...
 
Havent tried winsockfix.exe - I might run it on a test machine and have a
look at it.

I would suggest just blowing away the TCP from each NIC as a first up
experiment - sure as heck can't hurt.
 
Blaze - hold on a second... before you remove TCP/IP from
the NICs and potentially hose your system beyond repair...

Can you build another DC, load Ranger, and migrate the
users' home folders? It is easy to migrate your DHCP
database to another server, and AD integrated DNS is cake
to add a new nameserver...

My suggestion would be to build a new DC from scratch.
Install Ranger. Let it sit on the network a few days and
make sure it is stable. Then migrate DHCP. Then migrate
user shares and printers. Once you have migrated all the
services and data over to the new box, gracefully remove
the old one from AD (using DCPromo), then remove it from
the domain, then blow it away.

Rebuild it or re-allocate it if you feel compelled...

If you honker up the box trying to monkey with the TCP/IP
stack, you could find yourself in for a few days worth of
long long hours in the datacenter restoring from tape,
doing authoritative restore of AD, recreating printer and
data shares, etc. Your users will be faced with lots of
downtime and lost productivity - not good...

The situation may not turn out so bad - I have followed
the steps in the KB article you have sited and been
successful - but if this is your first run down that road
I would caution you to do so only as a last resort, and
only with competant assistance at your disposal.

Good luck!
Dale
 
RussS said:
Havent tried winsockfix.exe - I might run it on a test machine and have a
look at it.

I would suggest just blowing away the TCP from each NIC as a first up
experiment - sure as heck can't hurt.
Click to expand...

Yep will do... somehow the Proliant keeps the card settings invisible after
removing the cards ??
 
Remove the TCP/IP settings BEFORE you uninstall the NIC ... no NIC = no
settings, as the settings need to bind to a NIC.
 
Back
Top