Error 1208
Deutsch Version Russian IDEAL Administration IDEAL Alerter IDEAL Remote IDEAL Migration IDEAL Dispatch IDEAL Secure Download Order / Estimate Prices Support FAQ Free POINTDEV Espace Reva 2 alle Josime MARTIN 13160 CHATEAURENARD FRANCE Tel: 33 4 32 62 71 34 Fax: 33 4 32 62 71 35 FAQ: IDEAL Administration | IDEAL Dispatch | IDEAL Remote | IDEAL Migration | IDEAL Alerter | IDEAL Secure FAQ : IDEAL Administration Centralized Administration for Windows Active Directory Domains and Workgroups Network general errors How to troubleshoot the "[1208] An extended error has occured" message ? When i try to access a physical resource on my network (server or computer) with your software, I get sometimes the "[1208] An extended error has occured" message. What can I do ? The message "[1208] An extended error has occured" is a common native message of Microsoft Windows Operating System and is not directly related to Pointdev softwareTo resolve this error, please verify the following points : Check that you can ping with the CMD prompt the remote host (by its IP address or by its physical NetBIOS name), and that the host answers without significant packet loss. If the remote host does not answer when it is pingued by its hostname but answer when pingued with its IP address, please check on the remote host the DNS properties. This point should be considered because a good many functionalities of our products use the name resolution when trying to to access remot hosts. This issue may be also due to a synchronization problem between the time of the remote computer and the time of your administration computer, or the time between the PC and the DC (Domain Controller). After verifying that basic network connectivity exists, you can force time synchronization on a computer by running this command: net time /domain /set.
Last modification: 04/15/2011 << PreviousNext >> SOFTWARE IDEAL Administration IDEAL Dispatch IDEAL Remote IDEAL Migration IDEAL Alerter IDEAL Secure IDEAL Admin Pack SERVICES Download Request Quote How to Buy Pricing Technical Support Give your opinion FAQ Free SITEMAP Home Contact us Pointdev References Resellers My Account Customer testimonials Legal notice POINTDEV Espace Reva 2 allee Josime MARTIN 13160 CHATEAURENARD FRANCE Tel: +33 (0) 4 32 62 71 34 Fax: +33 (0) 4 32 62 71to connect error 1208 and System error 2148073478 On October 2, 2015, in How-to, by Cubert aka (Cube Dweller) We had a problem where a Windows 2012 R2 Domain Controller would not browse the shares of another Windows 2012 R2 WorkGroup Server. We kept getting error 1208 and then we tried to force a mapping to share and received System error 2148073478 This problem is caused by the "Secure Negotiate" feature that was added to SMB 3.0 for Windows Server 2012 and Windows 8. This feature depends upon the correct signing of error responses by all SMBv2 servers, including servers that support only protocol versions 2.0 and 2.1. Some http://www.pointdev.com/en/faq/faq-ideal-administration-windows-error-1208-an-extended-error-has-occured-id-655.html third-party file servers and other Windows Systems not on a domain may not not return a signed error response. Therefore, the connection fails. We had this issue with a Windows 2012 R2 Domain Controller trying to connect to a Windows 2012 workgroup server share. The Domain Controller had the local network set to Public and not Private, We had to change this by running a few PoSh commands. Get-NetConnectionProfile This gives http://www.squidworks.net/2015/10/network-drives-fail-to-connect-error-1208-and-system-error-2148073478/ us the index numbers for each interface then we find the interface marked public and change it to Private by running the PoSh command Set-NetConnectionProfile -InterfaceIndex 10 -NetworkCategory Private Change the InterfaceIndex number to the number of your interface. Next we need to low the security level for SMB so that we can allow the connection to complete. To do this we Edit the registry and change the value of RequireSecureNegotiate to zero Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters" RequireSecureNegotiate -Value 0 -Force Once that has completed you will now be able to access your network shares on other NAS servers or Windows systems. Hope this helps someone out there, Enjoy! Cubert Share this:FacebookLinkedInPrintEmailLike this:Like Loading... Tagged with: File share • NAS • network • SMB • Storage • Windows • windows 2012 Leave a Reply Click here to cancel reply. Name (required) Mail (will not be published) (required) Website CAPTCHA Code* Notify me of follow-up comments by email. Notify me of new posts by email. Systems Engineers HQ! Thanks for dropping by! Feel free to join the discussion by leaving comments, and stay updated by subscribing to the RSS feed. "Twitter messages not available." —Politicaliyinc LabTech Plugin Downloads ADMON Admin Group Monitor Plugin Agent Status Plugin Announce Maintenance Plugin AppassureD Backup Manager Plugin Apt
PKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response https://support.symantec.com/en_US/article.TECH108571.html Security Simulation Website Security SSL Certificates Complete Website Security https://community.sophos.com/kb/en-US/118209 Code Signing Certificates Norton Shopping Guarantee Buy SSL Products A-Z Services Services Home Business Critical Services Consulting Services Customer Success Services Cyber Security Services Education Services Solutions Solutions Home Topics Encryption Everywhere Internet of Things Next error 1208 Generation Endpoint Office 365 Industries Automotive Cyber Insurance Education Financial Services Global Service Providers Industrial Control Systems Healthcare Retail Government Federal Government State & Local Support Center Technical Support Symantec Connect Buying Programs Upgrades Maintenance & Renewals Training Security Center Security Center Home Blogs ISTR error 1208 Threats Virus Definitions and Security Updates Removal Tools Partner Find a Partner Become a Partner Login Required Login into Partner Portal Partner Licensing Partner Renewals Partner Training Margin Builder Opportunity Registration Financial Benefits English 中文(简体) 中文(繁體) Česká English Français Deutsch Magyar Italiano 日本語 한국어 Polski Português Pусский Español Site: Symantec Enterprise Small Business Norton United States Search Support Home Support Home MySymantec Licensing Products A-Z SYM16-015 Security Advisory Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' Error: "Error 1208 Network error" when navigating to a system, workgroup, or domain TECH108571 October 30th, 2013 http://www.symantec.com/docs/TECH108571 Support / Error: "Error 1208 Network error" when navigating to a system, workgroup, or domain Did this article resolve your issue? Thank you for your feedback! Provide feedback on this article Re
Home Sophos UTM 9 Sophos XG Firewall Web Appliance General Malware [Beta] Malware Course Sophos Intercept X Sophos Wireless Knowledge Base Blog Knowledge Base Advisories +Data Control and DLP Email Appliance +Endpoint Security and Control +Free antivirus & tools for desktops +General +Mobile device protection +PureMessage +Reflexion +SafeGuard encryption +Server protection & integration Sophos Clean +Sophos Cloud Sophos Home +Sophos UTM 9 +Sophos XG Firewall Web Appliance Tweets by @SophosSupport An endpoint computer fails to update ('Could not contact server') Article ID: 118209 Updated: 15 Aug 2016 19 people found this helpful Available in: English | Español | Italiano | 日本語 | Français | Deutsch Issue Sophos Endpoint Security and Control fails to update. You see one of the following problems on the endpoint computer: A cross on the Sophos shield Could not contact server Updating failed Sophos Endpoint Security and Control has failed to download updates. Sophos Protection Updating: failed First seen in Sophos Endpoint Security and Control 10.0 Cause There are various causes but the most common ones are: Sophos AutoUpdate (SAU) is incorrectly configured: The address attempting to be contacted is invalid or unreachable. The username is incorrect. The password is incorrect or has expired. The computer is experiencing network connectivity problems. What To Do Before following the advice below it is recommended that you confirm the following: The computer is fully connected to your network (and the Internet if updating from Sophos). The address Sophos AutoUpdate is attempting to contact is correct. This could either be a UNC path or HTTP address to a share hosted on your network or the one word address of 'Sophos' (without quotes) if updating from our databanks. Note:We use 'Sophos' so the exact address can be changed by us inside the product without affecting your configuration. The username is correct - either a valid account for your network (if connecting to a local/remote share) or a valid and active username issued by Sophos (if connecting to the address 'Sophos')