UNSOLVED

hito

updated

20 years ago

H

hito

14 Posts

0

15303

May 17th, 2006 12:00

XP sign on problem

It's brand new Dell computer and a windows XP based. I joined to domain this computer and try to log on to domain. I get following error message:
 
" Windows cannot connect to the domain either becuase the domain controller is down or otherwise inavailable or because your computer account was not found "
 
Majority of users doesn't have problem to sign on but this user gets those error.
The user can log on ans use computer a comple days and sometime happens..
Does anyone know why????
 
Please help.
  • BBraxton

    2 Intern

    •

    2037 Posts

    243

    0

    Posted May 17th, 2006 13:00

    I have seen something like this that has to do with location on our LAN. A system that cannot log in at all in one building might be fine when I move it to another location (usually in a different building).
    There might be a bad port in a switch.
    Is it possible to swap this line at the switch with another that is working fine to see whether the problem goes with the port or something else?
  • jmwills

    2 Intern

    •

    11984 Posts

    243

    0

    Posted May 18th, 2006 08:00

    Once the machine has been joinded to the Domain, that's it. You are probably seeing one of two things: either a bad cable or a bad ethernet port.

    Is it happening on just this machine?  is this a machine that replaced an existing machine with the SAME name in the Domain?

    Message Edited by jmwills on 05-18-200611:04 AM

  • hito

    14 Posts

    243

    0

    Posted May 19th, 2006 12:00

    I made a different computer name on those two computers.
  • hito

    14 Posts

    243

    0

    Posted May 19th, 2006 12:00

    Thank you for your reply. Actually, when this user had a problem, I tried to connect with other station's port or change network cable. However, the problem was same at the time.

    What I did to resolve this problem was... I remove this computer from domain and change to workgroup, after that I re-joined this computer to domain again then I was able to sign on to computer. However, this same problem happened after a couple days or week for same users again. Basically, whenever happened same problem, I just take same procedure to resolve this problem. I'm not sure why happens again.

    I had one more user which had a same problem and resolve it by same actions and this user seems ok for since then.

    What I don't understand is, previously user was using win98 machine and had never this problem. Now I rolled out XP machine to users and so far two users had same problem.

    Do you think this is a port problem?

     

    Thanks,

  • BBraxton

    2 Intern

    •

    2037 Posts

    243

    0

    Posted May 19th, 2006 12:00

    Where is the Windows 98 computer that you removed?
    When we put in a new computer, we have to use a new name.
    So, if the original computer had the name FLastname then we would give the new computer the name FLastname1 (as an example). As long as the old computer was not turned on there would be no problem. However, once the old computer was turned on, a new computer with the exact name of the original would fail (balk).
  • jmwills

    2 Intern

    •

    11984 Posts

    243

    0

    Posted May 19th, 2006 13:00

    Just renaming the machines is not enough.  The SID's have to be changed.
  • hito

    14 Posts

    243

    0

    Posted May 23rd, 2006 18:00

    Hi Jmwills,

    What exactly SID mean? Those XP computers are brand new DELL computers. When we purchased those from DELL, OS is already installed.  I haven’t done any ghost to make image from other computer so why I have to change SID? Do I still have to change SID for a new computer? Previous win98 computers are no longer utilizing in office. I have tried to connect with a different port and network cable. However, I wasn’t success so what else could be a problem. We have more than 30 computers and so far only have experienced for two users.  Please help.

  • BBraxton

    2 Intern

    •

    2037 Posts

    51

    0

    Posted May 23rd, 2006 18:00

    We had recently ONE GX-260 where the Ethernet failed due to a bad motherboard which Dell replaced. In our case it had been working perhaps for a year before it failed. Until we called it in to Dell, we used a USB to get around it. Then, when they replaced the motherboard, we took the USB network adapter out of the equation and have been fine since. That was as recent as two or three weeks ago.
  • hito

    14 Posts

    243

    0

    Posted May 23rd, 2006 18:00

    Hi there,

    We have replaced from old one to xp computer that win98 computer is no longer onto netowork.

    Therefore, I don't think computer name conflict.  I have tried using different port and network cable as well. Obviously, it didn’t help. This user can log on locally, without joined domain but not log on as domain. What I don’t understand is if I put this computer back to workgroup and then joined domain again, it works. (user can log on using domain) but after couple days happens same problem.. Do you have any other idea?

  • BBraxton

    2 Intern

    •

    2037 Posts

    243

    0

    Posted May 23rd, 2006 18:00

    I still think that the location on the LAN could be a factor.
    We had a building where a system like this went bad in the same fashion but when I carried it to a totally separate building (connected to a totally different switch) the same system worked fine.