Q:
System cannot log you on now because the domain **** is not accessible.
Windows Server 2003 Enterprise Edition, Windows Server Installation, Windows Server 2003, Windows XP, Windows Server Error Messages Hi all,
This could be my worst nightmare ever. I just installed a Windows Server 2003 Enterprise Edition on a clients network. Configured the Active Directory, DNS, DHCP e.t.c
Everything looks pretty much fine.
Went over to the Client conputer running windows XP to add it onto the new domain created. I was able to. Added it to the domain successfuly, restarted the computer.
Only for me to log on to the domain with an account i have created on the Active Directory i got this error message.
[strong]System cannot log you on now because the domain **** is not accessible.[/strong]
I have tried all i could, but luck in logging on.
Please please and please. . . .I need help fast.
Any idea will be appreciated[strong].
[/strong]
[strong]Syphun.[/strong]
This could be my worst nightmare ever. I just installed a Windows Server 2003 Enterprise Edition on a clients network. Configured the Active Directory, DNS, DHCP e.t.c
Everything looks pretty much fine.
Went over to the Client conputer running windows XP to add it onto the new domain created. I was able to. Added it to the domain successfuly, restarted the computer.
Only for me to log on to the domain with an account i have created on the Active Directory i got this error message.
[strong]System cannot log you on now because the domain **** is not accessible.[/strong]
I have tried all i could, but luck in logging on.
Please please and please. . . .I need help fast.
Any idea will be appreciated[strong].
[/strong]
[strong]Syphun.[/strong]
ASKED:
Nov 7 2009 8:54 AM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
A:
RATE THIS ANSWER
0
Click to Vote:
0
Click to Vote:
- 0
0
Naaah bro.
Got it sorted out.
I noticed the Router was enabled to distribute addresses on DHCP. and when i restarted the client computer after adding it on to the domain, it picked address from the router which was on another subnet from what i have on the network.
That way, the client computer couldn't get it's DNS resolved by the server, thus prompted the error message.
Thanks for the trouble anyway.
merci . . .
