A pain in the ... network...

Well, after all this is te first year of the seven of bad luck. Last week our new server crash because a HD failure (lost everything), strange you´ll say, no.. the mirror have suffered the same collapse, total data loss, he-he, we still have a terminal directly connected with the server with the only purpose to make automathic backups. Yeap, this disk blow up too. :) What can be worse? two weeks ago the tape device (for backups, of course!) was removed for maintenance. One good, at night, daily the server perform another backup in another machine, at least this one was fine.
After six hours of work, the system was reinstalled, the last backup restored and all the transactions made again. The rest of the week all was fine.

Today morning, some users had problems connecting to the server and others connected normally:

* From another thread (http://forums.windrivers.com/showthr...5&page=1&pp=15)
PBase001 ask:

Quote:

---

Can you ping the server?

---

Yes, we can ping the server from all the machines.

Quote:

---

Can you browse via double click <Network Places> -> <Entire Network> -> <Microsoft Windows Network> -> Domain

---

When double clicked Domain, an alert pops up with something like "the server is not configured to perform transactions"

Quote:

---

Can you see the Server listed?

---

Obviously not, can´t acces the domain...

* Then, my boss reseted the server, and the situation changed:

We still are able to ping the server. Now, we can access the domain, but the server is not listed there.

** Our techys are here, and they are more clueless than me, after a couple of hours they are suggesting that somehow the security directives are gone.

I´m sorry this is more a rant than a question, but can somebody tell me what the heck is going on?


(Like allways, please forgive me for killing your language in such horrible manner :( )

2 hdd's failing within hours - that's less than 1 in 100 million chance. I suspect something else is wrong there too.. like power supply... or memory/mobo/cpu corrupting data. Do a full system test before bringing the server back in production or you will have to deal with this again.
Check if the IP is properly assigned (static and the right one!) and that DNS is working properly. You may have to reset the machine account in the domain if it's not a DC. If it is a DC, has the restoration of AD data been performed in AD services restore mode? Do you have a secondary DC in your domain? Have the FSMO roles been assigned properly?

To me, "failing" is not the proper word, and were 3 hdd's not 2.

I'm sorry, I must have said it before but I'm not a Techy, I am a user with above average knowledge in computers than the common user.

Quote:

---

You may have to reset the machine account in the domain if it's not a DC. If it is a DC, has the restoration of AD data been performed in AD services restore mode? Do you have a secondary DC in your domain? Have the FSMO roles been assigned properly?

---

DC, AD and FSMO are for....? :( Perhaps not so above..

DC = Domain Controller
AD = Active Directory
FSMO = Flexible Single Master Operations

Us techies like to use acronyms. ;)


I would have to agree. 3 Hard Drives all at once. Something else happened there that day.

Thanks BOB IROC.

Quote:

---

You may have to reset the machine account in the domain if it's not a DC. If it is a DC, has the restoration of AD data been performed in AD services restore mode? Do you have a secondary DC in your domain? Have the FSMO roles been assigned properly?

---

Yes is the only DC, but the restoration was not of the OS (w2k server), the OS was installed from scratch in a new hdd, the backup we own is the sql database of the contable system.

My brain is still trying to understand the meanings of Flexible Single Master Operations roles...