Removing Netware client from Server 2003

I've been running a Server 2003 box for lil more than a year now and ages
back completed a migration of users/data from our steam powered Netware 3.12
box (don't laugh, too much!!). Upon trying to remove the netware client
from our windows box as it is now totally superfluous to needs, when 2003
reboots, it completely forgets what domain it's the DC of, and many other
crucial settings appear to go adrift with it. Putting the client back on
corrects this situation.

The sole reason behind wanting to remove the client is to significantly
improve server reboot times. With the NW client installed, the 2003 box
can't take roughly TEN minutes sitting there while it closes down network
connections (I'm assuming the nw client is waiting on non existant to time
out), which in my view is rediculous. Without the client installed, the
2003 box closes down in less than a minute (or there abouts).

Any ideas how I can rid my 2003 box of the netware client safely?
(rebuilding the 2003 box from scratch isn't an option!)

Cheers

Jason Aspinall

"J Aspinall" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Any ideas how I can rid my 2003 box of the netware client safely?
> (rebuilding the 2003 box from scratch isn't an option!)

Just to follow up on my previous post... Last night I attempted to disable
the Netware client by removing the ticks in NW entries of my Local Area
Connection properties, to no avail. Reboot time was equally as long (easily
10 mins) and upon logging back in, my event viewer was full of error
suggesting the NW client was disabled (bit of a no brainer really).

I then tried uninstalling the nwclient completely, reboot took forever
(well, it seemed that way at nearly 20 mins) and when I eventually got to my
server desktop, event viewer was showing a dead exchange server, dead DNS
too, not a pretty sight. No workstations could log in, those that hadn't
logged out lost access to network shares...basically it was fubar.

Reinstalling the nwclient brought back normality to the server, yet I still
have ferociously long reboot times. Closing the server down it simply sits
there for ages and ages...

Anyone have some ideas what I can look at next?

--
Jason Aspinall

"J Aspinall" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> "J Aspinall" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Any ideas how I can rid my 2003 box of the netware client safely?
>> (rebuilding the 2003 box from scratch isn't an option!)
>
> Just to follow up on my previous post... Last night I attempted to disable
> the Netware client by removing the ticks in NW entries of my Local Area
> Connection properties, to no avail. Reboot time was equally as long
> (easily 10 mins) and upon logging back in, my event viewer was full of
> error suggesting the NW client was disabled (bit of a no brainer really).
>
> I then tried uninstalling the nwclient completely, reboot took forever
> (well, it seemed that way at nearly 20 mins) and when I eventually got to
> my server desktop, event viewer was showing a dead exchange server, dead
> DNS too, not a pretty sight. No workstations could log in, those that
> hadn't logged out lost access to network shares...basically it was fubar.
>
> Reinstalling the nwclient brought back normality to the server, yet I
> still have ferociously long reboot times. Closing the server down it
> simply sits there for ages and ages...
>
> Anyone have some ideas what I can look at next?

Bump, anyone?

Do you have another Windows 2003 server that you can make the DC? I guess
where I'm going is I'd find a way to move services off this server and
re-build it. If that's not possible, tyr to un-install the Novell client and
use the reg clean tool to clean up the server registry. It's available from
microsoft.com/download

"J Aspinall" wrote:

> "J Aspinall" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > "J Aspinall" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> >> Any ideas how I can rid my 2003 box of the netware client safely?
> >> (rebuilding the 2003 box from scratch isn't an option!)
> >
> > Just to follow up on my previous post... Last night I attempted to disable
> > the Netware client by removing the ticks in NW entries of my Local Area
> > Connection properties, to no avail. Reboot time was equally as long
> > (easily 10 mins) and upon logging back in, my event viewer was full of
> > error suggesting the NW client was disabled (bit of a no brainer really).
> >
> > I then tried uninstalling the nwclient completely, reboot took forever
> > (well, it seemed that way at nearly 20 mins) and when I eventually got to
> > my server desktop, event viewer was showing a dead exchange server, dead
> > DNS too, not a pretty sight. No workstations could log in, those that
> > hadn't logged out lost access to network shares...basically it was fubar.
> >
> > Reinstalling the nwclient brought back normality to the server, yet I
> > still have ferociously long reboot times. Closing the server down it
> > simply sits there for ages and ages...
> >
> > Anyone have some ideas what I can look at next?
>
> Bump, anyone?
>
>
>

I came very very close to having to rebuild this particular server of ours
this morning, which would've eradicated Netware forever off our network. A
rogue expired certificate in some APC PowerChute software, in conjunction
with yesterdays update patches effectively killed off my box (2 hour reboot,
no dhcp, no dns, no lan access) - "quick" reboot in safe mode, disable APC
services, reboot normal and the server's back up and running.

I'm going to call MS back relating to my above issue to let them know their
suggestions did indeed cure my probs, and hint at the idea that perhaps I
could do with getting shot of the NW client to see if they can point me in
the direction of a KB entry or two...

Failing that, we will be introducing a backup DC to this particular server
in the not too distant future to do exactly what you say...push the services
over through replication, then eventually decommission the affected box for
a rebuild afresh

Thanks for the reply...

"Mocahbee" <(E-Mail Removed)> wrote in message
news:971516F1-8CF9-4F7D-BB2E-(E-Mail Removed)...
> Do you have another Windows 2003 server that you can make the DC? I guess
> where I'm going is I'd find a way to move services off this server and
> re-build it. If that's not possible, tyr to un-install the Novell client
> and
> use the reg clean tool to clean up the server registry. It's available
> from
> microsoft.com/download
>
> "J Aspinall" wrote:
>
>> "J Aspinall" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>> > "J Aspinall" <(E-Mail Removed)> wrote in message
>> > news:(E-Mail Removed)...
>> >> Any ideas how I can rid my 2003 box of the netware client safely?
>> >> (rebuilding the 2003 box from scratch isn't an option!)
>> >
>> > Just to follow up on my previous post... Last night I attempted to
>> > disable
>> > the Netware client by removing the ticks in NW entries of my Local Area
>> > Connection properties, to no avail. Reboot time was equally as long
>> > (easily 10 mins) and upon logging back in, my event viewer was full of
>> > error suggesting the NW client was disabled (bit of a no brainer
>> > really).
>> >
>> > I then tried uninstalling the nwclient completely, reboot took forever
>> > (well, it seemed that way at nearly 20 mins) and when I eventually got
>> > to
>> > my server desktop, event viewer was showing a dead exchange server,
>> > dead
>> > DNS too, not a pretty sight. No workstations could log in, those that
>> > hadn't logged out lost access to network shares...basically it was
>> > fubar.
>> >
>> > Reinstalling the nwclient brought back normality to the server, yet I
>> > still have ferociously long reboot times. Closing the server down it
>> > simply sits there for ages and ages...
>> >
>> > Anyone have some ideas what I can look at next?
>>
>> Bump, anyone?
>>
>>
>>