Error The Specified Network Name Is No Longer Available
Contents |
Español Nederlands 中文(简体) 日本語 Česky Polski Türkçe Português(BR) Español(LA) Resource error the specified network name is no longer available utorrent Pages Svenska עברית Sign In Go! Downloads Contact
The Specified Network Name Is No Longer Available Join Domain
Sales Sales Hotline: +49-800-100-0058 CET 8:00am – 6:00pm In EN Back Downloads Contact Sales
The Specified Network Name Is No Longer Available Windows 7
solutionsProductsHow to buyService ProvidersPartnersResourcesCompanySupport Business sizeEnterprise and Medium BusinessSmall BusinessVertical SegmentFederal Government (FED)State & Local Government/Education (SLED)CloudVeeam Cloud SolutionsDisaster Recovery-as-a-Service (DRaaS)Service
The Specified Network Name Is No Longer Available Sql Server
ProviderVirtualization PlatformMicrosoftVMwareStorage and ServerNetAppHPECiscoDell EMC All Success StoriesAvailability for the Always-On EnterpriseVeeam Availability PlatformVirtual Workloads (VMware and Hyper-V)Veeam Availability Suitev9Veeam Backup & Replication v9Veeam Availability ConsoleCloud and Physical WorkloadsVeeam Agent for Microsoft WindowsVeeam Agent for LinuxVeeam Availability ConsoleVeeam Backup for Microsoft Office 365Disaster Recovery the specified network name is no longer available server 2008 OrchestrationVeeam Availability OrchestratorSmall Business under 250 employeesVeeam Backup Essentialsv9Veeam vs. CompetitionCloud and Service ProvidersVCSP Program and Product OfferingsVeeam Availability ConsoleMonitoring and ManagementVeeam ONEv9Veeam Management Pack for System CenterFree ToolsVeeam Backup Free EditionVeeam Endpoint Backup FREEVeeam ONE Free EditionVeeam FastSCP for Microsoft AzureOther Free ToolsAll Veeam Products Success StoriesHow to buyRenewalsSpecial OffersFindaResellerFind a Veeam Cloud & Service ProviderContact SalesJoin the Veeam Cloud & Service Provider ProgramProgram OverviewThe DRaaS OpportunityLaunch a Managed Backup ServiceCloud & Service Provider DirectoryFind a Veeam Cloud & Service ProviderCloud & Service Provider Success StoriesAlready a VCSP?Log in to VCSP PortalVCSP EnablementHow to buy Become a PartnerService ProviderResellerDistributorAlliance PartnerProPartner Success StoriesAlready a Partner?Log in to ProPartner PortalProPartner UniversityDeal Registration Technical DocumentationResource LibraryVeeamBlogExecutive BlogFREE Online Education(Veeam University)Veeam Community ForumsVeeamLiveExpert WebinarsProduct DemosWhite PapersCompanyManagement TeamvExperts at VeeamMVPs at VeeamVeeam VanguardsCareersNews RoomAwardsEve
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about the specified network name is no longer available samba Stack Overflow the company Business Learn more about hiring developers or posting ads with the specified network name is no longer available server 2012 us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and the specified network name is no longer available apache network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Windows https://www.veeam.com/kb1735 share: The specified network name is no longer available up vote 5 down vote favorite 5 We've got an EMC NX4 SAN box serving a CIFS share to a number of Windows Server 2008 R2 app servers. The app servers are using the CIFS share to serve lots of image files (~2500 ops/sec on the share), however neither the SAN nor the app servers are showing any obvious signs of stress. Once http://serverfault.com/questions/205043/windows-share-the-specified-network-name-is-no-longer-available in a while an app server will, apparently all of a sudden, drop the connection to the SAN. Any .NET code trying to serve a file from the SAN fails with: System.IO.IOException: The specified network name is no longer available If I RDP to the app server and try to access "\san-name" through explorer, I get the same error. All other app servers can access it just fine. I can also access "\ip-of-san" just perfectly, pinging works as well. A reboot of the app server fixes the issue, but that's a somewhat drastic measure to the problem, given that it seems like the SAN is working fine and the computer can access it - it just looks like the "\san-name" access has barfed up. This has happened to two different app servers during the last week, so I don't suspect a single app server of being the cause. Ignoring the cause for now - how would I restore the "\san-name" connection without rebooting the machine? And can I somehow query what went wrong? Event logs shows nothing (besides related ASP.NET errors caused by the issue), neither on app servers nor on the SAN. Update: Based on the suggestions I'll try a restart of the Workstation service the next time and see
R2 for Windows Workstations→Troubleshooting Product Select Knowledge Base Installation / Uninstallation License / Activation Update Bases Settings / How to Rescue Disk http://support.kaspersky.com/us/5219 Remote Administration Reports / Notifications Troubleshooting Downloads & Info System http://www.tgrmn.com/web/forum/viewtopict4630.htm Requirements Common Articles How-to Videos Forum Contact Support Safety 101 Kaspersky Anti-Virus 6.0 R2 for Windows Workstations The specified network name is no longer available error occurs when locally accessing a shared folder by the the specified DNS name. What to do? Back to "Troubleshooting" 2012 Dec 26 ID: 5219 Applies to Kaspersky Anti-Virus 6.0 R2 for Windows Workstations v. 6.0.4.xDescription“The specified network name is no longer available” error occurs on a computer running Kaspersky Anti-Virus for Windows Workstations version 6.0.4.x when locally accessing a shared the specified network folder by the DNS name (\\host_name\folder_name).At the same time the folder can be accessed when addressed over the network or locally by IP address (\\host_IP_address\folder_name), by localhost (\\localhost\folder) or by the 127.0.0.1 IP address (\\127.0.0.1\folder).ReasonThis may be caused by a particular Anti-Hacker rule Windows "Server Message Block" Activity. When enabled, this rule blocks TCP connections on local port 445.SolutionOpen Kaspersky Anti-Virus and click the Settings button;Select Anti-Hacker in the left panel and click Settings in the Firewall section;Go to the Rules for packet filtering tab;Disable the Windows "Server Message Block" Activity (TCP) rule by unchecking its box in the Action column;Click OK > Apply.If this solution has not helped, please submit a request to the Technical support service. Was this information helpful? Yes No Back to "Troubleshooting" Kaspersky Anti-Virus 6.0 R2 for Windows Workstations Status: Limited SupportDatabase UpdateYesSupportYesError fixNo Latest Version: 6.0.4.1611 Commercial Release date:30 September 2009 Latest version release date: 30 March
1:38 pm Post subject: The specified network name is no longer available. I have a number of backup jobs that are working fine however with one server in particular, i keep getting the same error when it checks the source. The logs show these two errors: The specified network name is no longer available. followed by: Error scanning source folder. Funnily enough, it continually fails on the same set of folders. If i exclude them in the job, it skips these folders and the source checking works ok, and copies across the rest of the data. But i need to include these folders in the job too, so i need to work out why it is failing on these folders. Since it is the same folders that repeatedly cause these errors and others work fine, i'm ruling out anything hardware and/or OS based, along with network latency. I've also tried uninstalling the anti-virus software from the server too, but that had no effect. File permissions appear the same as the other folders that are working OK too. Oh also, network friendly folder scanning is turned on. So, any ideas what might be causing this? Thanks Back to top TGRMN SoftwareSite AdminJoined: 10 Jan 2005Posts: 7296 Posted: Fri Aug 29, 2014 4:34 am Post subject: Hi , what type of drive is the source folder? Is it Windows or MAC? thanks_________________-- TGRMN Software Support http://www.tgrmn.com http://www.compareandmerge.com Back to top raymarine1Joined: 20 Aug 2014Posts: 5 Posted: Fri Aug 29, 2014 6:48 am Post subject: Source and target are both Windows. Back to top TGRMN SoftwareSite AdminJoined: 10 Jan 2005Posts: 7296 Posted: Fri Aug 29, 2014 8:57 am Post subject: Thanks, if you point ViceVersa source or target to the specific subfolder that fails , does it still fail?_________________-- TGRMN Software Support http://www.tgrmn.com http: