Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Problems joining Win2K to WinNT4 domain

  • Please log in to reply
1 reply to this topic

#1 killahurtz


  • Members
  • 4 posts
  • Local time:02:58 PM

Posted 12 January 2005 - 06:21 PM

Recently, my network manager required all workstations to migrate to the Active directory network by a given date. All 18 of my workstation had to be upgraded to Win2K pro or XP pro and set to use DHCP. My server/domain controller is running WinNT4 and is still registered on the network until I am able to upgrade. After upgrading all my workstations, only one computer can not find the domain. I get a message that the domain does not exist or cannot be found. This particular workstation is one of my newer computers, Dell OptiPlex computers. The computer was already running Win2K so I simply change from static IP to DHCP. This is when I started having problems like DNS lookup errors. The network card is fine. It is a strange problem I am unable to figure out. All the other workstations are working fine since the change over. HELP PLEASE!!!!

Edited by killahurtz, 12 January 2005 - 06:21 PM.

BC AdBot (Login to Remove)


#2 DynoDon


  • Members
  • 32 posts
  • Local time:02:58 PM

Posted 13 January 2005 - 12:02 AM

Try resetting the XP tcpip stack.



As follows:

Command usage

netsh int ip reset [log_file_name]

To run the command successfully, you must specify a file name for the log where actions that are taken by netsh will be recorded. For example, at a command prompt, type either of the samples that are listed in the "Command samples" section. The TCP/IP stack will then be reset on a system, and the actions that were taken will be recorded in the log file, Resetlog.txt. The first sample creates the log file in the current directory, while the second sample creates a path where the log will reside. In either case, where the specified log file already exists, the new log will be appended to the end of the existing file.

Command samples
netsh int ip reset resetlog.txt
netsh int ip reset c:\resetlog.txt


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users