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?

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,

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/).

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.

Error 64 - the specified network name is no longer available

I am with the problem how error 64 system error 64 - the specified network name is no longer available in my computers
My servidor is Windows server 2008 R2 and my computer is windows 7.
I tried
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters\size number (3) and not result.

Hi,
What operation did you perform before the issue came out? Please refer to the threads below to troubleshoot the issue:
Can't access UNC share on Windows Server 2012 R2
http://social.technet.microsoft.com/Forums/en-US/bca317cd-87aa-4fd7-b12a-6715e6dddfe5/cant-access-unc-share-on-windows-server-2012-r2?forum=winserver8gen
Regards,
Mandy
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.

A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)

Hi guys
i have problem when i run my windows application exe in windows server 2003
it give me this exception error :
I using sql server 2005
visual studio 2008
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Data.SqlClient.SqlException: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket()
at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
at System.Data.SqlClient.TdsParserStateObject.ReadByte()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)
at Sales.SalesClass.ShowSalesData(String ConnectionString)
at Sales.Form1.timer1_Tick(Object sender, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
Sales
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Documents%20and%20Settings/administrator.ALTAWIREADYMIX.000/Desktop/Sales.exe
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
System.Transactions
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
System.EnterpriseServices
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Why this error show and how to solve it
if possible help me
Why this exception show and how to solve it.
Notes this exception not close my application and not affect in result show but i don't know why it show

The problem can be caused by certain issues of long-running queries, which are reported improperly. Try increasing the timeout:
http://support.microsoft.com/en-us/kb/555938

64 The specified network name is no longer available

Hi Experts,
We have been using TMG 2010 from last 5 years as a reverse web proxy for OWA , outlook anywhere , active sync etc. Of late users from one particular site have been complaining of regular disconnections on outlook and OWA.
We don't have complaint from any other site except to this , whereas users in this site can browse other secure web sites without any challenge.
I have diagnosed the packets coming from their public IP and i could see that lot of connections happen successfully whereas few it shows either denied connection or failed connection attempt.
if i concentrate on failed connection attempt , i get the below information. Can some one provide any hint on the possible resolution for this issue.
Any help would be much appreciated
Failed Connection Attempt
3/19/2015 1:29:14 PM
<id id="L_LogPane_LogType">Log type:
</id><id id="L_LogPane_WebProxyForward">Web Proxy (Reverse)</id>
<id id="L_LogPane_Status">Status: </id>64 The specified network name is no longer available.
<id id="L_LogPane_Rule">Rule:
</id>Outlook anywhere success rule
<id id="L_LogPane_Source">Source:
</id>External (91.230.41.193:53933)
<id id="L_LogPane_Destination">Destination:
</id>Local Host
<id id="L_LogPane_FilterInfo">Filter information:
</id>Req ID: 19374dc2; Compression: client=No, server=No, compress rate=0% decompress rate=0% ; FBA cookie: exists=no, valid=no, updated=yes, logged off=no, client type=unknown, user activity=yes
<id id="L_LogPane_Protocol">Protocol:
</id>https
<id id="L_LogPane_User">User:
</id>anonymous
Md.Abubakar Noorani IT Systems Engineer Serco Ltd.

Hi,
>>64 The specified network name is no longer available
This error is very general. You need to collect a network trace and analyze it. The most common one is when the backend server is performing a dirty TCP connection reset.
You could have a look at the blog below.
Error 64 “ The specified network name is no longer available” while accessing a
HTTPS site through ISA 2006
Best Regards,
Joyce
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 Subscriber Support, contact [email protected]

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

Cannot copy file: The specified network name is no longer available

After several tries stretching over weeks or months, I finally solved this problem. Internet sharing and transferring small files worked fine over the wireless network, but files over about 50 - 100 MB would fail giving the message "Cannot copy : The specified network name is no longer available. After suggesting numerous changes to the router setup, telling me that my Ethernet NIC in my desktop must be bad, and that I my file sharing or memory configuration was wrong, Linksys support finally suggested upgrading the router's firmware. Problem solved. I can now transfer 1 GB files with no problem over the wireless network. This is on a WRT54GS wireless router.
Upgrading the firmware isn't a 5-minute operation. Allow 1-2 hours. Before you do anything, make a copy of all router setup info. The firmware upgrade resets the router to defaults, so you lose your wireless network setup and any other setup info that you changed. Also, customer support sent me a more involved procedure than what was in the router Help info. It included things like temporarily assigning a static IP address to the computer wired to the router for the update. You might want to get that procedure from them. Also, some of the info about reconfiguring the wireless network after the upgrade was incorrect for my network; another reason to make sure you have all the details of your router setup saved before you upgrade.

Hi! I'm Engr. Michael, a network engineer from the Philippines. Firmware upgrade does not take 1-2 hours believe me. Try this instead ok? The
version of your router is on CPN alert which means it needs upgrading. So, connect your pc
first directly to the modem and go to this website -- www.linksys.com/connect. select
easylink firmware tool and save it to your desktop. Now connect your the modem back to the
router (internet port) and pc to port number 1. Run the file you have downloaded and it will
automatically upgrade the firmware of your router.Then follow instructions and That's it. You're good to go..
Tell me if
it works ok? Thanks for your time.

"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

What to do about Backup failed with error: The target volume is read-only

This is a weird story. My wife has a PowerBook G4/1.33 GHz that she uses in clamshell mode with a 20" Cinema Display. One day under OS X 10.5.6, her Time Machine backups (to a networked 500 GB Time Capsule) failed with the error: Backup failed with error: The target volume is read-only. So I upgraded her to 10.5.7 and erased the sparseimage file, starting a new Time Machine backup. And it just happened again. Any idea how this sort of problem arises? My wife was doing something at her computer when the Time Machine error occurred.
Please don't advise us to upgrade to 10.5.8, because her PowerBook freezes not infrequently with any OS later than 10.5.6, and I was just about to downgrade her from 10.5.7 to 10.5.6.

Pondini wrote:
odysseus wrote:
This is a weird story. My wife has a PowerBook G4/1.33 GHz that she uses in clamshell mode with a 20" Cinema Display. One day under OS X 10.5.6, her Time Machine backups (to a networked 500 GB Time Capsule) failed with the error: Backup failed with error: The target volume is read-only. So I upgraded her to 10.5.7 and erased the sparseimage file, starting a new Time Machine backup. And it just happened again.
Try repairing the sparse bundle, per #A5 of the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.
I've tried this before, but it can't be repaired, because it can't be mounted.
Any idea how this sort of problem arises? My wife was doing something at her computer when the Time Machine error occurred.
One possibility is, the HD in the Time Capsule is beginning to fail (all HDs fail, sooner or later).
I'm backing up to my own sparseimage bundle just fine.
Please don't advise us to upgrade to 10.5.8, because her PowerBook freezes not infrequently with any OS later than 10.5.6, and I was just about to downgrade her from 10.5.7 to 10.5.6.
Those two things may be related. Whatever's going wrong may very well be what's corrupting the backups.
I'd recommend finding out what's wrong with the Powerbook. It's impossible to tell, of course, but that may be the root of the problem.
There's a problem with PowerBooks and Cinema Displays. I've posted a lot about this. Even after a motherboard replacement, my PowerBook G4/1.67 GHz had freezes, and eventually Apple gave me a MacBook Pro, but I think there's a failure involving hardware/software design.
If you haven't yet, I'd start by dong a +*Verify Disk+* on it's internal HD (also per #A5);
That checks out fine.
if there are no errors, or they're fixed and the problem continues, run the +Apple Hardware Test+ from the disc that came with the Mac. (One of the discs should have that, and instructions for running it, printed in tiny type on the label).
If still no help, I'd be inclined to do an +Archive & Install, preserving users & settings,+ of Leopard, then download & install the appropriate "combo" update. That's a combination (thus the clever name) of all the updates to Leopard since it was first released, so installing it should fix anything that's gone wrong since then, such as with one of the normal "point" updates. Info and download available at: http://support.apple.com/downloads/MacOS_X_10_5_8_ComboUpdate (change the last "8" to the desired number). Be sure to do a +Repair Permissions+ via Disk Utility (in your Applications/Utilities folder) afterwards.

Export Tasksequence fail with error "The filename, directory name, or volume label syntax is incorrect"

Hello
When I try to Export a Task Sequence I recive the following error in the Export Wizard
Error: The filename, Directory name, or volume Label Syntax is incorrect
Dos someone now this error or is ther a log with more Information? In the Log TaskSequenceProvider.log I dont find any error.
Andreas

Hi Jörgen
Thanks for the Answer, I have exported do the Root of
a Drive.<o:p></o:p>
Put I have found the Problem, a Application Package pointed
to a Source path that doesn’t exists any more<o:p></o:p>
Andreas

Order Import failing with error "The specified subinventory is invalid to use, the profile option INV: Allow Expense to Asset Transfer is set to No. Change the profile option to Yes or choose a valid subinventory."

Hi All,
I am getting this error while importing an internal sales order.
“The specified subinventory is invalid to use, the profile option INV: Allow Expense to Asset Transfer is set to No. Change the profile option to Yes or choose a valid subinventory.”
I have tried to set mentioned profile as ‘Yes’. But still getting same error.
Also, provided subinventory is present and active in given inventory organization.
Please share if anybody encountered this before and have a solution.

Hi 2878342
Please refer the following metalink note, it should resolve your problem.
Order Import Interface.Error Message Specified Subinventory Is Invalid To Use (Doc ID 406411.1)

Copying to TC drive results in "network name is no longer available" error

Hi --
We have a Western Digital MyBook hooked up to Time Capsule and are using it as shared storage. I can view the drive and copy down files with no problem. However, I am now having trouble copying large files (e.g. videos) to that connected drive. Small files are not a problem, but anything over a few hundred MB produces a "network name is no longer available" error on XP.
Note that copying files FROM the TC-connected drive to a local drive is no problem, even for large ones -- a 600MB file takes about 2 minutes over wireless. But if I try to copy that same file BACK to the TC drive, I get the error.
One strange thing I noticed is that when copying FROM the TC-connected drive, right away I get the usual dialog box showing copying progress. But when copying TO the TC-connected drive, the dialog only shows up after about 30 seconds. And the actual progress bar never moves -- it just spins for about 30 more seconds and then shows e.g. "Cannot copy Wonderboys: The specified network name is no longer available"
Any suggestions on how to debug this further?
Ramon

Hi --
We have a Western Digital MyBook hooked up to Time Capsule and are using it as shared storage. I can view the drive and copy down files with no problem. However, I am now having trouble copying large files (e.g. videos) to that connected drive. Small files are not a problem, but anything over a few hundred MB produces a "network name is no longer available" error on XP.
Note that copying files FROM the TC-connected drive to a local drive is no problem, even for large ones -- a 600MB file takes about 2 minutes over wireless. But if I try to copy that same file BACK to the TC drive, I get the error.
One strange thing I noticed is that when copying FROM the TC-connected drive, right away I get the usual dialog box showing copying progress. But when copying TO the TC-connected drive, the dialog only shows up after about 30 seconds. And the actual progress bar never moves -- it just spins for about 30 more seconds and then shows e.g. "Cannot copy Wonderboys: The specified network name is no longer available"
Any suggestions on how to debug this further?
Ramon

Backups failing with error 19: the backup disk could not be resolved, or there was a problem mounting it

Hello all,
Doubt this issue relates to a recent and ugly issue but sharing anyways (resolved thanks to a user here: LaPastenague)
Time Capsule won't backup if Modem (Motorola SB6121) attached
This was on Feb 10th resolved. Few days later I upgraded to Yosemite. Backups were working fine since.
Yesterday I happen to notice my last backup was 5 days ago. I looked in the console logs and saw:
2/25/15 3:55:06.127 PM com.apple.backupd[2777]: Attempting to mount network destination URL: afp://Paul;AUTH=SRP@Time%20Capsule._afpovertcp._tcp.local./Data
2/25/15 3:55:17.778 PM com.apple.backupd[2777]: NAConnectToServerSync failed with error: 2 (No such file or directory) for url: afp://Paul;AUTH=SRP@Time%20Capsule._afpovertcp._tcp.local./Data
2/25/15 3:55:17.792 PM com.apple.backupd[2777]: Backup failed with error 19: The backup disk could not be resolved, or there was a problem mounting it.
2/25/15 3:57:18.808 PM com.apple.prefs.backup.remoteservice[2021]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
I called Apple. Their front line was clueless. He suggested resetting the TC (latest "tower" model btw") which then a backup kicked off YEAH
But the next hour it failed
Called Apple again, this time to Sr Advisor. He suggested factory reset of the TC and set up again. Also first backup worked then rest failed
Third call to Apple useless also. He was asking questions I didn't feel relevant. He also was asking me to reset the TC which I told him was done 2 hours prior. He asked me to reboot which I could NOT at that time.
I begged him to collect data to submit to engineering, which will take days to get a reply.
So I thought I would throw this out to the community....
TC Is NEW (replaced from last issue). Mac is 8 months old (iMac 27"), Os is Yosemite, TC also new (latest model)
Thanks...

Yosemite is problematic on two fronts.. Networking and Time Machine.. so the combo of doing both with a Time Capsule is like bugs on bugs.
Here is my standard list.. but your problem maybe difficult to resolve.. and my suggestion is simple.. until Apple get their act together and fix TM.. buy Carbon Copy Cloner and use that for your backup. It is solid and reliable.. even better if you use USB drive plugged into the computer and do a bootable clone.. because then you have a backup that is able to be tested for full functionality 2min after the end of the backup.
This also starts from a factory reset.. but the reason for it is to change the configuration which is much more easily handled with factory reset to begin.. the instructions are there.. because this is my standard reply.. this is not uncommon!!
Factory reset universal
Power off the TC.. ie pull the power cord or power off at the wall.. wait 10sec.. hold in the reset button.. be gentle.. power on again still holding in reset.. and keep holding it in for another 10sec. You may need some help as it is hard to both hold in reset and apply power. It will show success by rapidly blinking the front led. Release the reset.. and wait a couple of min for the TC to reset and come back with factory settings. If the front LED doesn’t blink rapidly you missed it and simply try again. The reset is fairly fragile in these.. press it so you feel it just click and no more.. I have seen people bend the lever or even break it. I use a toothpick as tool.
N.B. None of your files on the hard disk of the TC are deleted.. this simply clears out the router settings of the TC.
Setup the TC again.
ie Start from a factory reset. No files are lost on the hard disk doing this.
Then redo the setup from the computer with Yosemite.
1. Use very short names.. NOT APPLE RECOMMENDED names. No spaces and pure alphanumerics.
eg TCgen5 and TCwifi for basestation and wireless respectively.
Even better if the issue is more wireless use TC24ghz and TC5ghz with fixed channels as this also seems to help stop the nonsense. But this can be tried in the second round.
2. Use all passwords that also comply but can be a bit longer. ie 8-20 characters mixed case and numbers.. no non-alphanumerics.
3. Ensure the TC always takes the same IP address.. you will need to do this on the main router using dhcp reservation.. or a bit more complex setup using static IP in the TC. But this is important.. having IP drift all over the place when Yosemite cannot remember its own name for 5 min after a reboot makes for poor networking. If the TC is main router it will not be an issue.
4. Check your share name on the computer is not changing.. make sure it also complies with the above.. short no spaces and pure alphanumeric.. but this change will mess up your TM backup.. so be prepared to do a new full backup. Sorry.. keep this one for second round if you want to avoid a new backup.
5. Mount the TC disk in the computer manually.
In Finder, Go, Connect to server from the top menu,
Type in SMB://192.168.0.254 (or whatever the TC ip is which you have now made static. As a router by default it is 10.0.1.1 and I encourage people to stick with that unless you know what you are doing).
You can use name.. SMB://TCgen5.local where you replace TCgen5 with your TC name.. local is the default domain of the TC and doesn't change.
However names are not so easy as IP address.. nor as reliable. At least not in Yosemite they aren't. The domain can also be an issue if you are not plugged or wireless directly to the TC.
6. Make sure IPv6 is set to link-local only in the computer. For example wireless open the network preferences, wireless and advanced / TCP/IP.. and fix the IPv6. to link-local only.
There is a lot more jiggery pokery you can try but the above is a good start.. if you find it still unreliable.. don't be surprised.
You might need to do some more work on the Mac itself. eg Reset the PRAM.. has helped some people. Clean install of the OS is also helpful if you upgrade installed.
Tell us how you go.
Someone posted a solution.. See this thread.
Macbook can't find Time Capsule anymore
Start from the bottom and work up.. What I list here is good network practice changes but I have avoided Yosemites bug heaven.
This user has had success and a few others as well.
RáNdÓm GéÉzÁ
Yosemite has serious DNS bug in the networking application.. here is the lets say more arcane method of fixing it by doing a network transplant from mavericks.
http://arstechnica.com/apple/2015/01/why-dns-in-os-x-10-10-is-broken-and-what-yo u-can-do-to-fix-it/

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

Similar Messages

Maybe you are looking for