Windows Forum

Ask something
Discussion Locked

Windows 2K Server Configuration

0 helpful
9 replies

by paladin46

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Recently we set up a Windows 2000 server for our Dallas office. It is a member server on an NT domain, which was originally installed at our home office with a static IP address for our subnet. We then shipped the box to Dallas where I was to set it up. I logged on as the local administrator and changed the IP settings to reflect the network it was now residing on. Once the IP settings were changed I was unable to login to our domain. The message I received said that I was unable to login because the Net Logon service was not running, however when I login locally and check the services, it is running. I was able to stop and start the service with no problmes. I removed the server from the domain but when I tried to re-add it to the domain instead of being prompted for a username and password with the authority to do so, I got a message that the domain was not found. After trying this a few times I was able to join the domain and then able to login, but I want to avoid this happening again. Any ideas?

9 replies

by oholland

Your server is not seeing your Domain controller. If the controller is local, check your Subnet. If not...try to ping the domain. Most likely the server you may need to ad a route to the network that the Domain controller is on

by paladin46

oholland,

The domain controller is not local, but other PCs in the Dallas office were able to login and gain access to domain resources. If they could get through to the domain, shouldn't the server have been able to as well?

by deltree

To prevent this from happening again, I would configure the new IP info before sending the box to its new location.

by paladin46

We can't join the domain with it's intended IP address because it's on a different subnet. Are you saying once we join we should change the IP address while it still connected? I didn't try that but I will. Does this have something to do with tehway the SID is created? Does the IP information affect the SID?

by deltree

I misunderstood. I thought this was an existing box that was already a member of the domain.
Yes, make the box a member of the domain on your home office subnet. Then change the IP info for the Dallas subnet.
To answer your last question. When a domain controller creates a machine account (SID) for a new member, it doesn't care and is unaware of the machines IP configuration. It only cares about the users rights to join the domain.

Also, configuring the server in advance is a potential time saver. Work out the bugs at the home office so you are not at the remote site until 2am frantically working out bugs to have the server online at 8am.

This discussion is closed to new replies.