Windows

This sounds like a PC which normally logs into a domain. When the domain isn't available (no network connection), The user logs in using a copy of the domain user settings which have been saved loacaly from the last domain login. Check the network configuration of the users with that message.

You have to right click network neighborhood click on properties, then you will see the netwoork window click on identification then click on change, here you will be able to change the way the computer logs to the server, you must tell it to log asa workstation or domain, but make sure that you have an account set up for the workstation when you choose to set it up as a domain, make sure all other services are ok. including your TCP/IP address, use your DHCP, WINS & DNS service to configure your TCP/IP address it's much more simple.
Hope this helps!

One more thing, make sure that your network card is not bad, I had problems with 2 of NETGARE NIC cards, you can change the card if all fails with a card from another PC.
But first make sure that you can log on to the Domain, like the answer from# 1, you are logging the PC (workstation) with cache, so it's not understanding that you have a Domain setup.

Are your web developers on a different subnet? most logging issues that start up after it's been working for a while tend to be physical issues. i.e. bad cables, unpowered hubs, bad nic's, etc... make sure the domain they're logging into is a valid domain. make sure the PDC/BDC didn't get moved to a different subnet, and if so, that you have a router, or a device that forwards ip requests. Make sure, if you're using a DHCP server, that you have enough IP addresses.

This message is caused when the account for the WORKSTATION (not the user) does not match when the w/station tries to authenticate with the DC. To resolve this, you must remove the workstations acount from the PDC, and then rejoin the domain at the workstation.

This is caused when the two accounts get out of sync, due to not communicating for some time. There will be a reason why these machines are not talking to the PDC for long enough to get out of synch - are they used in standalone modeat any time? is there some network prob? At least you know what to look for now!

One problem is that a slow network connection can cause this - to increase the timeout period, change the following reg key - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters

by ading the following value:

Value Name: ExpectedDialupDelay
Data Type: Reg_Dword
Data Value is in seconds.
Min Value: 0
Max Value: 600 in decimal.


rgds

G