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.

Similar Messages

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

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?

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

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

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.

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]

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.

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,

"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

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

Cannot copy files from my network using finder

If I try to copy files from my NAS or my PC to my Macmini running Leopard, I cannot copy files that are larger than 64kb. Otherwise I get an error message. Interestingly, if I use the cp command in the console instead, he can copy the file, but the file is corrupt in the sense that it is smaller than the original and not working. Weirdest thing is that I can access the same files from itunes or iphoto or vlc or whatever. Any ideas?

After the update I cannot connect to my router anymore
(see other threat)

Cannot Copy Files over a network

I've had a new hard drive installed in iMac by Apple, and Apple re-installed the OS, which is running 10.6.7 (all current software updates are installed). The iMac is part of a network connecting to a OS X Server 10.4.10
All of the Network Drives have been connected, the user can copy documents under 1MB to and from the server fine. However if we try to copy files over 1MB the first file will copy fine, but then no more files can be copied to the server from this machine, regardless of the size.
If i use another Mac, with the same user credentials I can copy files of any size without any issues. I have tried connecting to the Network using both the Ethernet port and Airport but I experience the same issue regardless.
If I reboot the iMac I can copy a file over 1MB again and then the symptoms re-present themselves. I have tried creating a users, new network drives, folders etc. I can connect using any user, to any of the new folders from any other machine on the network but not from this one.
When the copying fails Finder just hangs with
Copying "" to "ShareName" rather than having the name of the file, I believe this may be where the error lies.
I have also tried running the App Maintenance from Titanium Software, after running this i can copy files over the network fine, but after I have copied 10 or so files, the situation goes back to not copying files correctly.
Tags:

I have tried several files and also I have copied the files on to a USB Hard Drive and then onto another machine, that machine was able to copy the files over the network.
The Firewall is switched off on this Mac, I have tried various different options with the Firewall, Turning it off, ensuring the AFP connections are allowed.
Also using the Maintenance app, that I mentioned clears the Caches, repairs permissions etc etc

Cannot copy file, file is in use

Macbook pro 13 mid 2009 with Yosemite fresh install. (i have the same problem with the old MacOSX).
When i try to copy a file, or a bunch of files, to the wdtvlivehub i have the message error "cannot copy file, the file is in use".
I try the following:
- in the wdtvlivehub activated the DNLA, WINDOWS and Itunes Server (and the linux).
- try both via wifi and ethernet
- repair permission on disk
- deactivate the show miniatures on the mac and on the wdtvlivehub
- drag & drop the file and cut e copy via keyboard or with the right click of the pad or mouse
- connect the wdtvlivehub via SMB, CIFS
- Try with AFP but i get a error message
- with an app i search for a program that block the file but it didn't find anything
-Basically i try everything suggest in this board and over the web but nothing resolve the problem.
The file sometimes been copied but i have to try a billion times....not so comfort in this.
What i have to do?
P.S. Sorry for my bad english.

Hi,
We often see this file in use when the file has not been closed. Is it just a regular file that was opened and how did you open it? I use AppleScript to close it if it was opened with AppleScript.
Edited: try this: Run Script Editor. Enter:
set f to choose file -- select the file
close access f
run it in Script Editor.
gl,
kel

WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network

The Exchange Management Shell fails to connect in Exchange 2013 environment, this is a DAG environment and previously it indicates another error message, which is in my another thread. We fixed that error by delete the retired proxy entry in the server registry,
after that the error is gone but changed to below one, anyway the EMS still fails to connect to all servers:
VERBOSE: Connecting to NSWVIP999WTMBX.air.abc.au.
New-PSSession : [NSWVIP999WTMBX.air.abc.au] Connecting to remote server NSWVIP999WTMBX.air.abc.au failed with the
following error message : WinRM cannot complete the operation. Verify that the specified computer name is valid, that
the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows
access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote
computers within the same local subnet. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : WinRMOperationTimeout,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:
Then it just show can't connect to all the exchange servers, from the wording it seems pointing to the Windows firewall settings for winRM, but when I look at the windows firewall found it's turned off. We use Sophos enterprise for the security, but all
other 3 exchange servers didn't have the same issue.

Hi Lynn,
Thanks for your analyst and reply, I run the command as you suggested and checked accordingly to Task Manager, but seems none of them indicates a firewall or anti-virus.
  TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       4
TCP    0.0.0.0:808            0.0.0.0:0              LISTENING       2260
TCP    172.17.2.123:444       172.16.2.127:8050      ESTABLISHED     4
TCP    172.17.2.123:444       172.16.2.127:8069      ESTABLISHED     4
TCP    172.17.2.123:444       172.17.2.127:8053      ESTABLISHED     4
TCP    172.17.2.123:10952     172.16.2.68:80         ESTABLISHED     3296
TCP    172.17.2.123:11185     172.16.2.90:8080       SYN_SENT        468
TCP    172.17.2.123:11190     172.16.2.90:8080       SYN_SENT        15268
TCP    172.17.2.123:11330     172.16.2.90:8080       SYN_SENT        1296
TCP    [::]:80                [::]:0                 LISTENING
4
TCP    [::]:808               [::]:0                 LISTENING
2260
TCP    [::1]:6001             [::1]:8028             ESTABLISHED     4764
TCP    [::1]:6001             [::1]:8029             ESTABLISHED     4764
TCP    [::1]:6001             [::1]:8030             ESTABLISHED     4764
TCP    [::1]:6001             [::1]:8031             ESTABLISHED     4764
TCP    [::1]:6001             [::1]:8032             ESTABLISHED     4764
TCP    [::1]:6001             [::1]:8033             ESTABLISHED     4764
TCP    [::1]:6001             [::1]:8034             ESTABLISHED     4764
TCP    [::1]:6001             [::1]:8035             ESTABLISHED     4764
TCP    [::1]:6001             [::1]:8036             ESTABLISHED     4764
TCP    [::1]:6001             [::1]:8037             ESTABLISHED     4764
TCP    [::1]:6001             [::1]:8040             ESTABLISHED     4764
TCP    [::1]:6001             [::1]:8041             ESTABLISHED     4764
TCP    [::1]:6001             [::1]:8048             ESTABLISHED     4764
TCP    [::1]:6001             [::1]:8049             ESTABLISHED     4764
TCP    [::1]:6001             [::1]:8059             ESTABLISHED     4764
TCP    [::1]:6001             [::1]:8060             ESTABLISHED     4764
TCP    [::1]:8028             [::1]:6001             ESTABLISHED     9980
TCP    [::1]:8029             [::1]:6001             ESTABLISHED     9980
TCP    [::1]:8030             [::1]:6001             ESTABLISHED     9980
TCP    [::1]:8031             [::1]:6001             ESTABLISHED     9980
TCP    [::1]:8032             [::1]:6001             ESTABLISHED     9980
TCP    [::1]:8033             [::1]:6001             ESTABLISHED     9980
TCP    [::1]:8034             [::1]:6001             ESTABLISHED     9980
TCP    [::1]:8035             [::1]:6001             ESTABLISHED     9980
TCP    [::1]:8036             [::1]:6001             ESTABLISHED     9980
TCP    [::1]:8037             [::1]:6001             ESTABLISHED     9980
TCP    [::1]:8040             [::1]:6001             ESTABLISHED     9980
TCP    [::1]:8041             [::1]:6001             ESTABLISHED     9980
TCP    [::1]:8048             [::1]:6001             ESTABLISHED     9980
TCP    [::1]:8049             [::1]:6001             ESTABLISHED     9980
TCP    [::1]:8059             [::1]:6001             ESTABLISHED     9980
TCP    [::1]:8060             [::1]:6001             ESTABLISHED     9980
TCP    [fe80::9054:e8f5:f885:8105%20]:808 [fe80::9054:e8f5:f885:8105%20]:9901
ESTABLISHED     2260
TCP    [fe80::9054:e8f5:f885:8105%20]:9901 [fe80::9054:e8f5:f885:8105%20]:808
ESTABLISHED     4868
This is the full result, among them
4 -- System -- NT Kernel & System
468 -- There is no process associated with PID 468
1296 -- svchost.exe -- Host Process for Windows Service
2260 -- SMSvcHost.exe -- SMSvcHost.exe
3296 -- CcmExec.exe -- CCM Executive
4764 -- Microsoft.Exchange.RpcClientAccess.Service.exe -- Microsoft.Exchange.RpcClientAccess.Service.exe
4868 -- Microsoft.Exchange.ServiceHost.exe -- Microsoft.Exchange.ServiceHost.exe
9980 -- w3wp.exe -- IIS Worker Process
15268 -- ServerManager.exe -- Server Manager

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

Similar Messages

Maybe you are looking for