profiles and permissions in server 2008

We are running server 2008. It has been running fine until a few days ago.
Now all the workstations, when logging in, cannot locate their profiles correctly and there is a second logon screen poppng up asking for a username and password.
It is as if the workstations are not part opf a domain.
Also, the workstations cannot be pinged from the werver and the netview command from the server gives a 6118 error message.
As far as I know nothing has changed on the server or workstations.
There is one thing I have noticed - the disk space on C Drive is down to 1 gb

Please can someobe advise on a course of action
doctorbillTechAsked:
Who is Participating?
 
doctorbillConnect With a Mentor TechAuthor Commented:
the one error that stands out is a "file replication error due to low disk space". I presume that this would effect profiles and shares, which is where the problems are at the moment
0
 
louisreevesConnect With a Mentor Commented:
In your example, There may be more then one thing wrong. However, The most alarming is the disk size. You need to have plenty of space for windows 2008. It is a peacock and it wants to fly:

http://technet.microsoft.com/en-us/library/cc753439(WS.10).aspx

The second logoin mau be the local login as the server is likely not responding to requests. It may be picking up dhcp from somewhere else. I dont know on that but  get the free disk space over 15 GB first.

Good luck!

L
0
 
kevinhsiehConnect With a Mentor Commented:
I don't think that 1 GB free space is causing the problem on your DC. Check event logs on your DC, file server, and PCs. There should be a good clue in there.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
Kevin HaysConnect With a Mentor IT AnalystCommented:
Agree, checking the event logs is the 1st place to usually look as to whats going on.

start/run/eventvwr

0
 
doctorbillTechAuthor Commented:
do you guys have any idea what may be causing this - event logs are very big and have a lot of info to search through
0
 
Kevin HaysConnect With a Mentor IT AnalystCommented:
look for warnings and errors to start with on the logs.  Start with the most recent.
0
 
doctorbillTechAuthor Commented:
please close question
0
 
doctorbillTechAuthor Commented:
I registerd the NIC with DNS and all the associations were recreated.
0
 
Kevin HaysIT AnalystCommented:
Glad you got it fixed Doctorbill.  You would be correct on the disk space btw.  Some reason I never got alerted you responded to this, sorry about that.

Kevin
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.