Still on the Domain or no?

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

Guest

Hi everyone

My company's network platform is running on Windows 2000 Server ADS. All of the computers are able to join the domain just fine. However, on one of the XP computers, the case is not true. After being able to join the domain for about 2-3 days, it appears that the computer might have excused from the domain. The user/password authenticate has to be on the Server in normal conditions; however, the user is still able to log in without the network cable plugged in!!! and the log-in screen shows the he/she has logged onto the network not the local machine. I have pinged the server by name and ip and even see on the ADS tool on XP Pro. The Computer Name also shows that the XP machine is on the network with the FQDN. Could any applications or additional hardware cause this problem? Or is it an entirely new network problem

Any response is greatly valued. I would like a response ASAP as having this type of login can compromise our network security. Thank you.
 
You user is logging on with cached credentials. Is your client DNS pointing
to the server hosting your AD namespace?


Tom said:
Hi everyone,

My company's network platform is running on Windows 2000 Server ADS. All
Click to expand...
of the computers are able to join the domain just fine. However, on one of
the XP computers, the case is not true. After being able to join the domain
for about 2-3 days, it appears that the computer might have excused from the
domain. The user/password authenticate has to be on the Server in normal
conditions; however, the user is still able to log in without the network
cable plugged in!!! and the log-in screen shows the he/she has logged onto
the network not the local machine. I have pinged the server by name and ip
and even see on the ADS tool on XP Pro. The Computer Name also shows that
the XP machine is on the network with the FQDN. Could any applications or
additional hardware cause this problem? Or is it an entirely new network
problem?
Any response is greatly valued. I would like a response ASAP as having
Click to expand...
this type of login can compromise our network security. Thank you.
 
The user is still able to log on without connections to the ADS. The user/password authentication is function without any connections to the network yet it still is connected to the domain. This is really causing a whole in our network security and is causing that workstation to be temporary "quarantined" for now. Please help with this problem ASAP. Thank you

-To

----- Tom wrote: ----

Yes. This is the current LAN configuration for the XP Pro machine
IP add-192.168.0.1
Sub-255.255.255.0
Default Gateway-non
DNS Servers- 192.168.0.100 (DC handling AD
Primary WINS Server- 192.168.0.10

----- Rob Elder, MVP-Networking wrote: ----

You user is logging on with cached credentials. Is your client DNS pointin
to the server hosting your AD namespace


Tom said:
Hi everyone
Click to expand...
of the computers are able to join the domain just fine. However, on one o
the XP computers, the case is not true. After being able to join the domai
for about 2-3 days, it appears that the computer might have excused from th
domain. The user/password authenticate has to be on the Server in norma
conditions; however, the user is still able to log in without the networ
cable plugged in!!! and the log-in screen shows the he/she has logged ont
the network not the local machine. I have pinged the server by name and i
and even see on the ADS tool on XP Pro. The Computer Name also shows tha
the XP machine is on the network with the FQDN. Could any applications o
additional hardware cause this problem? Or is it an entirely new networ
problemthis type of login can compromise our network security. Thank you
 
Back
Top