Home > The Specified > The Specified Network Name Is No Longer Available 2008

The Specified Network Name Is No Longer Available 2008

Contents

How does a teleconvertor affect magnification ratio? Ignoring the cause for now - how would I restore the "\san-name" connection without rebooting the machine? What to do? Windows Tips & tools to fight viruses and vulnerabilities   Scan your PC for viruses & vulnerabilities Kaspersky Security Scan (Windows) Kaspersky Virus Scanner Pro (Mac) Kaspersky Threat Scan (Android) Decrypt http://smartnewsolutions.com/the-specified/the-specified-network-name-is-no-longer-available-windows-2008.html

For information about Symantec support for Endpoint Protection 11, visit the Symantec Support site. I would not be surprised if there were errors from Source: MrxSmb or Source: TCPIP Network Monitor doesn't bite... Symantec Endpoint Protection versions prior to 11.0.4202 (MR4-MP2). The registry key of HKLM\Software\Microsoft\ASP.NET\FCNMode can be 0, 1 or 2. 0 is the default which has a FCN object for every folder. https://support.microsoft.com/en-us/kb/961293

The Specified Network Name Is No Longer Available Server 2008 R2

Restarting the app fix the issue temporarily but facing the same error latter. I've never seen a drawback to that change. Subscribe for updates: Products Contacts License Management Company Products Resources Veeam University Partners Success Stories Contact Veeam sales Buy Veeam products Renewals License Management Support Technical Documentation Knowledge Base Copyright ©2017 I looked really hard and found this - Disable "Large Send Offload" ipv4 and ipv6 on the virtual network adapter.

psexec appears to authenticates properly.psexec runs the command on the remote host. Most of the users and devices were or have retired long ago. Why is trying to talk children out of how they feel a bad idea? The Specified Network Name Is No Longer Available Joining Domain Is the topologist's sine curve a manifold?

There is no change on database side that can resolve this issue. You've got hardware issues. Please note: If you are unable to upgrade promptly or remove the software, Symantec urges you to contact their technical support to determine if there are any workarounds available to you. Join Now Does anyone enjoy obscure issues?   In our environment we have two Server 2008 R2 servers- a bot server and a file server.  Basically, as our bot server performs

asked 6 years ago viewed 29242 times active 9 months ago Blog Say Farewell to Winter Bash 2016! The Specified Network Name Is No Longer Available Windows 10 windows-server-2008 storage-area-network network-share unc share|improve this question edited Dec 13 '10 at 13:17 asked Nov 23 '10 at 8:26 Mark S. Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password? Have you disabled the AV on the bot server to see if it is the cause?  The AV on the bot server is going to be scanning all outgoing traffic (unless

The Specified Network Name Is No Longer Available Server 2003

Is it really possible that the firewall could be causing this?  I would think that if the firewall was causing the issue it would either work 100% of the time or http://serverfault.com/questions/372193/windows-server-2008-r2-cant-connect-to-shares-using-fqhn-or-ip-system-error-6 In my case uninstalling and restarting computer helped. The Specified Network Name Is No Longer Available Server 2008 R2 Also what AV setup is in place and how is the Celerra integrated with that. –Helvick Dec 4 '10 at 11:55 @Helvick No relevant entries in event logs, neither The Specified Network Name Is No Longer Available Windows 7 My problem is i am not consistently able to connect to the file server.

Robert confirms that Symantec Corporate Antivirus 10.2 does not exhibit the behavior. - Mike Platts 47 years ago Reply Anonymous I had this issue. http://smartnewsolutions.com/the-specified/the-specified-network-password-is-not-correct-net-use.html Browse other questions tagged windows-server-2008 storage-area-network network-share unc or ask your own question. Keep in touch with Experts ExchangeTech news and trends delivered to your inbox every month Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource share|improve this answer edited Apr 8 '16 at 16:03 Lockszmith 1034 answered Dec 9 '10 at 16:59 Scott Forsyth - MVP 13.9k22346 Since the bounty is about to run The Specified Network Name Is No Longer Available Server 2012

For more information, please see the Symantec Knowledge Base article about this issue. This is required because if you have the option System Restore enabled, the system will need additional 500 MB of free disk space for successful installation of Kaspersky Anti-Virus. more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed his comment is here Seriously.

They can change the network switch or manage the network bandwidth to stop this error. The Specified Network Name Is No Longer Available Xp The registry hive to muck with SMB versions is HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters In that hive, add a new DWORD value with the name SMB2 and set the value to 0. Update: Based on the suggestions I'll try a restart of the Workstation service the next time and see if that helps the issue.

Good tip regarding CIFS - I'll try and add an ISCSI LUN the next time too to see if it's related to just CIFS or if it's a general connectivity issue

That is not an exhaustive list, but gives you a start. version 2 Consider what OS your server is trying to connection to. However, this is the case on all my hosts, including the ones where psexec runs properly, so apparently the required ports are open.psexec runs locallyjust fine amongthe target hosts from one Error 64 "the Specified Network Name Is No Longer Available" How helpful is this article: 4 / 5 (56 votes cast) Back to KB search Report a typo on this page: Please select a spelling error or a typo on this

Hot Network Questions How can I render the “that” in “Don’t be like that”? If that fails, recycling the Workstation Service can avoid a reboot, but it's almost as drastic. maybe another kernel-mode app like a backup software ? weblink If you change it to 2 then it will use one object for the root and all subdirectories.

Is there a word for discontent with the present in favor of the past? Could you please add some info on Symantec Antivirus 10.2 (btw, link to it leads to file:/// not web server)? The problem occurs when you have the Autoprotect feature enabled in the applications. Here are two good articles about that: here and here.

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 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 Error: 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.) I did a lot of For DNS trouble-shooting As a Band-Aid and trouble-shooting aid add and entry to the hosts file on your app servers (not the SQL Server) at c:\windows\system32\drivers\etc SQLServerIPAddress SQLServerName Example: 172.16.0.5 ProductionSQLBox

The default timeout is one minute. TcpMaxDataRetransmissions - Reboot Required Key: HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\ParametersDWORD: TcpMaxDataRetransmissionsTry a value of 10.This increases the number of times the Windows TCP implementation will retransmit a data segment before it We have made change in Application to access another server to using IP address as we have static IP network. Registry Settings These registry values must be created on the the SMB client, which is specified in the repository settings as “Gateway server”. Network traces will show the server not responding to the SMB dialect packet.