Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. wilson7

    How to extend a partition or disk?

    We tried VVM, and what a nightmare. I'd suspect you'd have better luck with something like partition magic, if its OK to take the cluster down for a short time. During my trials with VVM - i found that Win2kSP3 with VVM keeps the processor at about 50% (as of last month anyway) stability...
  2. wilson7

    NICs, SmartStart & MSCS, lengthy!

    Just a guess: Ensure the setting for the interconnect (which i assume is a 10baseT X-over cable) is set to auto - or try 1/2 duplex 10mbit speed.
  3. wilson7

    MSCS not allowing resourse move or failover

    Are you sure your resources within the clusters are "allowed" to be owned by either node? You must define this when setting up your resources.
  4. wilson7

    MSCS not failing over when Public lan lost

    MSCS does not detect network failures, and therefore will not "failover" to the other node in the event of a network failure. Too bad, so sad.
  5. wilson7

    How to setup clustering.....

    Box 1 and Box 2 will each have their own Node names and IP addresses. Your "cluster" will then have an *additional* node name, and ip address - which can move between the boxes. The boxes do NOT have to be the same, but if you are dealing with a large population for your exchange...
  6. wilson7

    Win2k Server Licencing Problems...

    The license logging service is far from anything "robust". After countless calls to microsoft's premier line, they have come up with the ultimate solution: Stop the License Logging service, and set it to "manual".
  7. wilson7

    Time synchronisation

    mberwanger's suggestion - Timeserv from the resource kit is the best option. It uses SNTP - so as long as you don't care if the time is off by about .5 second - you should be fine. I use this to sync hundereds of machines. it works great.
  8. wilson7

    Is there a way to find out which computeris sending files to a server?

    try using Server Manager (look for open files) or "net session" to see what machines are connected. (this assumes you're not looking for attacks to your box, which is an different issue)
  9. wilson7

    WLBS and MSCS

    Can you be more specific? With MSCS, only one node can access the shared disk at any one time. That means, Node1 holds the disk until you "fail over" the shared disk to Node2. Based on my interpretation of your question, i don't think that these two options will work together...

Part and Inventory Search

Back
Top