You COULD get around that by using a NIC that is already listed in the W2K driver set. There are just a couple, I'm pretty sure... <G> Install it AND your fly-by-night NIC to pull the needed driver off your network.
Just keeping one or two on hand is a good idea. At 12:19 PM 5/7/2002, Ryan Malayter wrote: >Suppose you have to replace a blown NIC with one that uses a different >driver. How are you going to get administrative rights on the >workstation? You can't log into the domain as an administrator, because >you have no network connectivity, but the local admin password is >disabled... So you'd have to reinstall. > >-----Original Message----- >From: Bruce Fyfe [mailto:[EMAIL PROTECTED]] >Posted At: Monday, May 06, 2002 6:21 PM >Posted To: Windows NT/2000 List >Conversation: Security - Local Admin Account >Subject: RE: Security - Local Admin Account > > >Another suggestion would to be to disable the local admin account. Then >you wouldn't need to worry about changing the password. > >Bruce Fyfe, Network Engineer >Lakeside Industries (www. lakesideind.com) >(425) 313-2600 > > >-----Original Message----- >From: Paul Done [mailto:[EMAIL PROTECTED]] >Sent: Thursday, May 02, 2002 9:45 AM >To: NT 2000 Discussions >Subject: Security - Local Admin Account > >For W2k pro machines authenticating into a 2k domain is there a way for >the >machine (local) Administrator account password to periodically be >changed on >all machines by some sort of login script or tool? I have found a way to >crack this password, now I would like to change this at least every >couple >of days on all my machines. > >Is this a good idea? What are your thoughts? Todd C. Haugland mailto:[EMAIL PROTECTED] The world is divided by people who think they are right. ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
