Trying to do a log(-#) get domain error. never had this problem before. how do I fix it?

the issue might be a server connection error ..just use another browser like Mozilla or internet explorer for to log into your mail service ..and if you didn't deleted them ..they will be there.. Usually the mail domains ..keep the mails even in the trash folder for about a month ..so even if you deleted them by mistake you will be able to find them on the domain's web page ..
OR ..you just need to sign in again ..cause another person remained signed in ..or something like that ..
Just time the domain .in the search engine ..for ex..windows live ...or yahoo mail ..or what ever teh domain is..and the log in page will be displayed..Use your identification and password again and log into ..to read the mail ..
If you use a mail program ..like Thunderbird ..or outlook ...probably it is a communication with the server problem ..specially if it uses an smtp ..imap ..and not pop server to download teh mails and keep in computer ..

The question is:

What causes a user profile not to be loaded in Windows domain based network?

the answer is:
there are probably 3 broad reasons for this,
1. the user corrupted their profile somehow, such as shutting down without logging off (hard power off)
2. the connection to the domain was lost ungracefully, and offline information was not copied entirely, causing a mismatch of some encrypted profile data, (effectingly corrupting again) and preventing the logon.
3. an unknown event took place between the last time the user sucessfully logged on, and this time where the profile is now not loading. this could be hardware related (faulty Hard disk), RAM parity errors( bad memory), a change to the user profile SID details on the domain controller or other domain change.

Usually the cause is not so much a problem, unless it consistantly reoccurs.

Fixing it however, in XP is fairly easy.
with an account with domain admin rights, just navigate to the UNC path "\\computername\c$\documents and settings" - note the name of the folder/user affected, and just .old their profile folder.
example, username is Philip. - you see in their c:\documents and settings\ folder the folder called Philip, rename it to philip.old or something else.

You have to ensure this is done while the user is logged off, as files in this folder will be in use otherwise. potentially useful to reboot the computer before navigating to the profile folder.

If this problem just started on a network that was working try resetting (unpluging) the router and modem. Another option is to do a "repair"
I assume this is a wireless connection.
Open your wireless network connection and go to the support tab.
Here is where you can do a repair. This will reset your network adaptor.
Try this and it should solve the problem.

Domain name? Is there a drop down menu where you can unselect to login on a domain? Domains are generally for business or networks.

Also, try booting into safe mode and logging in as an administrator (leave password blank). Once there, do a restore back to a day whe you were able to login and this will fix the problem.

In active directory on the server you need to create a network admin user and any other normal users u want to have access to the domain.
Then you have to add the pc to the domain using the network admin user.
After this u can log on to the pc with the network admin or the other created user names.

Are you logging in through terminal services? If so you need to give the user "allow logon through terminal services" permission in group policy.

Otherwise you need to give the user "allow logon locally" permission on the domain controller.

press cortl+alt+del whneyou have the log on screen
click on option button at eh lower right corner, that will bring you;
login name
password
domain
change the domain to local computer,
login name =admin or administrator,
password= blank, or Admin or Administrator

The resolution and workaround to solve the error is as below.

1. Login to the Windows 2003 domain controller, and delete the computer account object from the Active Directory by using Microsoft Management Console (MMC) which you can always access from “Manage Your Server”.
2. Log-in to the PC workstation as local administrator. If you cannot logon as local administrator, try to unplug the network cable and logon to the computer by using a domain administrator user that used to logon on the PC before, by using cached logon credentials feature.
3. Go to Control Panel, then click on System icon, then go to Computer Name tab.
4. Unjoin the computer from the domain by clicking on “Change”. You should see that Domain button is now selected. Remember your domain name in the text box. Select (Click) on “Workgroup” to remove the computer from the domain, and put any workgroup name in the text box (e.g. workgroup).
5. Click OK to exit.
6. Restart the computer (optional)
7. Go back to the Control Panel, launch System properties and then go to Computer Name tab, and click on “Change”.
8. Rejoin the domain by uncheck the Workgroup button and select (check) Domain button, and put in the domain name noted above into the text box.
9. Click OK to exit.
10. Reboot the PC.

This should solve the unable to logon to domain error, without changing or losing the user profiles on AD.

You may need to edit group policy if this was once in a domain. You may want to try rebooting the machine and logging into the 'LOCAL' machine and see if you have rights that way. Each machine by default has one administrator account but if the server was part of a domain, that right may have been removed. You may need to reset OWNER privileges for all files in the machine.

Have I got this right. You want to prevent them from logging on to a particular pc without a username and password?
If the server is off the domain is not active to validate requests for authentication.
It might help me understand what you are trying to do if you tell me why you want this computer isolated as the solution I am thinking about may not be the right one. Is it in a public area or do you want to prevent guest users or some other reason.
Look forward to your next posting.
Julie