"domain network" - name is forest parent domain

I'm testing Windows 7 in our corporate environment. How does the Windows 7 Network and Sharing center determine the name for the "Domain Network" to which I'm attached? I notice on my test PC it is showing the name of another domain in our forest (our tree root), not the name of the domain I am joined to. For example, each of our regions has their own domain:
region1.company.com
region2.company.com
region3.company.com
ad.company.com (tree root)
I'm in region1.company.com, however my N&S Center shows my connection as being in ad.company.com. My DHCP server is in region1.company.com. It is handing me a connection specific suffix of region1.company.com.
How does Windows 7 determine this name?
Baffling... and I've searched all over

Hi,
“ad.company.com” should be your Network Name. I think this is related to “Network Awareness”:
Windows 7: Pre-release privacy supplement (Please note the section “Network Awareness”.)
For more information about Network Awareness, please also refer to:
Network Awareness in Windows Vista and Windows 7
Thanks.
Nicholas Li - MSFT

Similar Messages

Error occured joining the domain. The specified network name is no longer available - Error during joining a machine to a domain

Hi!
We have two companies in our building, Company A and Company B. Company A has 50 client computers and one brand new DC (Win 2012 R2 Std). Company B has 5 clients and one established DC (Win 2008 R2 Foundation).
I work for Company A and I have the job of connecting all 50 clients to the new DC. Up until last week we had a workgroup set up and it has been my task to migrate our clients onto the domain. I have done 10 migrations of Win 7 machines so far, but three
others seem to be unable to connect with the error: The specified network name is no longer available.
I have connected these successfully to Company B Domain Controller successfully so this seems to point towards Company A DC being wrong somewhere, but doesn't make sense as to why 10 other clients have connected fine.
Here are the troubleshooting steps I have taken so far:
I am in the Domain Admin group on Company A Active Directory
Computer Browser Service is running on server and affected client
Workstation Service is running on server and affected client
Server Service is running on server and affected client
To connect to the domain I have tried using the NetBIOS and the FQDN, I get the same error message.
NETLOGON service is enabled tried restarting - no difference
Windows Firewall is off
No AV installed at the moment. I have Sophos waiting to go on once the machine is hooked onto the domain.
DNS Reverse lookup manually created as it wasn't there
Tried ipconfig /flushdns /release /renew
NSLookup sucessful, can ping NETBIOS, FQDN of server and both client and server IP both directions
Affectted clients are configured with one network card.
I've been pulling my hair out for a few days on this one. Anyone have a possible solution for this.
Many thanks,
Matt

Hi!
We have two companies in our building, Company A and Company B. Company A has 50 client computers and one brand new DC (Win 2012 R2 Std). Company B has 5 clients and one established DC (Win 2008 R2 Foundation).
I work for Company A and I have the job of connecting all 50 clients to the new DC. Up until last week we had a workgroup set up and it has been my task to migrate our clients onto the domain. I have done 10 migrations of Win 7 machines so far, but three others
seem to be unable to connect with the error: The specified network name is no longer available.
I have connected these successfully to Company B Domain Controller successfully so this seems to point towards Company A DC being wrong somewhere, but doesn't make sense as to why 10 other clients have connected fine.
Here are the troubleshooting steps I have taken so far:
I am the Domain Admin group on Company A Active Directory and have full Admin rights to Company B
Computer Browser Service is running on server and affected client
Workstation Service is running on server and affected client
Server Service is running on server and affected client
NETLOGON service is enabled tried restarting - no difference
IPv6 is enabled, but not used
DCDIAG tests all pass
NIC 2 has been disabled as it is not used
NIC 1 is first priority
To connect to the domain I have tried using the NetBIOS and the FQDN, I get the same error.
Windows Firewall is off
No AV installed at the moment. I have Sophos waiting to go on once the machine is hooked onto the domain.
DNS Reverse lookup manually created as it wasn't there
Tried ipconfig /flushdns /release /renew /registerdns
NSLookup sucessful, can ping NETBIOS, FQDN of server and both client and server IP both directions
Affected clients are configured with one network card.
*****Domain Controller*****
C:\>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : AG-ADDS
Primary Dns Suffix . . . . . . . : aggora.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : aggora.local
Ethernet adapter NIC1:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : F8-BC-12-3D-C7-6A
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::b499:7b3b:5ee7:618c%12(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.0.251(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.4
DHCPv6 IAID . . . . . . . . . . . : 318290962
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-3E-88-37-F8-BC-12-3D-C7-6A
DNS Servers . . . . . . . . . . . : ::1
10.0.0.251
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{F2A8A31C-01D2-4F6F-8CFF-A5AB69F344A8}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
*****Problematic Client*****
C:\>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : AG21
Primary Dns Suffix . . . . . . . : aggora.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : aggora.local
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : aggora.local
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 00-19-99-9B-90-5B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.0.0.115(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 23 July 2014 10:12:30
Lease Expires . . . . . . . . . . : 24 July 2014 10:12:30
Default Gateway . . . . . . . . . : 10.0.0.4
DHCP Server . . . . . . . . . . . : 10.0.0.253
DNS Servers . . . . . . . . . . . : 10.0.0.251
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.aggora.local:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : aggora.local
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
I'd be grateful for any assistance.
Many thanks,

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.

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

SQL Service Broker 2012: the connection was closed by the remote end, or an error occurred while receiving data: '64(The specified network name is no longer available.)'

Anyone can help with the below issue please? Much appreciated.
We have about 2k+ messages in sys.transmission_queue
Telnet to the ports 4022 is working fine.
Network connectivity has been ruled out.
The firewalls are OFF.
We also explicitly provided the permissions to the service account on Server A and Server B to the Service broker end points.
GRANT
CONNECT ON
ENDPOINT <broker> <domain\serviceaccount>
Currently for troubleshooting purposes, the DR node is also out of the Availability Group, which means that we right now have only one replica the server is now a traditional cluster.
Important thing to note is when a SQL Server service is restarted, all the messages in the sys.transmission queue is cleared immediately. After about 30-40 minutes, the errors are continued to be seen with the below
The
connection was
closed by the
remote end,
or an
error occurred while
receiving data:
'64(The specified network name is no longer available.)'

We were able to narrow down the issue to an irrelevant IP coming into play during the data transfer. We tried ssbdiagnose runtime and found this error:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>SSBDIAGNOSE -E RUNTIME -ID 54F03D35-1A94-48D2-8144-5A9D24B24520 Connect to -S <SourceServer> -d <SourceDB> Connect To -S <DestinationServer> -d <DestinationDB>
Microsoft SQL Server 11.0.2100.60
Service Broker Diagnostic Utility
An internal exception occurred: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
P 29830 Could not find the connection to the SQL Server that
corresponds to the routing address tcp://XX.XXX.XXX.199:4022. Ensure the tool is connected to this server to allow investigation of runtime events
The IP that corresponds to routing address is no where configured within the SSB. We are yet unsure why this IP is being referred despite not being configured anywhere. We identified that this IP belongs to one of nodes other SQL Server cluster, which has
no direct relation to the source server. We failed over that irrelevant SQL Server cluster and made another node active and to our surprise, the data from sys.transmission_queue started flowing. Even today we are able to reproduce the issue, if we bring
back this node [XX.XXX.XXX.199] as active. Since, its a high business activity period, we are not investigating further until we get an approved downtime to find the root cause of it.
When we get a approved downtime, we will bring the node [XX.XXX.XXX.199] as active and we will be running Network Monitor, Process Monitor and the SSB Diagnose all in parallel to capture the process/program that is accessing the irrelevant IP.
Once, we are able to nail down the root cause, I will share more information.

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.

Network Name not going online during Install

I have 2 servers connected to a Fibre SAN both running Server 2012 in a Failover Cluster. I have been trying to install the first of a Failover SQL 2012 Cluster. Everything installs properly until it gets to the final phase of the install and the Network
Name will not go online. I have removed and reinstalled many times with no success.
If I leave the install alone it will eventually go online however when that happens and I try to install the second node it gets to the Services part of the install and does not have one of the accounts in it. It is set as read only and I cannot change it
so I cannot continue the install.
Here is the log file I get after the initial install, I see nothing in it to point to the problem. I have tried manually creating the server in AD, in DNS etc.
Thanks!
Overall summary:
Final result:                  Failed: see details below
Exit code (Decimal):           -2068774911
Start time:                    2013-01-15 11:13:04
End time:                      2013-01-15 11:23:19
Requested action:              InstallFailoverCluster
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine:       Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for DQ:              Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText:        Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication:     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Cluster properties:
Machine name: ServerName
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
SQL Server 2012
Management Tools - Basic                 1033                 Standard Edition
11.1.3000.0     No
SQL Server 2012
Management Tools - Complete              1033                 Standard Edition     11.1.3000.0
No
Machine name: STVM5
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Machine Properties:
Machine name:                  ServerName
Machine processor count:       24
OS version:                    Future Windows Version
OS service pack:
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  Yes
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
SQL Server 2012
Management Tools - Basic                 1033                 Standard Edition
11.1.3000.0     No
SQL Server 2012
Management Tools - Complete              1033                 Standard Edition     11.1.3000.0
No
Package properties:
Description:                   Microsoft SQL Server 2012 Service Pack 1
ProductName:                   SQL Server 2012
Type:                          RTM
Version:                       11
SPLevel:                       0
Installation location:         L:\x64\setup\
Installation edition:          Enterprise
Product Update Status:
None discovered.
User Input Settings:
ACTION:                        InstallFailoverCluster
AGTDOMAINGROUP:                <empty>
AGTSVCACCOUNT:                 Domain\SQLClusterAgent
AGTSVCPASSWORD:                *****
ASBACKUPDIR:                   Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   Config
ASDATADIR:                     Data
ASLOGDIR:                      Log
ASPROVIDERMSOLAP:              1
ASSERVERMODE:                  MULTIDIMENSIONAL
ASSVCACCOUNT:                  <empty>
ASSVCPASSWORD:                 <empty>
ASSVCSTARTUPTYPE:              Automatic
ASSYSADMINACCOUNTS:            <empty>
ASTEMPDIR:                     Temp
COMMFABRICENCRYPTION:          0
COMMFABRICNETWORKLEVEL:        0
COMMFABRICPORT:                0
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130115_111217\ConfigurationFile.ini
ENU:                           true
ERRORREPORTING:                false
FAILOVERCLUSTERDISKS:          Cluster Disk 1
FAILOVERCLUSTERGROUP:          SQL Server (SQLCLUSTER)
FAILOVERCLUSTERIPADDRESSES:    IPv4;x.x.x.x;Cluster Network 1;x.x.x.x
FAILOVERCLUSTERNETWORKNAME:    ClusterName
FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SQLCLUSTER
FTSVCPASSWORD:                 <empty>
HELP:                          false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS:              false
INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR:             O:\
INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    SQLCLUSTER
INSTANCENAME:                  SQLCLUSTER
ISSVCACCOUNT:                  NT AUTHORITY\Network Service
ISSVCPASSWORD:                 <empty>
ISSVCSTARTUPTYPE:              Automatic
MATRIXCMBRICKCOMMPORT:         0
MATRIXCMSERVERNAME:            <empty>
MATRIXNAME:                    <empty>
PID:                           *****
QUIET:                         false
QUIETSIMPLE:                   false
RSINSTALLMODE:                 DefaultNativeMode
RSSHPINSTALLMODE:              DefaultSharePointMode
RSSVCACCOUNT:                  <empty>
RSSVCPASSWORD:                 <empty>
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  SQL
SQLBACKUPDIR:                  O:\MSSQL\Backup
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT:                 Domain\SQLClusterEngine
SQLSVCPASSWORD:                *****
SQLSYSADMINACCOUNTS:           Domain\user1, Domain\user2
SQLTEMPDBDIR:                  O:\MSSQL\TempData
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  O:\MSSQL\Data
SQLUSERDBLOGDIR:               <empty>
SQMREPORTING:                  false
UIMODE:                        Normal
UpdateEnabled:                 true
UpdateSource:                  MU
X86:                           false
Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130115_111217\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
Reason for failure:            An error occurred during the setup process of the feature.
Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name:                SQL Server Database Engine Services Instance Features
Component error code:          0x86D80058
Error description:             The cluster resource 'SQL Server (SQLCLUSTER)' could not be brought online due to an error bringing the dependency resource 'SQL Network Name (ST-SQLCluster)'
online. Refer to the Cluster Events in the Failover Cluster Manager for more information.
Error help link:
Feature:                       Data Quality Services
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name:                SQL Server Database Engine Services Instance Features
Component error code:          0x86D80058
Error description:             The cluster resource 'SQL Server (SQLCLUSTER)' could not be brought online due to an error bringing the dependency resource 'SQL Network Name (ST-SQLCluster)'
online. Refer to the Cluster Events in the Failover Cluster Manager for more information.
Error help link:
Feature:                       Full-Text and Semantic Extractions for Search
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name:                SQL Server Database Engine Services Instance Features
Component error code:          0x86D80058
Error description:             The cluster resource 'SQL Server (SQLCLUSTER)' could not be brought online due to an error bringing the dependency resource 'SQL Network Name (ST-SQLCluster)'
online. Refer to the Cluster Events in the Failover Cluster Manager for more information.
Error help link:
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name:                SQL Server Database Engine Services Instance Features
Component error code:          0x86D80058
Error description:             The cluster resource 'SQL Server (SQLCLUSTER)' could not be brought online due to an error bringing the dependency resource 'SQL Network Name (ST-SQLCluster)'
online. Refer to the Cluster Events in the Failover Cluster Manager for more information.
Error help link:
Feature:                       SQL Browser
Status:                        Passed
Feature:                       SQL Writer
Status:                        Passed
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130115_111217\SystemConfigurationCheck_Report.htm

Here are the results:
Warnings
Cluster Configuration
Validate Resource Status
   Validating cluster resource IP Address: 10.10.32.216.
    This resource does not have all the nodes of the cluster listed as Possible Owners. The clustered role that this resource is a member of will not be able to start on any node that is not listed as a Possible Owner.
   Validating cluster resource Name: ST-SQLCluster.
    This resource does not have all the nodes of the cluster listed as Possible Owners. The clustered role that this resource is a member of will not be able to start on any node that is not listed as a Possible Owner.
   Validating cluster resource SQL Server (SQLCLUSTER).
    This resource does not have all the nodes of the cluster listed as Possible Owners. The clustered role that this resource is a member of will not be able to start on any node that is not listed as a Possible Owner.
    This resource is configured to run in a separate monitor. By default, resources are configured to run in a shared monitor. This setting can be changed manually to keep it from affecting or being affected by other resources. It can also
be set automatically by the failover cluster. If a resource fails it will be restarted in a separate monitor to try to reduce the impact on other resources if it fails again. This value can be changed by opening the resource properties and selecting the 'Advanced
Policies' tab. There is a check-box 'run this resource in a separate Resource Monitor'.
Hyper-V Configuration
Validate Matching Processor Manufacturers
  Node Processor Manufacturer Version
  Server1.Domain.com AuthenticAMD AMD64 Family 16 Model 9 Stepping 1
  Server2.Domain.com AuthenticAMD AMD64 Family 16 Model 4 Stepping 2
  The processor version is not consistent across all the nodes. This is important because Hyper-V may not be able to live migrate a virtual machine between processors of different versions.
Network
Validate IP Configuration
  Verifying that there are no node adapters with the same MAC physical address.
   Found duplicate physical address D0-67-E5-F9-33-AA on node STVM4.SedonaTek.com adapter vEthernet (Inside Trunk) and node STVM4.SedonaTek.com adapter InsideTrunk - VLAN 100 - Management LAN.
System Configuration
Validate Software Update Levels
  KB Article Title Support Security Bulletins
  2770917 Update for Windows Server 2012 (KB2770917)
  Software Updates missing on 'Server2.SedonaTek.com':
  All software updates present
  The servers do not all have the same software updates.
I don't believe any of the actual warnings, those not related to the SQL install, will cause a problem.

WebDav using https fails with network name cannot be found.

When I attempt to connect to a Webdav server from a Windows 8.1 box it fails with
System Error 67 has occurred.
The network name cannot be found.
I am using the net.exe USE command with the following syntax:
net.exe use Z: https://dav.DomainYaya.com/ <PASSWORD> /user:USERNAME
This exact syntax works for Windows 7.
I have more than one Windows 8.1 box where this fails.
There are various suggestions found all over the internet for various other situations. They do not apply or do not work.
For example, you will find an issue involving sending Basic authentication over http where there are suggestions about changing HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WebClient\Parameters
That does not work. There is also discussion about the Webclient service. (it is running). One can find discussion of the redirector. (The SYS file is present and is installed with Windows 8+ anyway.)
Using HTTP only fails similarly but with error 53 (but I only did that as a test.) The issue is the HTTPS version.
I have BTW tried this with two different webdav servers.
Any help is appreciated.
Joe

Hi Joe,
Based on our research, the error 67 have the following several possable causes:
•IIS is not installed or is not running on the server that you are attempting to connect to.
•You have not installed the WebDAV Redirector on your client system.
•The WebClient service is not running on your client system.
•You have not enabled WebDAV on your web site.
•You are using Basic Authentication and connecting to your web site using HTTP instead of HTTPS.
•You are connecting to a web site on your local network that is using Fully-Qualified Domain Names (FQDNs) for name resolution, your web site uses Windows Authentication, and you have not added the web site's FQDN to the proxy server bypass list on your client.
For more information, please refer to the article as below:
Using the WebDAV Redirector
http://www.iis.net/learn/publish/using-webdav/using-the-webdav-redirector
According to the test, I am able to reproduce this issue in my lab. By default, the Webclient service is not running on windows 8.1 client. But for windows 7 client this service is running by default.
So please try to start the WebClient service on windows 8.1 client to check if it helps.
If you have any question, please don't hesitate to let us know.
Karen Hu
TechNet Community Support

"The home folder could not be created because the network name cannot be found" error in AD users and computers

Our home folders are stored on a non-windows NAS device and with Windows XP and 2003 we've always got the above error when creating or modifying users home folders, even when the shares were al ready created and being used.
However this was never really a big issue as the error that popped up was really for information and finshed with a "we've modified the user properties anyway, please create the share manually" type message.
Unfortunately now we are moving to windows 7 and 2008R2, this last part of the the message is missing and it won't accept the correct value.
This issue may be in the way that the NAS device shares the folder, as only the username that matches the folder name can access the share. This behaviour can't be modified.
Is there a way to get Windows 7/2008R2 AD users and computers to behave the same way that Windows XP/2003 does , i.e. don't try and create the share just set the value in the user properties ?
The AD is still at 2003 level and we can still use Windows XP/2003 clients to make the changes but this is a bit of a limitation.

The KB article is almost what we have apart from theitalic underlined
part
Consider the following scenario:
You use a domain administrator account to log on to a computer that is running Windows 7 or Windows Server 2008 R2.
You use the Active Directory Users and Computers Microsoft Management Console (MMC) snap-in to connect to a domain controller.
You open the Properties dialog box of a user account.
The user account has sole access to a shared folder path that cannot be accessed by the administrator account.
You set the Remote Desktop Services Home Folderattribute to the shared folder path.
NoteThis attribute is located on the
Remote Desktop Services Profiletab.
You click Apply or OK.
In this scenario, you receive the following error message:
The home folder could not be created because: The network name cannot be found.
Note If you click Apply or OK again, no error message is returned. However, the setting is not saved.
I think the important bit is
The user account has sole access to a shared folder path that cannot be accessed by the administrator account.
We manually create the shares on our NAS and then just want to enter the path in the profile tab, I suppose the question is how to we stop it trying to create the shares ?

How do i get a network name? HOSTNAME=... doesn't work anymore

Hi,
I'm sure this question sounds very n00by, but this used to be working just fine in archlinux by setting the hostname variable and that was the network name as well. No issue and worked like a charme. However, i reinstalled my system and i got the (unpleasant) surprise of a lot of changes.
So, what's the "new" equivalent of HOSTNAME="pc-name" so that it works on the network again? I'm using just the default stock network stuff but with a static ip, no special things.
Right now i do have my hostname set in rc.conf but i can't ping my machine by that name. No, nothing in the local network changed. It really is only a reinstall of a local machine.
Cheers,
Mark

2ManyDogs wrote:
Do you also have the hostname set in /etc/hostname and /etc/hosts?
ArchWiki wrote:
A host name is a unique name created to identify a machine on a network. With Arch Linux, a machine's host name is set in /etc/hostname or until a restart using the hostname command. Host names are restricted to alphanumeric characters. The hyphen (-) can be used, but a host name cannot start or end with it. Length is restricted to 63 characters.
Simply put your host name in to /etc/hostname (archlinux is the host name in this example):
archlinux
After setting a host name, it is also important to include the same host name in /etc/hosts. This will help processes that refer to the computer by its host name to find its IP address, as well as programs that rely on the gethostname() system call to determine the system's host name.
Edit /etc/hosts and add the same HOSTNAME you entered in /etc/hostname:
127.0.0.1 archlinux.domain.org localhost.localdomain localhost archlinux
And do you have a nameserver in /etc/resolv.conf?
If none of this works, can you try using dhcp in your rc.conf just to make sure it's a config problem?
https://wiki.archlinux.org/index.php/HO … e_hostname
Hi,
I tried your suggestions and using dhcp it works partly.
This is my static config:
interface=eth0
address=192.168.1.99
netmask=255.255.255.0
broadcast=192.168.1.255
gateway=192.168.1.2
When i use dhcp (so comment out the lines except interface=eth0) then i do get the name assigned, but i can't ping the pc or access it by name. I can by ip.
If you have more suggestions, please do share
Cheers,
Mark

Can't bring Network Name on line

Can't bring Network Name on line
Cannot cannect to configuration database error was shown when trying to access site.
Checking I found Suddenly clustering isn't function. When I look at the dependency report, the Network Name is
offline but its IP address is online and pingable.
The event viewer shows several of the following:
==============
Event ID: 1205; The Cluster service failed to bring clustered service or
application 'Cluster Group' completely online or offline. One or more
resources may be in a failed state. This may impact the availability of the
clustered service or application.
==================
Event ID: 1069; Cluster resource 'Cluster Name' in clustered service or
application 'Cluster Group' failed.
==================
Event ID: 1207; Cluster network name resource 'printserver' cannot be
brought online. The computer object associated with the resource could not be
updated in domain 'domainname.com' for the following reason:
Unable to obtain the Primary Cluster Name Identity token.
The text for the associated error code is: An attempt has been made to
operate on an impersonation token by a thread that is not currently
impersonating a client.
The cluster identity 'SPSERVERCLUS$' may lack permissions required to
update the object. Please work with your domain administrator to ensure that
the cluster identity can update computer objects in the domain.
==========
Event ID: 1205; The Cluster service failed to bring clustered service or
application 'Cluster Group' completely online or offline. One or more
resources may be in a failed state. This may impact the availability of the
clustered service or application.
Environment: Windows SQL Server 2008 R2.
Did any updates created and issue?
Checked DNS name is mapped to correct IP address.
AD has no expired credentials.
Surprisingly when turned 1 DB OFF, we can connect to site but still this error persist.
I've been googling this for a while, but haven't found a solution.
Please recommend the appropriate forum for this.I'd
appreciate any ideas. Thanks.
Thanks and Regards, Parth
Thanks and Regards, Parth

Hi, Actually we tried fixing many different ways but the thing which worked was Built-in recovery Processes. Computer object that represents the CNO was deleted, you will no longer be able to create the computer objects associated with cluster CAPs.
First, you must engage a Domain Administrator to recover the deleted computer object from the DeletedObjects container in Active Directory. Then, after the object has been restored and re-enabled, you execute the Repair Active Directory Object process in
the Failover Cluster Management snap-in.
there was a possibility that the cluster configuration file located in the %systemroot%\cluster subdirectory would become corrupted and then have to be replaced. In Failover Clusters, the self-healing capability can help. If the cluster service starts on
a node and the configuration database is corrupted, a minimal configuration template will be loaded using information contained in the HKLM\System\CCS\Services\ClusSvc\Parameters registry key. The node will attempt to join an already formed cluster and, if
this attempt is successful, a fresh copy of the cluster registry hive will be pushed to the node. If a node cannot join a cluster, the cluster service will be terminated.
Hope that can be helpful!
Thanks and Regards, Parth

FailSafe - Intelligent Agent - Network Name

Here's the ordeal.
A client has a windows 2000 cluster (gak). I set up Oracle FailSafe 3.3.1 and for several months it has worked fine. THey had a poweroutage the other day and the UPS battery was running low. They shut the servers down without taking the group offline (dough). When the first box went down a failover occured. Then the second was shutdown. Upon restarting they did not realize the database was set to not failback automatically. Then it is unclear what occured as panic set in. Now I have repaired most of the damage and the group is back ionline with the two datbaase and listener functioning properly. Howwever the Agent has failed to be restored because the Network Name resource fails to come online. Windows provides little info on why.
For a brief time I was able to get the Network Name to come online by removing it an recreating it with the Microsoft Cluster Administrator. With the fully qulified name and domain machinename.foobar.local. Then the intelligent agent was added and everything came on line. Meanwhile, back at the OEM management server, it was restarted and an atemmpt was made to refresh the node. WANK! WOn't refresh the node. An error says that there is a conflict between the Intelligent Agent version and the OEM Management server....both however are found to be 2.2 (I suspect though the agent was reinstalled on the cluster but I have not confirmed. Here come the questions:
Why does now the Network Name fail to come online? (tried everything now excpet rebooting the entire shooting match.)
Verifying the INtelligent Agent version?
Anythoughts on troubleshooting the agent would be appreciated before I rebuild the whole freakin' mess....
Brad

Tks for your reply
For this moment i've deployed one agent agent OFF on each node .This part of configuration is ok ,
i can monitor database from grid control.
the goal is configuring agent for failsafe now and integrate agent OFS to ressource . ,
I've got an error while step 'add ressource to group ' ( refer to NOTE:396659.1 paragraf 11)
The added ressouce ( grid agent) hang online pending on the screen of failsafe manager.
In the note it's notified to add Network name ,and IP address as dependencies, but i can find only Virtual IP adress in the scrolling box.
any idea ??

How to connect old aiport express to my new Airport Extreme? My Ipad says "base station e5713b cannot be configured" and my AirPort tool on my PC will not permit me to add my new Airport Extreme network (no network names to choose from)

How to connect old aiport express to my new Airport Extreme?
I have a PC running with Win7 and just replaced my Jensen With a brand New Airport Extreme.
I have set up the Airport Extreme to the internet, Iphones and Ipads and it work as it should.
I have downloaded latest Version of Airport tool on my PC. In addition i have downloaded the airport tool for Ipad.
I have reset one of my airport Express and it now shows up both on the Ipad and on the PC airport tool.
My Ipad says "base station e5713b cannot be configured."
I have wired the airport Express to my Ethernet to be able to "see it" on my Airport tool.
My AirPort tool on the PC will not permit me to add the airport Express to my new Airport Extreme network (no network names on the drop-down list to choose from). I wished for an easy set-up, but nothing seems to be plug and play as the Commercial says.. can you please help me?
Sigve

Hi
Thanks for Swift reply.
Yep - I in fact have two A1088 and one A1264
I actually bought the new router because the Jensen
router always lost connection to the Airport Express after some hours or days. I
always needed to restart my Jensen to play music and that was driving my wife
mad. The hope was that the Extreme should fix this. Both A1088 have been set up
to only stream music to two of my stereo amplifiers from my PC’s Itunes library.
Are the A1088 now useless?
The A1264 has been set up to feed internet into a Denon Reciever that needed Ethernet cable.
Please advise
Regards
Sigve

Help with new Airport Extreme (and network name) not recognizing Time Capsule and other Airports in the home

I had a Time Capsule running in an AV Cabinet and it made too much noise as it backed up and ruined soft/quiet music passages (and created far too much warmth as well). So, I visited the local Apple store and the guy I met worked through a few solutions with me. I decided on an Airport Extreme for the audio cabinet, and would move the Time Capsule to another room where it would not create noise interference.
So, I have the Airport up and running perfectly well. I changed my wireless network name and password.
I cannot get the Airport Express and Time Capsule to show up on my network. They both just blink that brown/orange color on the front. When I go to the Airport Utility, it does not pick up the Time Capsule or Airport Express. I have tried unplugging and plugging back in and scanning for devices, but dont know what else to do. Are they still looking for my old network? Is there a way to reset them??
Thanks for any help.

I've tried the option key on both--the AEBS offers 14 options, including Automatic, while the TC offers 8 options, and no Automatic. The AEBS lists (among others) 802.11 a/n-b/g compatible, 802.11 a-b/g compatible, or 802.11 n (5 GHz)-b/g compatible. The TC offers 802.11.n (b/g compatible), 802.11n only (2.4 GHz), and 802.11n only (5 GHz), among others...
I had already followed the instructions in the link you supplied, except that the wireless options don't quite match...
I am currently trying 802.11n (5GHz)-b/g compatible on the AEBS and 802.11 (5GHz) on the TC, which gives me a rate of 270 on my n devices and 54 on my g devices, according to the Airport Utility.
This might be the best I can do, without buying a new TC. Thanks for any advice you can give...
C.

My iphone will no longer connect to my home wifi. it recognises it, but the searching cirlce is constant next to network name. there are three laptops and another iphone on the same wifi that have no issues. i have reset network settings

my iphone will no longer connect to my home wifi. it recognises it, but the searching cirlce is constant next to network name. there are three laptops and another iphone on the same wifi that have no connectivity issues. i have reset the network settings but that did not help. the issue started last week when the second iphone was introduced to the house, could this be the cause?

No.
Any problem connecting your iPhone to any other wi-fi network besides your own?

"domain network" - name is forest parent domain

Similar Messages

Maybe you are looking for