Removing Netware client from Server 2003

[Guest zippy172]

Below are two posts I've already made to microsoft.public.windows.server.networking with no reponses (yet)... Anyone here clueful enough to help me?

Post 1.

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!)

and...

Post 2.

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?