chris.thompson

We have two servers running. The mainboard in them (I don't recall the exact model) is an Asus with a P45 north and ICH10R south bridge. In each we have 4x Seagate 7200.11 500GB hard drives (and yes the firmware is updated) in a Raid 10 on the integrated Intel raid. We're having a couple problems with them, but they're most likely related. Disk reads and writes are pretty slow, I've run tests and the drive in my laptop has better performance. But the biggest concern is that doing large file copies renders them unusable until power is cycled. It doesn't happen every time, but occasionally (once or twice a week) we'll come in to work and nobody will have access. No video comes up on the monitor connected to it, and trying to remote desktop to it just hangs trying to connect. Cycling the power allows it to boot normally and function like it should (though it does always kick off an verify and repair scan by the Intel Matrix utility). The thing is, we do a backup of the VMs on the systems to the local array at night, and today when I was copying a VM to the array, the same thing happened. I've done the "Long" test on all of the drives in Seatools, they don't seem to be the issue. And like I said, I've updated the firmware to the latest. I've read a lot of things about similar problems in Vista (concerning running RAID on Intel controllers), but all conversation on that seems to stop about 2 years ago. It seems likely to me that it's the controller, but I'm not really sure what I can try. Any thoughts? Thanks!

Thanks a lot, that seemed to do the trick.

To start, for our setup, we have two Domain Controllers, both running Hyper-V. One of the VMs, a member server, is acting as a print server. It has print services installed, and we have added 8 network printers to it. It works pretty well. What I've noticed is that somehow, both domain controllers have picked up 4 printers from the print servers, and at the end of each printer name is (Redirected 1). So, if a printer is named "Accounting" on the print server, on the domain controllers it is named "Accounting (Redirected 1)". None of these printers work. It seems like they don't have any drivers. My bigger problem is that I can't remove them, I get an "Printer cannot be removed. Access is denied." message. I'm logged onto the domain controller with the domain administrator account. They're also causing a lot of errors in the event log, mostly related to Terminal Services. I'm not really sure what I can do to get rid of these, I'm hoping someone can help. It is possible that another person screwing around somehow added these there, but I'm mostly concerned with getting rid of them. Thanks for any help!

I did the nslookup on two different systems. On mine (which is on the domain) they both return the correct IP, 222. On the other one, a test system which is off the domain, it returned 250 for s1 and 222 for s2. I'm going to try deleting the record out later when nobody is here. Is there any amount of time I should wait after deleting it, and should I add it to one or the other first? Thanks! Edit: I've now deleted the entry for wiki out of DNS altogether. When doing an nslookup on s1 and s2 on my domain system, it says it can't find it (as it should). On a few non-domain systems (after flushing dns even) it still reads s1 as 250 and s2 as 222.

I have a fairly interesting problem happening. We have two servers running Windows 2008 Enterprise Server. They are basically copies of each other; each one is a Domain Controller, Global Catalog Server, DNS Server, and also runs Hyper-V. For the purposes of this I'll call them S1 and S2. They're both fully patched. We just recently moved our local wiki from one server to a virtual server, and so I updated the CNAME record for it for the new system that it's on (and that system has a corresponding A record). It was on IP 250, now it's on 222. People on the domain can get to it with no problem, no matter what server they use for DNS. Non-domain computers, such as our linux clients and some other scattered Windows systems can resolve properly to 222 only when using S2, but when using S1, they still resolve to 250. I tested a few systems and found this to be very consistent. I had one machine off the domain using S1 for DNS, and it gave 250. I put it on the domain, and it started giving 222. S2 gave 222 both on and off the domain, so it really seems like it's an issue with not being on the domain, which I'm pretty stumped about because I don't know why that would have anything to do with DNS. I've tried ipconfig/flushdns on these systems that don't get the proper address as well. Any help or suggestions would be greatly appreciated! If I'm not clear about anything let me know and I'll try to elaborate.