aaridas Posted July 15, 2010 Posted July 15, 2010 The computer is currently connected to the network physicaly (cable) and when it asks to enter the username and password it rejects saying the domain is not available , which in reality the domain is working fine. if i log in on a computer next to it then it logs fine. it is just that computer.... any suggestions???
p858snake Posted July 15, 2010 Posted July 15, 2010 Remove it from the domain, delete the computer from AD and rejoin it? Ensure the cable is working and getting a correct network detection (aka it can see the cable, try logging in locally and pinging the server)?
aaridas Posted July 15, 2010 Author Posted July 15, 2010 tried it already. still doesnt work. rejoined back and restarted the system many times.
p858snake Posted July 15, 2010 Posted July 15, 2010 Did you actually delete it from Active directory on the server? (did you let it replicate around if you replicate your AD catalog?)
aaridas Posted July 15, 2010 Author Posted July 15, 2010 I havent tried to replicate it. how does it work?
zippo Posted July 15, 2010 Posted July 15, 2010 First things first - logon locally and check the IP address. Is it getting its address from the server or is it the 169.x.x.x address that Windows substitues whe it can't find a DHCP server. Check that the station has not had a manual DNS server configured (do this even if its getting its IP from the DHCP server). Finally can you actually get onto the internet or ping your servers by name.
sted Posted July 15, 2010 Posted July 15, 2010 if you login localy can you ping the server by name and ip? might sound odd but its not a fujitsu e2500 is it? if so turn off yank power lead out turn on put power lead back in and turn on
SpuffMonkey Posted July 16, 2010 Posted July 16, 2010 On our setup - this is almost always caused by a connectivity issue - network cable damaged or pulled out, damaged wall socket etc etc
Andrew_Sharrad Posted July 16, 2010 Posted July 16, 2010 Hi There, Can I recommend please that you log on as the local Administrator of the PC and check that it has got an IP address from the network? The IP address should not start with 169.xxx.xxx.xxx. Regards, Andrew
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now