Hello my name is George.I have a home network with four computers. three of these computer are connected to the same domain,the other one is a differnt domain connectedon the same network. The problem is I can swap files on all three computers on the same domain. The three computers have operating system of windows server 2003, one is a domain controller{root server] the other two are file servers.The name of my servers are Ire [the domain controller] server1[file server] and server2 [file server].Like I said before I can share files on all of my servers on the same domain, but I can't log on to the domain with file server2.I can log on to file server from the domain controller and the other file server1, but notvice versa. Whenever I tried to log on to the entire networkI can seethe domain name and I click on it the response iswhatagwone [the domain] is not accessible. You might not have permission to use this network resources. Contact the administrator[ I am the administrator] of this server to find out if you have access permission.The list of servers for this workgroup is not currently available.The other computer in the different domain I can share files with all computers so it's not a problem.Thanks for your response!

Machine Hawk, I want to start by restating your problem to make sure I understand it correctly. You have a network for 4 servers, 3 that are in the same domain. Of the 3 domain servers, one is the DC and the other 2 are file servers. Network communications seems to work fine as a client of any of the servers, but for some reason you cannot log onto server 2 with a domain account. Is this correct? This sounds to me like a DNS client issue on server 2. I imagine that you are running DNS services on you Domain Controller (Please correct me if this is not the case), so the other machines within the domain should be pointing to the DC for DNS. I would assume that your DC locator records are registered in DNS (See articles below), because it seems that Server 1 is able to logon with a domain account. The first thing I would do is check the primary DNS server listed on network card(s) of server 2 and match this setting with those on server 1 (from the run command enter ncpa.cpl. Then on each NIC right click then go to "Properties" -> "TCP/IP" -> "Properties". On the resulting window look for the entry in "Preferred DNS Server"). Correct any inconsistencies using the config on server 1 as a guide. If these settings are different between the two servers then run the following at the command-line on server 2. Yhen log off and try to log on with a domain account: ipconfig /flushdns If this still fails or if the DNS client information between the two appears to be the same then open a command prompt on both server 1 and server 2. Then do the following (filling in the FQDN of your domain in the final command): nslookup set type=srv _ldap._tcp.<FQDN of Domain Name> Compare the answers that you find. you should get the same set of records on both servers. If you do find that these are the same and you have already found the settings are the same for the DNS client, then do this at the command line of server 2: ipconfig /flushdns net stop "DNS Client" Now log out and back in with domain credentials. If this still fails then a network trace is the only way to go. I would suggest Netmon 3 be run on the DC, while trying to access a domain resource (such as the sysvol share on the DC). If you need some help assessing the network traces, and do not want to post them here on the forum, let me know. If you get to this point, please post screen shots of the steps you took to get here, as well as an ipconfig /all output from each server, so we can check to make sure nothing else funky is going on. How Domain Controllers Are Located in Windows XP: http://support.microsoft.com/kb/314861 How to verify that SRV DNS records have been created for a domain controller: http://support.microsoft.com/kb/816587 Don't forget to give credit where credit is due, vote this as helpful if it helped you.