Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1481
  • Last Modified:

disjoin a windows 2003 client from domain by command line?

how i can disjoin a windows 2003 client from domain by command line?
0
ajalboush
Asked:
ajalboush
2 Solutions
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
0
 
ajalboushAuthor Commented:
"The identification of the computer cannot be changed because:  Networking is not properly installed or not properly configured"

when i right click on my computer and i want to change the domain i recieve the previous error on the properties page ?
0
 
ajalboushAuthor Commented:
and the netlogin service is not installed on the machine ?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
ajalboushAuthor Commented:
am logged in as the local Administrator and I cannot
>get the system to join our domain. In the system
>Properties page under the Computer Name tab, both the
>Network ID and Change buttons are greyed out. There is
a
>message at the bottom that reads "Note: the
>identification of the computer cannot be changed
>because: -networking is not installed or is not properly
>configured." Any ideas???
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
Well, it sounds like your problem could be that Networking is not properly installed or not properly configured.

If you can provide a context - why your trying to do this via the command line, a description of the system, it's IP configuration, etc - I might be able to provide a better comment.
0
 
trenesCommented:
Hi ajalboush,

Try login as a domain admin to move the client from the domain.

Cheers!
regards,

Trenes
0
 
ajalboushAuthor Commented:
i tird, nothing new.
0
 
Netman66Commented:
Reset the stack on that computer:

http://support.microsoft.com/kb/299357


Also, fix Winsock if it's broken:

http://support.microsoft.com/kb/811259


After this, you should be functional again.

0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now