Joining NT 4.0 domain

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I manage a NT 4.0 WAN. We have been adding new XP pro workstations at a rate
of 1 to 2 per month. The first couple were no problem. Now they will not
log in to the domain.

We have just two segments to the WAN with the PDC on one side and a BDC on
the other. I am setting up the new work stations on the side of the BDC.
Both servers are DHCP and DNS enabled.

If I manually set the IP information I cna ping the BDC both by IP address
and name. I can ping the PDC on the other side of the WAN by IP address but
by not by name. I can not receive and IP address from the BDC's DHCP.

My guesses are that this is either some sort of firewall issue with the new
XP stations or the DNS is not set up properly on the BDC.

I spent 7 hours over the weekend trying everything I could think of to
correct the problem but no luck.

I am sure this is not a big problem, but I am out of ideas. Any ideas would
be appreciated.
 
jim_herr said:
I manage a NT 4.0 WAN. We have been adding new XP pro workstations at a
rate
of 1 to 2 per month. The first couple were no problem. Now they will not
log in to the domain.

We have just two segments to the WAN with the PDC on one side and a BDC on
the other. I am setting up the new work stations on the side of the BDC.
Both servers are DHCP and DNS enabled.

If I manually set the IP information I cna ping the BDC both by IP address
and name. I can ping the PDC on the other side of the WAN by IP address
but
by not by name. I can not receive and IP address from the BDC's DHCP.

My guesses are that this is either some sort of firewall issue with the
new
XP stations or the DNS is not set up properly on the BDC.

I spent 7 hours over the weekend trying everything I could think of to
correct the problem but no luck.

I am sure this is not a big problem, but I am out of ideas. Any ideas
would
be appreciated.
Click to expand...


NT4 domains require NetBIOS name resolution, not DNS.
Ensure all the machines are pointing to the correct WINS servers.
If the PDC and BDC are both WINS servers, ensure they are replicating
properly.
You should then be able to ping the PDC by name.

The inability to get an IP by DHCP is more worrying.
Are these clean installs?
What SP level are they at - SP1/SP2?
Were they installed as that, or was the SP applied as an add-on?

First, check the DHCP client service is running.
start | run | services.msc,
look for DHCP client.
It needs to be running, and Startup Type = Automatic.

If it is, then another possibility is the machine had malware, and was then
upgraded to SP2.
This commonly causes winsock problems that cause these symptoms.

First, if the machine is SP2, try this:
Go to a command prompt window, and type:

netsh winsock reset catalog


Otherwise,these tools often repair the damage:

http://www.cexx.org/lspfix.htm
http://www.downloads.subratam.org/WinsockFix.zip
 
Thank you for your response. A couple of notes:

The DHCP server is handing out IP adderesses to other work stations
(including some XP pro stations) so I assume the service is runnning even
though the new stations will not attach.

The new stations are from Dell and came with SP2 installed already.

Do you still think that running the netsh command should be run?
 
Thank you for
your response. A couple of notes:
The DHCP server is handing out IP adderesses to other work stations
(including some XP pro stations) so I assume the service is runnning even
though the new stations will not attach.

The new stations are from Dell and came with SP2 installed already.

Do you still think that running the netsh command should be run?
Click to expand...



I wasn't talking about the DHCP server.

The service is the DHCP **CLIENT** service,and should be running on the
clients.
That's the guy that picks up the addresses, not issues them.

Make sure it's running.

And then try the other things on the broken clients,
but since they came with SP2 pre-installed, that's probably not it.
 
I have tried both manually entering the IP information and user the DHCP
client. When using the DHCP client on the new machines, the TCP/IP
information on these machines ends up blank. If I enter it manually that is
when I can ping the IP address but only the names on the current side of the
WAA. But I still can not add the domain on the client side. It asks me for
user and password with athorization but returns an error saying the Domain is
not available.
 
Back
Top