The cluster network name is not online

Our cluster is a four node, Windows Server 2012 failover cluster running Hyper-V role only. Today it starts throwing the error 'The cluster network name is not online'. The IP is online (and all the VMs are running) but migrations fail and any
scripts that rely on the name fail. Attempting a More Actions | Repair results in 'The action 'Repair' did not complete. Error code 0x80005000'
The AD object for the cluster still exists. We do not have a disjoint namespace.
I am at a loss and hoping for some insight from the forum.
Thanks

Hi BlakeDuffey,
It seems like the computer object registry keys missing, please first try to runn gpupdate /force command on all nodes and repair again, if it not work please refer the following
article to repair the object registry key..
The related article:
Cluster network name resource 'Cluster Name' cannot be brought online, Unable to get Computer Object using GUID.
http://blogs.technet.com/b/csstwplatform/archive/2010/10/15/cluster-network-name-resource-cluster-name-cannot-be-brought-online-unable-to-get-computer-object-using-guid.aspx
Windows Server 2008 R2: Failover Clustering Troubleshooting Scenarios
https://technet.microsoft.com/en-us/magazine/hh289314.aspx
How to Troubleshoot Create Cluster failures in Windows Server 2012
http://blogs.msdn.com/b/clustering/archive/2012/05/07/10301709.aspx
http://blogs.technet.com/b/askcore/archive/2012/09/25/cno-blog-series-increasing-awareness-around-the-cluster-name-object-cno.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]

Similar Messages

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.

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 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

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.

Node failed to join the cluster because it ould not send and receive failure detection network messages

One of my customers has a Windows Server 2008 R2 cluster for an Exchange 2010 Mailbox Database Availability Group. Lately, they've been having problems with one of their nodes (the one node that is on a different subnet in a different datacenter) where
their Exchange databases aren't replicating. While looking into this issue it seems that the problem is the Network Manager isn't started because the cluster service is failing. Since the issue seems to be with the cluster service, and not Exchange,
I'm asking here.
When the cluster service starts, it appears to start working, but within a few minutes the following is logged in the system event log.
FailoverClustering
1572
Critical
Cluster Virtual Adapter
Node 'nodename' failed to join the cluster because it could not send and receive failure detection network messages with other cluster nodes. ...
It seems that the problem is with the 169.254 address on the cluster virtual adapter. An entry in the cluster.log file says: Aborting connection because NetFT route to node nodename on virtual IP 169.254.1.44:~3343~ has failed to come up.
In my experience, you never have to mess with the cluster virtual adapter. I'm not sure what happened here, but I doubt it has been modified. I need the cluster to communicate with its other nodes on our routed 10. network. I've never experienced
this before and found little in my searches on the subject. Any idea how I can fix this?
Thanks,
Joe
Joseph M. Durnal MCM: Exchange 2010 MCITP: Enterprise Messaging Administrator, Exchange 2010 MCITP: Enterprise Messaging Administrator, MCITP: Enterprise Administrator

Hi,
I suspected an issue with communication on UDP port 3343. Please confirm the set rules for port 3343 on all the nodes in firewall and enabled all connections for all the profiles
in firewall on all the nodes are opened, or confirm the connectivity of all the node.
Use ipconfig /flushdns to update all the node DNS register, then confirm the DNS in your DNS server entry is correct.
The similar issue article:
Exchange 2010 DAG - NetworkManager has not yet been initialized
https://blogs.technet.com/b/dblanch/archive/2012/03/05/exchange-2010-dag-networkmanager-has-not-yet-been-initialized.aspx?Redirected=true
Hope this helps.
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 error 1196

I have a two-node Hyper-V 2012 Core Server cluster. Initially, the cluster was working fine and I was able to do live migrations with no problem. I first realized that something had gone wrong when I was attempting to move a VM's storage to the Cluster Disk.
When I right click on the VM and select Move > Virtual Machine Storage, the bottom left area of the "move storage" screen says "Loading..." forever and never displays the cluster storage. This happened once before and I was able to correct
the issue by taking the Server Name resource offline and doing More Actions > Repair. However, if I try a repair now I receive the following error messages:
"There was an error repairing the active directory object for 'Cluster Name'. Error Code: 0x800713b8. The cluster request is not valid for this object".
I have verified that the cluster name Active Directory object (CCSDCluster) still exists and each node as well as itself has full permissions to the object. What I am not certain of is whether the object is still in the same Organizational Unit as it was
originally. After the failed repair attempt, I am able to bring the Server Name resource back online successfully.
In addition, I am continually receiving cluster event errors indicating the following:
"Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason: The handle is invalid. Ensure that the network adapters associated with dependent IP address resources are configured
with at least one accessible DNS server."
Each of the two nodes has multiple NICs configured. One for management, one for guest OSs (Hyper-V virtual switch is configured to use this NIC and not allow management OS access), and two for iSCSI (for redundancy and multi-path). Live migration is set
to only use the management NICs. The management NIC on both nodes is configured with valid DNS servers. The CCSDCluster DNS entry has full permissions for both nodes and itself.
Any suggestions on what to try would be greatly appreciated. Thank you!

Could my issues be related to a problematic network configuration? Please see the ipconfig below from one of my Hyper-V host servers.
Ethernet adapter Ethernet 8 = iSCSI
Ethernet adapter Ethernet 6 = iSCSI
Ethernet adapter Ethernet 2 = Management interface
10.1.3.19 = Management IP address, 10.1.3.3 = IP address of Cluster Name Object
Tunnel adapter Local Area Connection *11 = ?? Not sure what this one is
Windows IP Configuration
Host Name . . . . . . . . . . . . : CCSDVM01
Primary Dns Suffix . . . . . . . : clairton.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : clairton.local
Ethernet adapter Ethernet 9:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC552SFP Dual Port 10GbE Server Adapter #4
Physical Address. . . . . . . . . : 28-92-4A-AF-46-34
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Ethernet 8:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC552SFP Dual Port 10GbE Server Adapter #3
Physical Address. . . . . . . . . : 28-92-4A-AF-61-68
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 172.16.1.12(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.16.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Ethernet 7:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC552SFP Dual Port 10GbE Server Adapter #2
Physical Address. . . . . . . . . : 28-92-4A-AF-61-6C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Ethernet 6:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC552SFP Dual Port 10GbE Server Adapter
Physical Address. . . . . . . . . : 28-92-4A-AF-46-30
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 172.16.1.11(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.16.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Ethernet 3:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #55
Physical Address. . . . . . . . . : E4-11-5B-B9-3A-9C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Ethernet 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #58
Physical Address. . . . . . . . . : E4-11-5B-B9-3A-A2
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.1.3.19(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 10.1.3.3(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.1.3.100
DNS Servers . . . . . . . . . . . : 10.1.3.10
10.1.3.39
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Local Area Connection* 11:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapter
Physical Address. . . . . . . . . : 02-AD-4B-6D-A9-FB
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 169.254.2.92(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled

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.

WinXP to Mac - The Specified Network Name is No Longer Available

Hello,
I cannot figure out, for the life of me, why our WinXP machine won't connect to our Mac.
Mac: Powerbook G4 running OS X 10.4.7, WIndows File Sharing is active and an account is selected which will use Windows sharing.
PC: Windows XP Home Edition, SP2. A file share is active.
We're both using wireless connections via a D-Link DI-624 router. Both the Mac and PC are on the same workgroup and have different machine names. Both are on the same subnet.
The Mac can connect to Windows XP share directories and printers without a problem. The Windows XP machine can browse to the Mac's web page when the Personal Web Sharing on the Mac is active. The XP machine can even ping the Mac's address with no packet losses.
However, when the XP machine tries to connect to the Mac (via Map Network Drive or from the command line) using \\machine\share, we get the following error: "The Specified Network Name is No Longer Available". The Mac's machine name shows up when we do a search for computers, but gives us that same error when we double click on it. Furthermore, the printer name does not show up in the printer list, although the Mac's machine name does.
Any ideas? Any more information needed?
Thanks a lot. This problem is driving me insane. :/
Scott

I finally figured it out! It had to do with the smb.conf file and a missing file. Here's what happened (for people with future problems like this):
o Looked at the log.smbd file (in /var/log/samba) and saw errors about not being able to convert from CP0. Searched online and found (from http://discussions.apple.com/thread.jspa?messageID=2490054&#2490054) that I needed to change 'dos charset = 0' to 'CP850'...
o In Terminal, did a 'sudo pico /etc/smb.conf' and changed the line "dos charset = 0" to "dos charset = CP850"
o Still didn't work, and found from the log.smbd file that the convert msg was gone, but was replaced with a "Failed to open /private/var/db/samba/secrets.tdb" msg.
o I saw that the directory (at the ..../samba level) didn't exist, so, from Terminal, I used sudo to create the /private/var/db/samba directory (sudo mkdir /private/var/db/samba), and did a 'sudo touch secrets.tdb' to create the file, then 'sudo chown root:wheel secrets.tdb' to assign the correct user/group.
Used 'sharepoints' program to create shares and voila! It works great now!
To share my printer, I'm using bonjour, which is a free printer/etc. sharing program from Apple for those with OS X 10.4 (Tiger) and WinXP/2000/2003 machines (http://www.apple.com/macosx/features/bonjour/).

RDS Gateway + Smart Card Error [ The specified user name does not exist.]

I have the following Windows Server 2008 R2 servers:
addsdc.contoso.com, AD DS Domain Controller for contoso.com
adcsca.contoso.com, AD CS Enterprise CA, CDPs/AIAs published externally.
fileserver.contoso.com, RDS Session Host for Administration enabled
rdsgateway.contoso.com, RDS Gateway enabled
tmgserver.contoso.com, 'Publishing' rdsgateway.contoso.com but with pass-through authentication
And the following Windows 7 PCs:
internalclient.contoso.com
externalclient.fabrikam.com
There's no trust between the domains, the external client is completely separate on the internet but the CA certificate for contoso.com has been installed in the trusted Root CA store. All servers have certificates for secure RDP.
I enrolled for a custom 'Smart Card Authentication' certificate with Client Authentication and Smart Card Logon EKUs from the CA, stored on my new Gemalto smart card using the Microsoft Base Smart Card CSP.
From internalclient.contoso.com, I can RDP to fileserver.contoso.com
using the smart card just fine with no certificate errors.
From externalclient.fabrikam.com, I can RDP to fileserver.contoso.com
via rdsgateway.contoso.com using a username and password just fine with no certificate errors.
From externalclient.fabrikam.com, I can RDP to fileserver.contoso.com
via rdsgateway.contoso.com using the smart card to authenticate to the gateway, and a username and password to authenticate to the end server, just fine.
BUT from when using a smart card to authenticate to the end server via the gateway, it fails with:
The specified user name does not exist. Verify the username and try logging in again. If the problem continues, contact your system administrator or technical support.
When I move the client into the internal network and try the connection again (still via the RDS Gateway), it works fine - the only thing I can think of is being outside the network and not being able to contact the AD DS DC for Kerberos is causing the issue
- but I'm pretty sure this is a supported scenario?
The smart card works fine internally, the subject of the certificate is the user's common name (John Smith) and the only SAN is
[email protected] which matches the UPN of the user account as it was auto-enrolled.
Does anyone have any ideas?

I had a similar issue where I am using a smart card through a Remote Desktop Gateway. I had to disable Network Level Authentication (NLA) on the destination Remote Desktop Server. If anyone has another way around this, I'd appreciate hearing it. I'd prefer
to use NLA.

BMR-SS backup fails with error "the specified network name is no longer available"

We are running DPM 2012 SP1 on a Windows Server 2008 R2 system, backing up a Windows Server 2012 system that is a DC. The agent version is 4.1.3417.0. Both the DPM server and the DC are physical systems - brand new HP Proliant 360's.
When creating the replicas for the 2012 server the first time, the backups work fine, and then for a day or so after that. After a couple of days, the BMR-SS backups fail with the error "the specified network name is no longer available".
I can watch the backup happening in the Windows Server Backup console on the protected server - the BMR backup goes up to 99% and then fails. BMR backups on all the other servers are working - we have a mix of Win2008R2 and Win2012.
Here is what I have tried:
I can connect to the UNC path on the backup server without a problem during and after the backup is happening.
Tried reinstalling the DPM agent.
Tried backing up directly from the protected server to another server's network share, which worked.
I can copy multiple gigabyte files directly from the protected server to the DPM file share without a problem (the same one that DPM uses for the replica)
Tried turning off the SCEP real-time protection during the backup.
Any help would be appreciated - thanks.
KW

llo Boudewijn
I followed Boudewijn's suggestion.
The Windows 2012R2 servers had no recovery partition in disk C. I created one (400MB) following http://support.microsoft.com/kb/2930294/en-us and
DPM system restore worked. But just once.
So this is not the solution to the problem......
Is no one else having issues with DPM bare metal protection of Windows 2012R2 servers?

"the specified network name is no longer available"

I have a weird situation. I am using both iMac and Dell laptop. I use AEBS a1s a bridge - AT & T installed a wireless router and one hard line, and I plug my AEBS on the hard line. Dell is connected to AT&T router (and then to AEBS through hard ethernet line) with 801g. I connect my iMac to AEBS with 801n. I also attach a USB printer and 500G external HDD to AEBS. I formatted HDD with FAT32.
In terms of iMac, everything is working fine; I can print, I can read (or play) the files in Airdisk, and I can write (or copy) the files on Airdisk. No problem.
Dell laptop is a problem. Good things: I can print to the USB printer plugged in AEBS. I can read/play files stored in Airdisk. BAD THINGS: Every time I try to copy a file(s) to the HDD plugged in Airdisk, this error message appears: "the specified network name is no longer available"
If I cannot see the Airdisk at all, or cannot print any documents to AEBS-connected printer, then I may believe the network problem. Well, I can print a paper, I can read/play files in the HDD, but I cannot copy a file to the HDD! The size is less than 400MB, so the size should not be a matter.
I called Apple Tech Support, and they have kept me waiting for 32 minutes (and counting - now is 5:50pm PST - 10 minutes to go!). I have searched Apple discussion, Google, whatever, in vain.
Please share any tips with me. My iMac is run by Leopard, and I have Win XP SP3 for my Dell; Airport Utility is 5.3.2.

I solved the problem in this way: i had the hard disk and the printer connected to a usb hub. I tried to directly connect the hard disk to my airport and everything was ok! Now I can copy files without any problem...
Hope to help someone else!

"The Specified Network name is no longer enough"

Hi,
We have our (Windows Server 2008 R2) file server in remote location. I have a Linux server in my location...and I am using Windows 7 Pro 64-Bit.
we have Firewall to Firewall(Both are Sonicwall) VPN enabled between remote site and our location.
I have a Samba Share in my Linux server. I mapped this share as "P"drive in my Windows 7 PC.
While I am copying files from "File server" to local "P" drive....{ I am using xcopy command to copy the files: xcopy "\\fileserver\criss\" "P:\criss\" /Y}..it copies for few seconds and then it says " The specified
network name is no longer enough". some times it copies for long time and then says the same error.
I was able to do this till last week...Some how suddenly its not working...I automated this using Task Scheduler...it worked for 2 months without any issues.
Everything works fine in my Windows XP PC. (Clearly it seems to be an issue with windows 7)
Please help me with this.

Kdhara wrote:
M able to copy the files from server to local C, and able to copy to
samba server.....However somehow, when I try to access the fileserver
using RUN command (Eg:\\fileserver <file://\\fileserver>) sometimes
it works fine and sometimes it wont connect and says "The Specified
Network name is no longer available"....I observerd the both ways
around 1-2 Hours ....
So you do not have the issue, that a filecopy operation aborts in the
middle of the operation as you said in your root-post, but that you
sometimes cannot access your W2008R2 server via UNC-path?
In this situation I'd first check, that you do not have any
offline-files defined for that server (- because you need to be
patient, if using this feature, as it takes awhile for this feature to
detect changes in connectivity).
Further as you are using Netbios name resolution and accessing a server
in another subnet do you have a valid WINS-server, which has an entry
for your W2008R2 server, configured on your Win7 PC - or do you have a
correct entry in the LMHOSTS file for your W2008R2 server?
But generally speaking it is quite normal for Netbios name resolution
to fail for quite some time if the Master Browser service in your
subnet changes due to a change of network topology like shutting down a
computer or starting up a computer, etc. . If you don't need the
browsing capabilities, which netbios delivers, it is much more reliable
and quicker to use DNS as name resolution for Windows networks, too.
Wolfgang

"The iPhone (iPhone name) could not be synced because the connection to the iPhone was reset".

This started yesterday at about 10:30am California time and hasn't stopped or been fixed. Whenever I sync or try to backup my iPhone 5 it goes through the process but right when it's about to finish backing up it gives me an error message that says "The iPhone (iPhone name) could not be synced because the connection to the iPhone was reset"
I have tried using a different USB cable, using a different port on my macbook, restarting both my phone and my computer. And nothing works and I have search through about every search engine and this problem isn't to be found anywhere online. Posting my problem and calling Apple support are my last options. Also I am still running on iOS 6.1.4 and have not updated to iOS7 because I want to be able to have an up-to-date backup file in case anything goes wrong. And I don't want to restore a backup because my last actual backup is from a couple months ago. But another thing I don't quite understand is that even though that message comes up, a couples minutes later my iPhone's summary says the last backup was the current time like it actually DID back it up. So my question is if the error message says that it can't be synced then why does it show that it actually did backup? Please help because I really would like to get rid of this problem so I could backup and sync to update to iOS7.

Try TS1389: iTunes repeatedly prompts to authorize computer to play iTunes Store purchases.
tt2

What's the reason for this message, "A server with the specified host name could not be found" ? I'm using iPhone 4s, 16gB, iOS 7.0.4

I get a pop-up message saying "A server with the specified host name could not be found", whenever I try to access any streaming websites/apps or even WhatApp over Wi-Fi and I cannot access the specific THING for that moment, and I've tried switching Wi-Fi On and Off both in my Phone and also in the Router. I got an internet connection and a Wi-Fi router just before two days, and it's happening since. I got the internet speed around 80kbps and i can easily stream YouTube videos except sometimes, I receive that annoying message. I can't even browse the internet in Safari, which says "No Internet Connection"(Even though the Wi-Fi is connected), and I can access it after somewhile (say 10 minutes, it'll be perfectly alright). I use iPhone 4s. And everything about the internet connection is totally fine in my Computer, but not in my iPhone, as I've explained the issues, above. If there are any technical settings that I should change/modify, either on my computer(Windows 7 OS) or in my iPhone(iOS 7.0.4), PLEASE let me know
I hope I've provided enough information for the reader to understand my point. (I apologize for my verbal mistakes, if there are )
THANKS

Hello Paneesh,
Thank you for the details of the issue you are experiencing with Wi-Fi on your iPhone 4s. I recommend the following steps:
Be sure you're in range of your Wi-Fi router (access point).
Tap Settings > Wi-Fi and turn Wi-Fi off and on. If your W-Fi setting is dimmed, follow these steps.
Confirm that your Wi-Fi router and cable or DSL modem are connected to power, turned on, and connected to the Internet. If not, refer to your network administrator or Internet service provider (ISP) for assistance.
Restart your iOS device.
Tap Settings > Wi-Fi and locate the Wi-Fi network to which you're connected.
Tap and Forget this Network.
Try to connect to your desired Wi-Fi network.
Note: You may need to enter your Wi-Fi password again if your network requires one.
Turn your Wi-Fi router off and on2. If your ISP also provides cable or phone service, check with them before attempting this step to avoid interruption of service.
Update your device to the latest version of software.
Update your Wi-Fi router to the latest firmware2. For AirPort Base Stations, install updates using the AirPort Utility.
If the issue is still unresolved Wi-Fi disconnects or signal strength is less than expected
Move closer to the Wi-Fi router (access point).
Check for sources of potential interference.
Remove any case, stand, or other accessories from your iOS device and see if signal strength improves.
Reset network settings by tapping Settings > General > Reset > Reset Network Settings. Note: This will reset all network settings including
previously connected Wi-Fi networks and passwords
recently used Bluetooth accessories
VPN and APN settings
You can find the full article here:
iOS: Troubleshooting Wi-Fi networks and connections
http://support.apple.com/kb/ts1398
Thank you for using Apple Support Communities.
Best,
Sheila M.

The cluster network name is not online

Similar Messages

Maybe you are looking for