Can you ping the member server from another workstation? If not that points to some kind of wiring/nic/switch problem. or Was your domain controller restarting last night (windows update?) when the backup was to happen and unavailable to the backup program to validate the name? Everyone can login now but maybe not last night when the backup job tried to run. Before you disjoined the server, could the server communicate with the rest of the network? Doug ________________________________ From: windows2000-bounce@xxxxxxxxxxxxx [mailto:windows2000-bounce@xxxxxxxxxxxxx] On Behalf Of Ron Leach Sent: Friday, May 13, 2005 9:50 AM To: windows2000@xxxxxxxxxxxxx Subject: [windows2000] Unable to connect to domain Good Morning List, We have a simple small business network. One domain controller, one member server (accounting & bookkeeping) and ~25 workstations. Windows 2000 Server with Win2k & Win XP clients. I come in this morning and I start receiving complaints that users cannot print jobs from the printer that is installed on the member server. Upon investigating a little further I find that the backup job on the same member server failed. The reason being that the user's logon account for the backup service was rejected. Event log states that 'No domain controller could be contacted...' I know that this is not correct because everyone can login, connect to network shares (on the dc) and print (printers installed on the dc). No dns changes have been made. The only other event that was different was that we installed an ODBC driver on the member server yesterday. I have since removed it. I'm beginning to wonder if the nic has gone bad??? It has a green status light but... I tried disjoining the member server from the domain and re-joining but now it says it does not recognize the domain name. Any insight would be very much appreciated! Thanks Ron