T
Thomas N
Hello all,
Yesterday, I joined an XP Pro machine onto our company's
existing Windows 2000 AD network. The operation was
successful and all DNS/WINS/DHCP configurations tested
out successfully. Today morning, the user could not log
on because the XP Pro machine could not find the domain.
All hardware have been checked. When I try to log in with
my account, I is able too, even with the network cable
unplugged! I reconnected the cable and went to the 2000
AD DC, I was unable to ping the XP machine by name or by
ip address. All other machines can be pinged by the AD DC
as well. On the contrary, the XP machine is able to ping
all other machines on the network (with cat 5 plugged in
of course). All DNS and TCP/IP configurations have been
checked (DNS points to DC and WINS as well). Seems as if
the XP machine cannot contact the DC (or get replies
from) and is unable to authenticate usernames nor access
network resources.
Any hints or tips to point me in the right direction will
be greatly appreciated.
-Thomas
Yesterday, I joined an XP Pro machine onto our company's
existing Windows 2000 AD network. The operation was
successful and all DNS/WINS/DHCP configurations tested
out successfully. Today morning, the user could not log
on because the XP Pro machine could not find the domain.
All hardware have been checked. When I try to log in with
my account, I is able too, even with the network cable
unplugged! I reconnected the cable and went to the 2000
AD DC, I was unable to ping the XP machine by name or by
ip address. All other machines can be pinged by the AD DC
as well. On the contrary, the XP machine is able to ping
all other machines on the network (with cat 5 plugged in
of course). All DNS and TCP/IP configurations have been
checked (DNS points to DC and WINS as well). Seems as if
the XP machine cannot contact the DC (or get replies
from) and is unable to authenticate usernames nor access
network resources.
Any hints or tips to point me in the right direction will
be greatly appreciated.
-Thomas