Failure to properly join domain?

  • Thread starter Thread starter Support Staff
  • Start date Start date
S

Support Staff

Just installed Win2000 on a workstation, as done many times. Seems to go in
OK, renamed and joined domain OK(it registers with DNS), but when rebooted
and try to log on it grinds to a halt, starts (but fails) to run logon
script and then loses network altogether (Can't ping in or out). Tried
reinstalling clean Win2000 and different network card.

Any ideas most welcome.

Thanks
 
What exactly is the login script doing? Why not remove that machine from
the script/GPO and see what happens?
 
Login scripts do nothing but map drives. Doesn't seem to make any
difference simplifying that.... However... the pattern seems to be: set
machine to dynamic IP address and its OK, but set it to a fixed IP (and
we've tried a few!) and it falls over. The network card simply disconnects
(at some arbitary point?) while machine is logging in....
 
More: There seems to be a consistent pattern regardless of way DHCP is
configured and regardless of which of 3 network cards we use: join the
domain OK, reboot and log in and the network connection fails within
seconds.

This machine used to exist on our network under a different name with Win98.
The previous name no longer exists (in DHCP for example) but anyway we've
completely reformatted the machine and have used the different cards!

Really puzzled...
 
Any event log errors? Also, can you explain your network a little more? Do
you have a domain? Please describe the infrastructure, switches, servers to
which this computer is "logging in."
Where is DNS and DHCP coming from? List results of ipconfig /all
 
The situation is this. We have a single domain with 4 W2K servers. We are
attempting to put this machine on in the server room, which means it is
connected to the same switch as the servers. We have done this many times
without problem.

The workstation used to be Windows 98 and was on the domain for a few years.
I re-installed W98 yesterday and it went onto the domain with no problem
with it's fixed IP address (which we need to do for this machine for a
specific admin purpose).

Following this I re-installed W2K and (after deleting all reference to it in
Active Directory, DHCP, DNS, WINs) then rejoined the Domain. First log in
it went fine, no problem. Soon as you log out then log in again, bump, it
loses it's network connection. I'm sure this is at the network card level
(so presumably addressing).
DHCP and DNS come from our primary server, but DHCP should not be involved
as this has a fixed IP address. All network settings are correct (first
log-in was ok, as described above). Subsequent logins....pfft.
I disjoined the workstation from the domain, and logged on as local
administrator (same fixed IP address for the card), and I can access our
proxy internet server no problem, doing all updates as necessary to Windows.
So the networkcard is working fine. But when I rejoin the domain (and I get
all the right messages...i.e. 'Welcome to Domain') I do the required reboot,
then during logon, the network card is literally disconnected. I've seen
this happen as I was pinging the work station from another location during
the login. Everything went fine initially then suddenly it workstation is
disconnected from the network!

Between the W2K / W98 installations the hard drive is formatted, there can
be no leftovers.
 
Ok, but you didn't answer the question, any event log errors??

Also, tried renaming the box? Tried latest nic driver? (although this is
less likely to be the problem since it works off the domain, but it wouldn't
hurt to make sure it is current) Tried adjusting speed/duplex settings on
nic and switch port to something other than Auto? (ie: 10/half or 100/Full;
suggest start with lower setting) Tried different cable and/or port on
switch? Tried nics in different slots?

Also, you didn't clearly answer the question about the login script. Did
you try NOT applying the script to this machine regardless of how
meaningless it may seem to do so? When off the domain, can you still ping a
domain controller by name?

My guess is that it is not hardware related. Keep us posted.
 
OK many thanks for your help. I have partially resolved this problem.
I noticed the network card SEND packet count, displayed in the system tray
icon, was being reset to zero when the network connection failed.
It appears to be the network card being cut off during or shortly after the
log in. Although Device Manager showed no conflicts, the network card had
the same interrupt as the onboard soundcard (motherboard is a Winnex 3). I
disabled the sound card (in BIOS) and now there is never a problem logging
onto the network. The remaining problem is that after some degree of the
network download traffic the network card is disconnected in the same way,
but this always happens after some considerable abount of traffic. I am
presently endeavouring to resolve this problem.
Nonetheless you help was much appreciated, and I again express my thanks.

Support staff.
 
Just to let anyone who is interested know what appears to have been causing
the disconnection after some time on this machine. A few months back we
had DNS problems, in that machines were not being registered in the DNS. We
found the problem was due to a Service Pack 4 glitch, the fix of which was
to install two entries in the registry. (826743).
Anyway these entries had been put in, but there was a mistake on the first
entry (DNScache/Parameters). This would appear to have caused a
disconnection from the network, in fact, literally turned off the network
card, after a period of time (and I'm not sure why).
Looks cured now.
 
Back
Top