The following is a test question I will have put to me at an interview on Friday (I really want this Job!). I have my own ideas on how to explain to answer, but I want some other opinions. The question is: The user try's to log on using the correct user name and password, but keeps on getting the message: "No Domain Server is Available to Log you on" The account is not locked out on the server so what could the problem be? The configeration of the computer is as follows IP: 10.2.1.55 Subnet 255.255.255.0 Domain: ATTRACTIONS Workgroup ATTRACTIONS no gateway needed The computer itself is connected to the network correctly (hardware wise) and there is no software needed to solve the problem, everything you need to complete the task is in front of you. So there it is guys, please let me know how you would approach this problem, in front of a machine on your own for 15 minutes. Thanks for your help

You don't mention if this is a W2k domain or an NT domain or what sort of client computer you are sitting in front of. Since this is a 2000 forum I will assume you are using 2000 computers. In that case I would say the problem is most likely one of DNS. Assuming the domain controller is available then problem seems to be the inability of the client to find it. 2k clients use DNS to locate services and computers. I would like to know the DNS settings of this client computer. It should be pointed to a W2K DNS server that knows how to contact the domain controller. What were your thoughts on the problem?

My idea is that you cannot actually be in both a domain and a workgroup at the same time. I think its a bit of a trick question. It could be the DNS but the paper states "everything you need to complete the task is in front of you". Surely a DNS address would be on the paper if this was the problem? What do you think?

Again, I would check the DNS settings. There really is not enough info to answer this. Is the domain controller on the same subnet? It appears so since they say no gateway is needed. Is the computer configured to join the domain? They don't really say. It must be if it is trying to contact the domain controller but if this is a 2000 client then the Workgroup name is irrelevant because you can not configure both - only one or the other. The IP and mask settings also mean nothing without knowing the IP address of the server. If the mask was wrong then that would cause problems but there is no way to know this without knowing the mask and settings of the DC. There just is not enough info. If you break it down... (1)The IP and mask mean nothing in your scenrio. You have to assume they are correct because you are not given any info about the network. (2)If you don't need a gateway, then this must be a single subnet, non-routed environment so forget about the gateway. (3)The only thing left is the domain and workgroup settings. If this is a 2000 client you can only configure one. Which one do they want? I think you may be missing some info on the question.

My first thought is to make sure you can browse the network. After you know you are on with good connectivity. I would check domain names. If it is a Win2k server and a Win98 workstation. I would check "Client For Microsoft Networks" and not login to a domain. Just keep the workgroup settings.

You can't be on both a domain and a workgroup, but that test question leaves WAY too much leeway. Are they both on the same subnet? is the IP address duplicated? is the subnet mask correct? Is there a router down between the machine and the server? is ther server connecting to the network? is the OS corrupted? does it have a virus? has it been hacked? Lost of different thing sit could be, but yeah, go with the domain/workgroup issue....

I am having this exact same problem, however this is no test question. I have roaming profiles that are not loading on some machines. Basically we migrated our subnet and the gateway got split in two. Those computers that happen to boot up into the same gateway as the server via DHCP see the server just fine. All computers that get into the other gateway are blind to my server. I have had people say that you cannot cross gateways in microsoft networking, but I think there must be some way around this. Everything was working fine before we moved the subnet, but now it's all over the fan. Thanks.