Cluster network 3 is down

Cluster network 'Cluster Network 3' is down. None of the available nodes can communicate using this network. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related
to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

Hello,
Come back and mark the replies as answers if they help and unmark them if they provide no help.
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Cara Chen
TechNet Community Support

Similar Messages

  • Failover Cluster Network Name Failed and Can't be Repaired

    I have an issue that seem to be a different problem than any others have encountered.
    I've scoured everything I can find and nothing has fixed my problem.
    The problem starts with the common problem of the cluster network name failing on my 2 node server 2012 file server cluster.  The computer object was still in AD and appeared to be fine so it was not the common problem of the object
    getting deleted somehow.  At the time, there was no other object with that name in the recycling bin, so I don't think it was mistakenly deleted and quickly recreated to cover any tracks, so to speak.
    Following one guide, I tried to find the registry key that corresponded with the GUID of the object, but neither node in the cluster had it in its registry (which may be part of the problem).
    Since it was in the failed state, I tried to do the repair on the object to no avail.
    We run a "locked down" DC environment so all computer objects have to be pre-provisioned.  They were all pre-provisioned successfully and successfully assigned during cluster creation.  The cluster was running with no issues for a month
    or so before this problem came up.
    When I do a repair on the object while taking diagnostic logs the following 4609 error appears:
    The action 'Repair' did not complete. - System.ApplicationException: An error occurred resetting the password for 'Cluster Name'. ---> System.ComponentModel.Win32Exception: Unknown error (0x80005000)
    There appears to be a corresponding 4771 error with a failure code 0x18 that comes from the security log of the DC that states there was a Kerberos pre-authentication failure for the cluster network name object (Domain\Clustername$)
    I believe this is what is causing the repair failure.  All the information I found related to security error 4771 was either a bad credentials given for a user account or the fix was to reconnect the computer to the domain.  I can't seem to find
    a way to do this with the cluster network name.  If there's a way please let me know.
    I've tried a number of things, like resetting the object, disabling it, deleting and creating a new object with the same name, deleting that new object and recovering the original, etc...
    Can anyone shed some light on what is going on and hopefully how to fix it other than rebuilding the cluster?  I'm quite close to just tearing it down and building it back up but am hesitant because this cluster in currently in production...
    Any help would be appreciated

    Hi,
    I don’t find out the similar issue with yours, base on my experience, the 4096 error
     often caused by the CSV disk issue, and the 0x80005000 error some time caused by the repetitive computer object in OU. Please check the above related part or run the validate test then post the error information.
    Although I do have a CSV, there doesn't seem to be any problems with it and it was running just fine for a month or so before the problem started.  I double checked and there is no duplicate computer objects, maybe I don't understand what you mean by
    repetitive, could you explain further?
    The cluster validates successfully with a few warnings:
    Validating cluster resource Name: DT-FileCluster.
    This resource is marked with a state of 'Failed' instead of
    'Online'. This failed state indicates that the resource had a problem either
    coming online or had a failure while it was online. The event logs and cluster
    logs may have information that is helpful in identifying the cause of the
    failure.
    - This is because the cluster name is in the failed state
    Validating the service principal names for Name:
    DT-FileCluster.
    The network name Name: DT-FileCluster does not have a valid
    value for the read-only property 'ObjectGUID'. To validate the service principal
    name the read-only private property 'ObjectGuid' must have a valid value. To
    correct this issue make sure that the network name has been brought online at
    least once. If this does not correct this issue you will need to delete the
    network name and re-create it.
    - This is definitely related to the problem and the GUID probably got removed when we attempted a fix by resetting the object and trying the repair from the failover cluster manager.
    The user running validate, does not have permissions to create
    computer objects in the 'ad.unlv.edu' domain.
    - This is correct, we run a restricted domain.  I have a delegated OU that I can pre-provision accounts in.  The account was pro-provisioned successfully and was at one point setup and working just fine.
    There are no other errors nor warnings.

  • Cluster Network Randomly Failing on Hyper-V Cluster

    Please let me know if there is a more appropriate forum. I am having a really strange issue that is seemingly random. I have a 3 host cluster that are all identical hardware and running Hyper-V Server 2012 R2. The networking is as follows and each network
    is a different VLAN/Subnet:
    3 Cluster networks for virtual machines
    1 Cluster network for cluster traffic/management
    1 Heartbeat network
    2 iSCSI networks for storage
    All of the networks are perfectly fine except for one which seems to fail on a random node at a random time during the day (so far, a maximum of once per day).
    If I start to live migrate virtual machines that are on the failed network, the cluster network comes back up. The cluster networks are teamed using SCVMM and they are switch independent and running the Dynamic teaming algorithm. We have tried changing the
    network switches to see if it was faulty network hardware and things ran fine for one day and then just happened again today so we've ruled that out. The only error message I get is 1127 which is the error stating that the cluster network has gone into a failed
    state which doesn't help much. I've run the cluster validation tool for networking several times and it always passes 100%. What I am worried about is hardware incompatibilities as I am using Dell servers (PowerEdge R720) that have Broadcom NIC's in them.
    We have 12 Ethernet ports in each server and they are all identical hardware. Four of them are integrated Broadcom, another four that are from a Broadcom quad add-on NIC, and another 4 that are from an Intel quad add-on NIC. All are server grade NIC's. The
    only problem I've had in the past is with VMQ which we've had to disable as a workaround but that has always stabilized our virtual networks. In any case all of the cluster networks for virtual machines are set up identically and only this particular one randomly
    fails on any one of the three hosts (it has happened at least once on each node now).
    I am wondering if anyone has had this experience before. I have read that there are some nasty compatibility issues between Broadcom and Hyper-V  but I am wondering if someone could give me some ideas to find out how to narrow this down since the event
    logs don't seem to be speaking in obvious terms to me.
    Please let me know if you have any suggestions on how to narrow down what's causing this or if there is more information that I could provide. In the meantime, I'm going to try and take note of which virtual machines are running on the host that has the
    network fail just in case there's some correlation there but that could take a while to accrue any useful data and our users aren't too happy with the instability...
    Thank you in advance for your time and sorry for the lengthy post!

    Since I made the change last Friday evening, 4/10, I haven't experienced the issue. I won't be completely convinced that this resolved it until I monitor for at least one more week since it didn't actually present itself for the first time until I was already
    one week into live deployment. Also, this link below is much more eloquent than how I put it and describes my issue exactly. Coupled with the KB article that someone posted within this comments section (the same that I posted earlier here) of the article,
    this is what led me to check the VMQ status through PowerShell which is much better than going through the registry to do it (I'm running Hyper-V Server 2012 R2 which is like core so I don't have the GUI options shown in the article).
    http://alexappleton.net/post/77116755157/hyper-v-virtual-machines-losing-network
    I could try updating the driver but there is mention in the comments of this post that driver updates have yet to resolve this issue so we may still be waiting on Broadcom for a fix. Please confirm otherwise if anyone has any information.

  • Host server live migration causing Guest Cluster node goes down

    Hi 
    I have two node Hyper host cluster , Im using converged network for Host management,Live migartion and cluster network. And Separate NICs for ISCSI multi-pathing. When I live migrate the Guest node from one host to another , within guest cluster the node
    is going down.  I have increased clusterthroshold and clusterdelay values.  Guest nodes are connecting to ISCSI network directly from ISCSI initiator on Server 2012. 
    The converged networks for management ,cluster and live migration networks are built on top of a NIC Team with switch Independent mode and load balancing as Hyper V port. 
    I have VMQ enabled on Converged fabric  and jumbo frames enabled on ISCSI. 
    Can Anyone guess why would live migration cause failure on the guest node. 
    thanks
    mumtaz 

    Repost here: http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/threads
    in the Hyper-V forum.  You'll get a lot more help there.
    This forum is for Virtual Server 2005.

  • DAG 2010 Cluster IP address resource 'Cluster IP Address' cannot be brought online because the cluster network replication

    Hello,
    DAG Exchange 2010 SP3 RU6 with MAPI network and Replication network. All works correctly.
    But, when the DAG member restarts , the cluster goes offline and i can't bring it online.
    The message error:
    Cluster IP address resource 'Cluster IP Address' cannot be brought online because the cluster network 'Cluster Network 1' is not configured to allow client access.
    Cluster Network 1 is the replication network and it is normal that allow client access is unchecked
    I already tried to check, apply then uncheck apply. it does anything.
    Could you please help me to figure out the issue ?
    Best regards

    Hi,
    Check below link.
    http://forums.msexchange.org/Cluster_network_name_is_not_online/m_1800552315/tm.htm
    I was able to resolve the issue without taking down any resources.
    First, I noticed that the Failover Cluster Manager "Cluster Name" had the IP address of the replication network only..
    After going back through the guide @
    http://technet.microsoft.com/en-us/library/dd638104.aspx I changed the properties on the NICs for file sharing, etc..I then adjusted windows firewall rules to block traffic from my MAPI network destined for the replication network. 
    I then removed the IP from the replication network on the DAG leaving only the 1 MAPI network IP.
    After an hour or so, I ran Get-DatabaseAvailabilityGroupNetwork and seen that the MAPIAccess property was finally set to true on my MAPI network. I went back to Failover Cluster Manager and my Cluster Core Resource Cluster Name dropped the IP address that was
    associated (IP from the replication network) I added a new IP from my Mapi network range, updated the DAG IP in Exchange and the DNS record for the DAG and my cluster resource came online.

  • Sql cluster network

    i have got a curious question in regards to sql clustering, what if the client network goes down and the hb network is still up, does it failover and why? kindly assist.

    Hello,
    There is no such thing as a "heaertbeat" network anymore. You have four choices: Client communications, cluster communications, client and cluster, or none.
    Anything marked for cluster communications means the cluster can do internal communications over that interface - which could be things like resource health checking, monitoring, cluster views, etc.
    If your "client" network went down, the clients wouldn't be able to connect. You may have some other resources go offline depending on many different settings, and those settings may cause a failover to occur. However, if the failover would occur
    there shouldn't be a problem as long as there is a network available for cluster communications.
    -Sean
    The views, opinions, and posts do not reflect those of my company and are solely my own. No warranty, service, or results are expressed or implied.

  • Ethernet/networking link down // AppleYukon2 - en0 link down

    *Massive writing into a Volume located on a NAS // Ethernet/networking link down // AppleYukon2 - en0 link down*
    Scenario
    Writing a massive data into a volume (sparsebundle) on a NAS (network attached store).
    *Problem / Error*
    Always during this process the Ethernet link down.
    Then the MAC OS X (10.5.6) freeze – no reset, no shutdown and no volume eject – after trying some clicks the spinning wheel comes and only soft reset or hard reset shutdown.
    *Technical Info*
    Wireless Device: Linksys - WRT54G firmware updated
    NAS/External Hard Drive: Iomega - Home Network HD firmware updated
    MacBook Pro // Mac OS X (10.5.6) // 2.2 GHz Intel Core 2 Duo // 2 GB
    Logs
    +LOG 1+
    Apr 8 18:56:30 wslyMac /System/Library/CoreServices/backupd[207]: Backup requested by user
    Apr 8 18:56:30 wslyMac /System/Library/CoreServices/backupd[207]: Starting standard backup
    Apr 8 18:56:36 wslyMac /System/Library/CoreServices/backupd[207]: Mounted network destination using URL: smb://admin@STORAGE-7AB4/TimeMachine
    Apr 8 18:56:36 wslyMac /System/Library/CoreServices/backupd[207]: Backup destination mounted at path: /Volumes/TimeMachine-1
    Apr 8 18:56:58 wslyMac kernel[0]: AppleYukon2: 00000000,00000001 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
    Apr 8 18:57:07 wslyMac hdiejectd[231]: running
    Apr 8 18:57:08 wslyMac kernel[0]: jnl: disk1s2: replay_journal: from: 8088064 to: 15072256 (joffset 0x7d0000)
    Apr 8 18:57:25 wslyMac kernel[0]: jnl: disk1s2: journal replay done.
    Apr 8 18:57:25 wslyMac fseventsd[37]: event logs in /Volumes/TimeMachine_Backup/.fseventsd out of sync with volume. destroying old logs. (1989 18 2969)
    Apr 8 18:57:25 wslyMac /System/Library/CoreServices/backupd[207]: Disk image /Volumes/TimeMachine-1/wslyMac_001b63b30d6b.sparsebundle mounted at: /Volumes/TimeMachine_Backup
    Apr 8 18:57:25 wslyMac /System/Library/CoreServices/backupd[207]: Backing up to: /Volumes/TimeMachine_Backup/Backups.backupdb
    Apr 8 18:57:29 wslyMac fseventsd[37]: log dir: /Volumes/TimeMachine_Backup/.fseventsd getting new uuid: CBE196F1-1008-4BFB-8D4A-AD9504E68ACF
    Apr 8 18:57:59 wslyMac /System/Library/CoreServices/backupd[207]: Event store UUIDs don't match for volume: Macintosh HD
    Apr 8 18:58:00 wslyMac /System/Library/CoreServices/backupd[207]: No pre-backup thinning needed: 29.79 GB requested (including padding), 245.17 GB available
    Apr 8 19:20:31 wslyMac kernel[0]: AppleYukon2: 00000000,00000017 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
    Apr 8 19:21:35 wslyMac kernel[0]: AppleYukon2: 00000000,0000001b sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
    Apr 8 19:21:53 wslyMac kernel[0]: AppleYukon2: 00000000,0000001e sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
    Apr 8 19:23:32 wslyMac kernel[0]: AppleYukon2: 00000000,00000004 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
    Apr 8 19:23:37 wslyMac kernel[0]: AppleYukon2: 00000000,00000001 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
    Apr 8 19:23:41 wslyMac kernel[0]: AppleYukon2: 00000000,00000011 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
    Apr 8 19:25:32 wslyMac kernel[0]: smbiodsendall: Timed out waiting on the response for 0x32
    Apr 8 19:25:38 wslyMac kernel[0]: AppleYukon2: 00000000,000003e8 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket timedout
    Apr 8 19:32:07 localhost kernel[0]: npvhash=4095
    +LOG 2+
    Apr 8 22:03:19 wslyMac /System/Library/CoreServices/backupd[356]: Backup requested by user
    Apr 8 22:03:19 wslyMac /System/Library/CoreServices/backupd[356]: Starting standard backup
    Apr 8 22:03:19 wslyMac /System/Library/CoreServices/backupd[356]: Mounted network destination using URL: smb://admin@STORAGE-7AB4/TimeMachine
    Apr 8 22:03:19 wslyMac /System/Library/CoreServices/backupd[356]: Backup destination mounted at path: /Volumes/TimeMachine-1
    Apr 8 22:03:26 wslyMac /System/Library/CoreServices/backupd[356]: Disk image /Volumes/TimeMachine-1/wslyMac_001b63b30d6b.sparsebundle mounted at: /Volumes/TimeMachine_Backup
    Apr 8 22:03:26 wslyMac /System/Library/CoreServices/backupd[356]: Backing up to: /Volumes/TimeMachine_Backup/Backups.backupdb
    Apr 8 22:03:26 wslyMac /System/Library/CoreServices/backupd[356]: Ownership is disabled on the backup destination volume. Enabling.
    Apr 8 22:03:26 wslyMac KernelEventAgent[35]: tid 00000000 received unknown event (256)
    Apr 8 22:03:27 wslyMac /System/Library/CoreServices/backupd[356]: Event store UUIDs don't match for volume: Macintosh HD
    Apr 8 22:08:22 wslyMac /System/Library/CoreServices/backupd[356]: Backup content size: 66.6 GB excluded items size: 44.6 GB for volume Macintosh HD
    Apr 8 22:08:22 wslyMac /System/Library/CoreServices/backupd[356]: No pre-backup thinning needed: 26.46 GB requested (including padding), 249.57 GB available
    Apr 8 22:08:22 wslyMac /System/Library/CoreServices/backupd[356]: Waiting for index to be ready (909 > 0)
    Apr 8 22:40:50 wslyMac kernel[0]: AppleYukon2: 00000000,0000009c sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
    Apr 8 22:40:50 wslyMac kernel[0]: AppleYukon2: 00000000,00000008 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
    Apr 8 22:40:50 wslyMac kernel[0]: AppleYukon2: 00000000,00000004 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
    Apr 8 22:41:20 wslyMac kernel[0]: smbiodreconnect: Reconnected to STORAGE-7AB4
    Apr 8 22:41:49: --- last message repeated 1 time ---
    Apr 8 22:41:49 wslyMac kernel[0]: disk1s2: 0x48 (UNDEFINED).
    Apr 8 22:41:50 wslyMac kernel[0]:
    Apr 8 22:41:50: --- last message repeated 1 time ---
    Apr 8 22:41:50 wslyMac kernel[0]: jnl: disk1s2: dojnlio: strategy err 0x5
    Apr 8 22:41:50 wslyMac kernel[0]: jnl: disk1s2: end_transaction: only wrote 0 of 463360 bytes to the journal!
    Apr 8 22:41:50 wslyMac kernel[0]: smbiodreconnect: Reconnected to STORAGE-7AB4
    Apr 8 22:41:50 wslyMac fseventsd[39]: disk logger: failed to open output file /Volumes/TimeMachine_Backup/.fseventsd/00000000005a57d8 (Invalid argument). mount point /Volumes/TimeMachine_Backup/.fseventsd
    Apr 8 22:41:50 wslyMac kernel[0]: smbfssmb_reopenfile: Reopen 1a with open deny modes failed because the modify time has changed was 1239244850s 0ns now 1239244910s 0ns!
    Apr 8 22:41:50 wslyMac kernel[0]: smbfssmb_reopenfile: Warning: pid 360(diskimages-helpe) reopening of 1a failed with error 5
    Apr 8 22:41:50 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)(Error) IndexCI in ci_ftruncate:ftruncate(53 /Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A- AE37-350EFD1764B1/live.0.indexPostings, 131072) error:22
    Apr 8 22:41:50 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)(Error) IndexCI in initPayload:ftruncate err: 22
    Apr 8 22:41:50 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)(Error) IndexGeneral in notify_lowspace:low space for device 234881029 (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)
    Apr 8 22:41:50 wslyMac mds[33]: (Error) Volume: LOW DISK SPACE device:234881029
    Apr 8 22:41:50 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)(Error) IndexCI in ci_ftruncate:ftruncate(54 /Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A- AE37-350EFD1764B1/live.0.indexPostings, 131072) error:22
    Apr 8 22:41:50 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)(Error) IndexCI in initPayload:ftruncate err: 22
    Apr 8 22:41:50 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98 -813F-46DA8DCFF8AF)(Error) IndexCI in ci_ftruncate:ftruncate(48 /Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98- 813F-46DA8DCFF8AF/live.0.indexPostings, 4096) error:22
    Apr 8 22:41:50 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98 -813F-46DA8DCFF8AF)(Error) IndexCI in initPayload:ftruncate err: 22
    Apr 8 22:41:50 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)(Error) IndexCI in copyFileOrFd:error (22) opening 0.indexGroups
    Apr 8 22:41:50 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)(Error) IndexCI in recoverIndex:Unrecoverable error: could not recover groups file (0.)
    Apr 8 22:41:50 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)(Error) IndexCI in CIMetaInfoCreate:Tried to create index when index already existed /Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A- AE37-350EFD1764B1
    Apr 8 22:41:50 wslyMac /System/Library/CoreServices/backupd[356]: Error: (-50) SrcErr:NO Copying /Applications/Utilities/System Profiler.app/Contents/version.plist to /Volumes/TimeMachine_Backup/Backups.backupdb/wslyMac/2009-04-08-220327.inProgre ss/0788B97B-3F1C-4331-90E0-7FAE0EDDC3D1/Macintosh HD/Applications/Utilities/System Profiler.app/Contents
    Apr 8 22:41:50 wslyMac /System/Library/CoreServices/backupd[356]: Error: (-50) SrcErr:NO Copying /Applications/Utilities/System Profiler.app/Contents to /Volumes/TimeMachine_Backup/Backups.backupdb/wslyMac/2009-04-08-220327.inProgre ss/0788B97B-3F1C-4331-90E0-7FAE0EDDC3D1/Macintosh HD/Applications/Utilities/System Profiler.app
    Apr 8 22:41:50 wslyMac /System/Library/CoreServices/backupd[356]: Indexing a file failed. Returned -1132 for: /Applications/Utilities/System Profiler.app, /Volumes/TimeMachine_Backup/Backups.backupdb/wslyMac/2009-04-08-220327.inProgre ss/0788B97B-3F1C-4331-90E0-7FAE0EDDC3D1/Macintosh HD/Applications/Utilities/System Profiler.app
    Apr 8 22:41:50 wslyMac /System/Library/CoreServices/backupd[356]: Aborting backup because indexing of file failed.
    Apr 8 22:41:50 wslyMac /System/Library/CoreServices/backupd[356]: Stopping backup.
    Apr 8 22:41:50 wslyMac /System/Library/CoreServices/backupd[356]: Error: (-50) SrcErr:NO Copying /Applications/Utilities/System Profiler.app to /Volumes/TimeMachine_Backup/Backups.backupdb/wslyMac/2009-04-08-220327.inProgre ss/0788B97B-3F1C-4331-90E0-7FAE0EDDC3D1/Macintosh HD/Applications/Utilities
    Apr 8 22:41:50 wslyMac /System/Library/CoreServices/backupd[356]: Copied 1738 files (4.0 GB) from volume Macintosh HD.
    Apr 8 22:41:55 wslyMac /System/Library/CoreServices/backupd[356]: Backup canceled.
    Apr 8 22:41:56 wslyMac /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[117]: StatusMonitor::volumesChangedCallBack returned -47
    Apr 8 22:42:06: --- last message repeated 1 time ---
    Apr 8 22:42:06 wslyMac /System/Library/CoreServices/backupd[356]: Failed to eject volume /Volumes/TimeMachine_Backup (FSVolumeRefNum: -113; status: -47; dissenting pid: 0)
    Apr 8 22:42:06 wslyMac /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[117]: StatusMonitor::volumesChangedCallBack returned -47
    Apr 8 22:42:56 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98 -813F-46DA8DCFF8AF)(Error) IndexCI in ci_ftruncate:ftruncate(43 /Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98- 813F-46DA8DCFF8AF/live.0.indexIds, 32768) error:22
    Apr 8 22:42:56 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98 -813F-46DA8DCFF8AF)(Error) IndexCI in openindexfile:ftruncate error: 22, size: 32768, live.0.indexIds
    Apr 8 22:42:56 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98 -813F-46DA8DCFF8AF)(Error) IndexCI in ContentIndexOpenBulk:Could not open /Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98- 813F-46DA8DCFF8AF/live.0.; needs recovery
    Apr 8 22:42:56 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98 -813F-46DA8DCFF8AF)(Error) IndexCI in copyFileOrFd:error (22) opening 0.indexGroups
    Apr 8 22:42:56 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98 -813F-46DA8DCFF8AF)(Error) IndexCI in recoverIndex:Unrecoverable error: could not recover groups file (0.)
    Apr 8 22:42:56 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98 -813F-46DA8DCFF8AF)(Error) IndexCI in CIMetaInfoCreate:Tried to create index when index already existed /Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/B8028080-DC7D-4A98- 813F-46DA8DCFF8AF
    Apr 8 22:42:56 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)(Error) IndexCI in copyFileOrFd:error (22) opening 0.indexGroups
    Apr 8 22:42:56 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)(Error) IndexCI in recoverIndex:Unrecoverable error: could not recover groups file (0.)
    Apr 8 22:42:56 wslyMac mds[33]: (/Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A -AE37-350EFD1764B1)(Error) IndexCI in CIMetaInfoCreate:Tried to create index when index already existed /Volumes/TimeMachine_Backup/.Spotlight-V100/Store-V1/Stores/DE7D5030-E962-480A- AE37-350EFD1764B1
    Apr 8 22:50:21 localhost kernel[0]: npvhash=4095
    Apr 8 22:50:17 localhost com.apple.launchctl.System[2]: fsck_hfs: Volume is journaled. No checking performed.
    Apr 8 22:50:17 localhost com.apple.launchctl.System[2]: fsck_hfs: Use the -f option to force checking.
    Apr 8 22:50:21 localhost com.apple.launchctl.System[2]: launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
    Apr 8 22:50:21 localhost com.apple.launchd[1] (com.apple.blued): Unknown key for boolean: EnableTransactions
    Apr 8 22:50:21 localhost com.apple.launchd[1] (org.cups.cupsd): Unknown key: SHAuthorizationRight
    Apr 8 22:50:21 localhost com.apple.launchd[1] (org.ntp.ntpd): Unknown key: SHAuthorizationRight
    Apr 8 22:50:21 localhost DirectoryService[11]: Launched version 5.6 (v514.24)
    Apr 8 22:50:27 localhost kernel[0]: hi mem tramps at 0xffe00000
    Apr 8 22:50:22 localhost DirectoryService[11]: Improper shutdown detected
    Apr 8 22:50:27 localhost kernel[0]: PAE enabled
    Apr 8 22:50:27 localhost kernel[0]: 64 bit mode enabled
    Apr 8 22:50:27 localhost kernel[0]: Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386
    Apr 8 22:50:27 localhost kernel[0]: standard timeslicing quantum is 10000 us
    Apr 8 22:50:27 localhost kernel[0]: vmpagebootstrap: 511374 free pages and 12914 wired pages
    Apr 8 22:50:27 localhost kernel[0]: migtable_maxdispl = 79
    Apr 8 22:50:22 localhost kextd[10]: 417 cached, 0 uncached personalities to catalog
    Apr 8 22:50:27 localhost kernel[0]: 101 prelinked modules
    Apr 8 22:50:27 localhost kernel[0]: AppleACPICPU: ProcessorApicId=0 LocalApicId=0 Enabled
    Apr 8 22:50:27 localhost kernel[0]: AppleACPICPU: ProcessorApicId=1 LocalApicId=1 Enabled
    Apr 8 22:50:27 localhost kernel[0]: Loading security extension com.apple.security.TMSafetyNet
    Apr 8 22:50:27 localhost kernel[0]: calling mpopolicyinit for TMSafetyNet
    Apr 8 22:50:27 localhost kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)
    Apr 8 22:50:27 localhost kernel[0]: Loading security extension com.apple.nke.applicationfirewall
    Apr 8 22:50:27 localhost kernel[0]: Loading security extension com.apple.security.seatbelt
    Apr 8 22:50:27 localhost kernel[0]: calling mpopolicyinit for mb
    Apr 8 22:50:27 localhost kernel[0]: Seatbelt MACF policy initialized
    Apr 8 22:50:27 localhost kernel[0]: Security policy loaded: Seatbelt Policy (mb)
    Apr 8 22:50:27 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
    Apr 8 22:50:27 localhost kernel[0]: The Regents of the University of California. All rights reserved.
    Apr 8 22:50:27 localhost kernel[0]: MAC Framework successfully initialized
    Apr 8 22:50:27 localhost kernel[0]: using 10485 buffer headers and 4096 cluster IO buffer headers
    Apr 8 22:50:27 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
    Apr 8 22:50:27 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
    Apr 8 22:50:27 localhost kernel[0]: mbinit: done
    Apr 8 22:50:27 localhost kernel[0]: Security auditing service present
    Apr 8 22:50:27 localhost kernel[0]: BSM auditing present
    Apr 8 22:50:27 localhost kernel[0]: rooting via boot-uuid from /chosen: 402D8D77-0836-3192-8A63-554D726141DC
    Apr 8 22:50:27 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
    Apr 8 22:50:27 localhost kernel[0]: FireWire (OHCI) TI ID 8025 built-in now active, GUID 001e52fffe3817fa; max speed s800.
    Apr 8 22:50:27 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0/AppleACPIPCI/SATA@1F,2/AppleICH8AHCI/PR T0@0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageD river/FUJITSU MHY2120BH Media/IOGUIDPartitionScheme/Customer@2
    Apr 8 22:50:27 localhost kernel[0]: BSD root: disk0s2, major 14, minor 2
    Apr 8 22:50:27 localhost kernel[0]: jnl: unknown-dev: replay_journal: from: 15129600 to: 2979328 (joffset 0x7d01000)
    Apr 8 22:50:27 localhost kernel[0]: [Bluetooth::CSRHIDTransition] switchToHCIMode (legacy)
    Apr 8 22:50:27 localhost kernel[0]: [Bluetooth::CSRHIDTransition] transition complete.
    Apr 8 22:50:27 localhost kernel[0]: [HCIController][configurePM] power parent ready after 1 tries
    Apr 8 22:50:27 localhost kernel[0]: AppleIntelCPUPowerManagement: initialization complete
    Apr 8 22:50:27 localhost kernel[0]: jnl: unknown-dev: journal replay done.
    Apr 8 22:50:27 localhost kernel[0]: HFS: Removed 4 orphaned unlinked files or directories
    Apr 8 22:50:27 localhost kernel[0]: Jettisoning kernel linker.
    Apr 8 22:50:27 localhost kernel[0]: Resetting IOCatalogue.
    Apr 8 22:50:27 localhost kernel[0]: GFX0: family specific matching fails
    Apr 8 22:50:27 localhost kernel[0]: Matching service count = 1
    Apr 8 22:50:27 localhost kernel[0]: Matching service count = 2
    Apr 8 22:50:27: --- last message repeated 4 times ---
    Apr 8 22:50:27 localhost kernel[0]: Previous Shutdown Cause: 5
    Apr 8 22:50:27 localhost kernel[0]: NVDANV50HAL loaded and registered.
    Apr 8 22:50:27 localhost kernel[0]: GFX0: family specific matching fails
    Apr 8 22:50:27 localhost kernel[0]: ath_attach: devid 0x24
    Apr 8 22:50:27 localhost kernel[0]: Override HT40 CTL Powers. EEPROM Version is 14.4, Device Type 5
    Apr 8 22:50:27 localhost kernel[0]: mac 12.10 phy 8.1 radio 12.0
    Apr 8 22:50:27 localhost kernel[0]: GFX0: family specific matching fails
    Apr 8 22:50:27: --- last message repeated 1 time ---
    Apr 8 22:50:27 localhost kernel[0]: Matching service count = 0
    Apr 8 22:50:27 localhost kernel[0]: yukon: Ethernet address 00:1b:63:b3:0d:6b
    Apr 8 22:50:27 localhost kernel[0]: AirPort_Athr5424ab: Ethernet address 00:1e:52:71:2c:52
    Apr 8 22:50:30 localhost mDNSResponder mDNSResponder-176.3 (Sep 30 2008 16:59:38)[16]: starting
    Apr 8 22:50:30 localhost fseventsd[38]: event logs in /.fseventsd out of sync with volume. destroying old logs. (3603 22 3778)
    Apr 8 22:50:30 localhost rpc.statd[30]: statd.notify - no notifications needed
    Apr 8 22:50:31 localhost kernel[0]: AirPort: Link Down on en1
    Apr 8 22:50:30 localhost /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[33]: Login Window Application Started -- Threaded auth
    Apr 8 22:50:30 localhost fseventsd[38]: log dir: /.fseventsd getting new uuid: B621E1D8-11D5-49D5-90F5-6E32BEDC8615
    Apr 8 22:50:30 localhost bootlog[45]: BOOT_TIME: 1239241808 0
    Apr 8 22:50:30 localhost blued[46]: Apple Bluetooth daemon started.
    Apr 8 22:50:31 wslyMac configd[14]: setting hostname to "wslyMac.local"
    Apr 8 22:50:33 wslyMac kernel[0]: AppleYukon2 - en0 link active, 100-Mbit, full duplex, symmetric flow control enabled port 0
    Apr 8 22:50:35 wslyMac org.ntp.ntpd[26]: Error : nodename nor servname provided, or not known
    Apr 8 22:50:35 wslyMac ntpdate[60]: can't find host time.apple.com
    Apr 8 22:50:35 wslyMac ntpdate[60]: no servers can be used, exiting
    Apr 8 22:50:39 wslyMac kernel[0]: IOHIDSystem: Seize of IOHIDPointing failed.
    Apr 8 22:50:39 wslyMac kernel[0]: IOHIDSystem: Seize of IOHIDEventDriver failed.
    Apr 8 22:50:39 wslyMac kextd[10]: writing kernel link data to /var/run/mach.sym
    Apr 8 22:50:43 wslyMac /usr/sbin/ocspd[75]: starting
    Apr 8 22:50:43 wslyMac com.apple.SystemStarter[28]: Starting HP IO Monitor
    Apr 8 22:50:43 wslyMac com.apple.SystemStarter[28]: Starting HP Trap Monitor
    Apr 8 22:50:43 wslyMac com.apple.SystemStarter[28]: /Library/StartupItems/HP Trap Monitor/HP Trap Monitor: line 15: /Library/Printers/hp/hpio/HPIO Trap Monitor.app/Contents/MacOS/HPIO Trap Monitor: No such file or directory
    Apr 8 22:50:46 wslyMac loginwindow[33]: Login Window Started Security Agent
    Apr 8 22:52:36 wslyMac authorizationhost[95]: MechanismInvoke 0x125de0 retainCount 2
    Apr 8 22:52:36 wslyMac SecurityAgent[96]: MechanismInvoke 0x101660 retainCount 1
    Apr 8 22:52:37 wslyMac SecurityAgent[96]: NSSecureTextFieldCell detected a field editor ((null)) that is not a NSTextView subclass designed to work with the cell. Ignoring...
    Apr 8 22:52:37 wslyMac loginwindow[33]: Login Window - Returned from Security Agent
    Apr 8 22:52:37 wslyMac SecurityAgent[96]: MechanismDestroy 0x101660 retainCount 1
    Apr 8 22:52:37 wslyMac authorizationhost[95]: MechanismDestroy 0x125de0 retainCount 2
    Apr 8 22:52:37 wslyMac loginwindow[33]: USER_PROCESS: 33 console
    Apr 8 22:52:37 wslyMac com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[91]): Exited: Terminated
    Apr 8 22:52:37 wslyMac com.apple.launchd[108] (com.apple.AirPortBaseStationAgent): Unknown key for boolean: EnableTransactions
    Apr 8 22:52:42 wslyMac Dock[118]: _DESCRegisterDockExtraClient failed 268435459
    Apr 8 22:52:44 wslyMac /System/Library/CoreServices/coreservicesd[56]: SFLSharePointsEntry::CreateDSRecord: dsCreateRecordAndOpen(wsly Hiroyuki Mompean Ueda's Public Folder) returned -14135
    Apr 8 22:53:02 wslyMac /System/Library/CoreServices/SystemUIServer.app/Contents/MacOS/SystemUIServer[1 24]: CPSGetProcessInfo(): This call is deprecated and should not be called anymore.
    Apr 8 22:53:02 wslyMac /System/Library/CoreServices/SystemUIServer.app/Contents/MacOS/SystemUIServer[1 24]: CPSPBGetProcessInfo(): This call is deprecated and should not be called anymore.
    Apr 8 22:54:42 wslyMac kernel[0]: AppleYukon2 - en0 link down
    Apr 8 22:54:46 wslyMac kernel[0]: AppleYukon2 - en0 link active, 100-Mbit, full duplex, symmetric flow control enabled port 0
    Apr 8 22:54:52 wslyMac kernel[0]: AppleYukon2 - en0 link down
    Apr 8 22:54:53 wslyMac kernel[0]: AppleYukon2 - en0 link active, 100-Mbit, full duplex, symmetric flow control enabled port 0

    I've had this problem with this computer as soon as I remember starting to use it.
    You should have taken it back to apple immediately.
    You need to try a clean install of the OS.. yosemite has known bugs especially with the wireless and if you upgrade installed the OS it can just get worse.
    You should do a clone of the hard disk and a Time Machine backup etc.. to make sure you don't lose files.. but a clean install will at least show if it is driver issue or actual faulty hardware. Is the laptop still in warranty / Applecare.. if so return it to apple for checking.

  • Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason: The handle is invalid.

    I'm stuck here trying to figure this error out.  
    2003 domain, 2012 hyper v core 3 nodes.  (I have two of these hyper V groups, hvclust2012 is the problem group, hvclust2008 is okay)
    In Failover Cluster Manager I see these errors, "Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason:  The handle is invalid."
    I restarted the host node that was listed in having the error then another node starts showing the errors.
    I tried to follow this site:  http://blog.subvertallmedia.com/2012/12/06/repairing-a-failover-cluster-in-windows-server-2012-live-migration-fails-dns-cluster-name-errors/
    Then this error shows up when doing the repair:  there was an error repairing the active directory object for 'Cluster Name'
    I looked at our domain controller and noticed I don't have access to local users and groups.  I can access our other hvclust2008 (both clusters are same version 2012).
    <image here>
    I came upon this thread:  http://social.technet.microsoft.com/Forums/en-US/85fc2ad5-b0c0-41f0-900e-df1db8625445/windows-2012-cluster-resource-name-fails-dns-registration-evt-1196?forum=winserverClustering
    Now, I'm stuck on adding a managed service account (mas).  I'm not sure if I'm way off track to fix this.  Any advice?  Thanks in advance!
    <image here>

    Thanks Elton,
    I restarted 3 hosts after applying the hotfix.  Then I did the steps below and got stuck on step 5.  That is when I get the error (image above).  There
    was an error repairing the active directory object for 'Cluster Name'.  For more data, see 'Information Details'.
    To reset the password on the affected name resource, perform the following steps:
    From Failover Cluster Manager, locate the name resource.
    Right-click on the resource, and click Properties.
    On the Policies tab, select If resource fails, do not restart, and then click OK.
    Right-click on the resource, click More Actions, and then click Simulate Failure.
    When the name resource shows "Failed," right-click on the resource, click More Actions, and then click Repair.
    After the name resource is online, right-click on the resource, and then click Properties.
    On the Policies tab, select If resource fails, attempt restart on current node, and then click OK.
    Thanks

  • Can I change which nic is used for a cluster network when more than one nic on the node is on same subnet?

    This cluster has been up and working for maybe a year and a half the way it is.  There are two nodes, running Server 2012.  In addition to a couple network interfaces devoted to VM traffic each node has:
    Management Interface: 192.168.1.0/24
    iSCSI Interface: 192.168.1.0/24
    Internal Cluster Interface: 192.168.99.0/24
    The iSCSI interfaces have to be on same subnet as management interfaces due to limitations in the shared storage.  Basically if I segregate it I wouldn't be able access the shared storage itself for any kind of management or maintenance tasks. 
    I have restricted the iSCSI traffic to only use the one interface on each cluster node but I noticed that one of the cluster networks is connecting the management interface on one cluster node member with the iSCSI interface on the other cluster node member. 
    I would like for the cluster network to be using the management interface on both cluster node members so as not to interfere with iSCSI traffic.  Can I change this?
    Binding order of interfaces is the same on both boxes but maybe I did that after I created the cluster, not sure. 

    Hi MnM Show,
    Tim is correct, if you are using ISCSI Storage and using the network to get to it, it is recommended that the iSCSI Storage fabric have a dedicated and isolated network. This
    network should be disabled for Cluster communications so that the network is dedicated to only storage related traffic.
    This prevents intra-cluster communication as well as CSV traffic from flowing over same network. During the creation of the Cluster, ISCSI traffic will be detected and the network
    will be disabled from Cluster use. This network should set to lowest in the binding order.
    The related article:
    Configuring Windows Failover Cluster Networks
    http://blogs.technet.com/b/askcore/archive/2014/02/20/configuring-windows-failover-cluster-networks.aspx
    I’m glad to be of help to you!
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Hi, My network went down earlier in the week.  Now it is fine, but my macbook airport no longer detects it and keeps asking for a WAP.  When I put the password in, it 'times out'.  I'm getting rather fed up.

    Hi, My network went down earlier in the week.  Now the network is fine, I can connect through the ethernet cable, but my macbook airport no longer detects it, when prompted, macbook will find it, but I get asked for the WAP.  When I put the password in, it 'times out'.  Prior to the network problem my macbook worked fine everytime. Anyone know the answer?

    My guess is all the issues are probably related and fall back to malware.
    AVG is probably correct in identifying malware. So I suggest you try some cleaning tools other than Emsisoft .
    ones I use (all of them one after the other until I find one that can cope) are;
    Roguekiller http://www.adlice.com/softwares/roguekiller/
    Malwarebytes anti malware Free http://www.malwarebytes.org/mwb-download/var2/confirm/
    ESET online scanner http://www.eset.com/int/home/products/online-scanner/
    So first create a clean boot in Windows using Microsoft's instructions https://support.microsoft.com/kb/929135?wa=wsignin1.0 and then run the anti malware applications.
    My outside looking in guess is that malware has set itself up as an internet proxy and is is downloading copies of itself and other malware, blocking some mail port as times as downloading more malware is more important, and probably breaking your tivo as well..
    Try the malware programs first. If that does not work I will try and talk you through some logging to see what is happening.

  • How to upload files in cluster without bringing down the cluster.

    Hi,
    Here is my problem:
    My weblogic portal 7.0 application should run in 24x7 environment. The production
    system is running in a cluster mode with external staging. Both the managed servers
    are pointing to the same application sync database.
    So to give a solution to this problem, we are trying to bring down one managed
    server down and apply the patches into that managed server without bringing down
    the other. Since webflow files and entitlements needs to be synchronized with
    the portal database. If we perform a sync on the portal database, there might
    be a chance that it might corrupt the existing portal database state. Our deployment
    would not be complete unless we perform a sync on the other managed servers. So
    we could not able to update the latest pathces into the cluster without bringing
    down the cluster.
    What I would like to know is "Is there any work around to get rid of this problem?".
    I would be delighted if any one provides the solution.
    Thanks & Regards,
    Ratnakar

    Hi Ratnakar,
    When you perform sync you do it against the admin server which in turn does it
    to the managed server. If you want to apply any changes to webflow you can do
    it on the live system itself. I mean apply the new webflow and entitlements and
    do the sync on the live system. Also while doing sync there are two modes. One
    mode will sync only the modified changes and the other will apply all of it. You
    can opt for the first option by which you can sync only the modified changes.
    This may bring a small disturbance but it will be unnoticed.
    The other option is to have two separate domains(each having one admin & one or
    more managed servers) which may be having two separate portal databases. In this
    way you can apply patches to one domain while other domain may provide the service.
    Regards
    Shaan
    "Ratnakar Sonti" <[email protected]> wrote:
    >
    Hi,
    Here is my problem:
    My weblogic portal 7.0 application should run in 24x7 environment. The
    production
    system is running in a cluster mode with external staging. Both the managed
    servers
    are pointing to the same application sync database.
    So to give a solution to this problem, we are trying to bring down one
    managed
    server down and apply the patches into that managed server without bringing
    down
    the other. Since webflow files and entitlements needs to be synchronized
    with
    the portal database. If we perform a sync on the portal database, there
    might
    be a chance that it might corrupt the existing portal database state.
    Our deployment
    would not be complete unless we perform a sync on the other managed servers.
    So
    we could not able to update the latest pathces into the cluster without
    bringing
    down the cluster.
    What I would like to know is "Is there any work around to get rid of
    this problem?".
    I would be delighted if any one provides the solution.
    Thanks & Regards,
    Ratnakar

  • SLP Directory Agent (port 427) - internal network goes down

    Due to some VPN problems with corporate headquarters, I had to switch out my current firewall (Instagate EX2) with a new SonicWall. Whenever we tried to switchover to the new SonicWall, my entire internal network went down. I was not able to login to the different Xserves for their appropriate services. Examples included the email server, FTP server, and a special application server we use for news editing. All Xserves run OS X Server 10.4. Our clients range from PowerMacs to Mac Minis and Mac Pros - all running OSX 10.4 with a few running 10.3. Symptoms of problems include when trying to connect to the email server, it just sits saying "Connecting to 10.1.2.x...", same thing for the FTP services. The newsroom software, that usually takes a 1 - 2 seconds to log into, then takes 45 seconds or so. Several techs looked at the problem without any suggestions about what to do to fix it.
    We have a Juniper Netscreen router provided by our ISP that connects to the Instagate firewall and to the network itself. Upon looking at the logs, it was discovered that the OS X stations IPs were using a port 427 - which is used by SLP. One of the techs said that is what is taking our network down when we disconnect the Instagate router from the network (because it evidently is passing this SLP traffic onto the Netscreen router). So when the Netscreen router comes off the network, none of the services on the Xserves work because of this. They said I needed to disable the port 427 on the Netscreen, but if I do this, isn't this having the same effect as taking the network down. Then it was told to me to setup a Directory Agent to handle this traffic. But they didn't provide any instructions to me on how to setup this up on the network or on OS X Server.
    Does anyone have any guidance or suggestions regarding this?
    Thanks,
    G

    I had the ISP's tech in today with proper network analysis software to see what's going on.
    We discovered that it is not SLP that is causing problems as one tech had suggested. Anytime that the internet access was disconnected from the network, the access to services on the OS X Servers go down or are extremely slow. So we began to look at the DNS entries and realized if we removed DNS then the servers refused access, if DNS entries were made (using OpenDNS), then the servers work.
    For example, we use the mail server component of OS X Server 10.4 for our email services. We cannot access the internal server (via IP) without the XServe having an entry in DNS. Put in OpenDNS servers, and things work like they should. The same scenario applies to any services (FTP, NewsEdit, etc.) that's on the OS X Servers. I guess what I'm not understanding is why does everything work internally as long as the OS X Servers have something listed for DNS - even though the DNS is an external DNS IP? Because it is external outside of the network, it's not like the mail server or clients are resolving the private IPs (which there's nothing to resolve since use IP numbers for connection purposes).

  • Captivate 4 won' start when network is down

    Captivate 4 won't start
    up when a network user logs on and the network is down AND the user's home drive points to a network location.
    i know Captivate must be looking for seom files on the network, but can anybody tell me what files they are and if there is a workaround, rather than log on as a local user?

    Since you WERE working over the nextwork on project files, Captivate is tracking where they were located so that it can populate the splash screen links or the Open Recent links in the File menu.
    When it can no longer reach these files...
    So it's still affected by the choice made to work other than locally.  Captivate 5 just degrades more gracefully.

  • Cluster Network name resource could not be updated in domain

    Hi,
    I have the following error and need clarification on the below solution in bold:
    Event Id 1206 -
    The computer object associated with the cluster network name resource 'Cluster Name' could not be updated in domain 'xxxxx.xxxx'. The error code was 'Password change'. The cluster identity 'ClusterGroup1$' may lack permissions required to update the object.
    1 - Move CNO back to the Computers Container
    2- Give the Cluster Node Computer Accounts Change Password permission on the CNO
    3 - Take the Cluster Name Resource offline
    4 - Repair Cluster Name Resource
    5 - Bring Cluster Name Resource back online
    Firstly, is there any implication?
    Secondly if ClusterGroup1$ is my CNO (Cluster Name Object) then is my
    cluster node computer account the server nodes in the cluster? E.g. ClusterGroup1$ is the cluster, the nodes are hyperv01 and hyperv02, do I add hyperv01 and hyperv02 to clustergroup1 -- properties -- security?
    Thank you.

    Hi SPD IT,
    If you have pre-stage your cluster object to a specific OU, you needn’t move them to default computer OU, with your current error information it most possible caused by the
    lack permission of cluster nodes or some unless GPO applied to cluster nodes, please exclude the cluster from any GPO, then test this issue.
    If it does not work please follow this repair action then monitor this issue:
    1. Open Failover Cluster manager
    2. Select Clustername
    3. Under Cluster Core Resources right click on Cluster Name and select Take offline
    4. Right click on Cluster Name and select repair.
    I’m glad to be of help to you!
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Server 2008 R2 Failover cluster network configuration

    Hi
    We have a customer with a Server 2008 R2 Hyper-V failover cluster. They have 2 cluster networks, "Cluster Network 1" and "Cluster Network 2".
    "Cluster Network 1": NIC team on 172.16.1.0/24 for private cluster network communication
    "Cluster Network 2": NIC team on 192.168.1.0/24 for production network communication
    I can see that "Cluster Network 1" is configured to "Allow cluster network communication on this network" and "Allow clients to connect through this network".
    If "Cluster Network 1" is ONLY for communication between the to cluster nodes then I assume the selection in "Allow clients to connect through this network" should be removed?
    /Lasse

    It will cause a lost network connection for any client that is accessing through that network.  Those clients would need to reconnect.
    Did you configure both IPs on the cluster resource name that clients are accessing?  If you only configured the one you want, there should be no issue.  If you configured both, then it is possible some clients might be connected via the private
    network.
    Another thing you should, and if you have already done this you will most likely not have issues at all, is that you should disable DNS registration on any network you do not want client access coming through.  If the clients can only find the resource
    through the DNS name registered, that is the way they will be coming in.  In my clusters, which often have 7 or more NICs, there is only one with a published DNS record.
    . : | : . : | : . tim

Maybe you are looking for