Error 1208 Windows 8
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows 10Windows 10 MobilePrevious versionsMDOPSurfaceSurface HubLibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: Network error 1208 with NAS Windows 7 IT Pro > Windows 7 Networking Question 0 Sign in to vote I am getting the Network error 1208 with my network error 1208 windows 10 NAS unit when trying to connect.After a google search on this i found it to be
Network Error 1208 Server 2012
very common and no-one with a solution.I can access the NAS with my other PC's with XP and Vista but 7 will only come up network error 1208 windows 7 with this error.Any solutions?Nick Tuesday, June 30, 2009 10:49 AM Reply | Quote All replies 0 Sign in to vote Can you see it in your network map? Can you map it as a network drive? Tuesday, June 30, 2009 1:34
Error 1208 An Extended Error Has Occurred
PM Reply | Quote 0 Sign in to vote Yes i can see it and no i havn't tried to map it as a drive as i never do and i just place a shortcut on my desk top to explore it whenever i need it.Its when i try to go into it that the error apears.Nick Tuesday, June 30, 2009 8:54 PM Reply | Quote 0 Sign in to vote Same problem here. Freecom 500Gb NAS with the latest firmware. XP and Vista works fine, Win7 gives Network error 1208. Is there any new information how to solve he problem? Monday, November 02, 2009 9:33 AM Reply | Quote 1 Sign in to vote Hi, I don't normally do forums, however, i came across this problem and had a look and couldn't find the answer.... Found a work around though....I mapped a network drive to the NAS book from a VISTA machine and then created a shortcut and placed it in the shared folders. Next I connected to the VISTA PC's shared folders from the Windows 7 PC and then copy and paste the shortcut to the desktop. This then maps a drive and also gives access via tghe shortcut to the Freecom NAS drive. Weird I know, but it works.... Thursday, November 19, 2009 3:35 PM Reply | Quote 0 Sign in to vote Great thanks! Thursday, November 19, 2009 8:49 PM Reply | Quote 0 Sign in to vote Windows 7 64 bit Had the same problem with 250G Freecom network drive. Found solution back-up of Registry first and then try Regedit/LocalMachine/System/Current Control Set/Control/LSA Add New key LMCompatabilitylevel set the value to 1 or 2 This worked for me and so hope it does for you Hope this helps Bramham Thursday, January 21, 2010 10:47 PM Reply | Quote 0 Sign in to vote Try this.If you want to map the drive but can't get to it go to Computer and click on "Ma
to 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 https://social.technet.microsoft.com/Forums/windows/en-US/cf59527d-d374-4274-86ae-734e546ccd72/network-error-1208-with-nas?forum=w7itpronetworking 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 third-party file servers and other Windows Systems not on a domain may not not return a signed error response. Therefore, the http://www.squidworks.net/2015/10/network-drives-fail-to-connect-error-1208-and-system-error-2148073478/ 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 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 Sha
next » Print Pages: [1] Go Down Author Topic: Connection Error occured - Error 1208 (resolved) (Read 6912 times) Omni Member Posts: 1 Connection Error occured - Error 1208 (resolved) « on: http://www.komodolabs.com/forum/index.php?topic=737.0 May 27, 2010, 01:28:50 AM » Running the trial edition of NEWT Pro 2.5 on a Windows 2003 SBS server and recieving \"Connection Error occurred (Error 1208: An extended error has occurred.)Any idea\'s, help https://community.emc.com/thread/189992?start=0&tstart=0 or suggestions. Scan completes on the SBS server but fails on the PC\'s that are part of the same domain. Thanks Logged Komodo Support Administrator Member Posts: 760 Springboro, Ohio, USA Connection Error error 1208 occured - Error 1208 (resolved) « Reply #1 on: May 30, 2010, 12:38:46 AM » Hello there. We sincerely apologize for the delay. We usually respond multiple times a day, and at least once a day depending on the time zone.As for this very strange error.. what happens if you just try to visit one of those PCs from Windows Explorer or IE, as in \"\\\\ThePCName\" (no quotes), error 1208 windows from that SBS Server? Logged OlivierH Member Posts: 14 Connection Error occured - Error 1208 (resolved) « Reply #2 on: September 14, 2010, 12:40:59 AM » Any update on this issue. I am also suddenly receiving this message on all my servers. It worked fine about a week ago.Error 1208: An extended error has occurred. Making a UNC connection to the server works fine. Logged Komodo Support Administrator Member Posts: 760 Springboro, Ohio, USA Connection Error occured - Error 1208 (resolved) « Reply #3 on: September 14, 2010, 12:21:30 PM » Hello again. Can you right-click on the error there under the \"Scan Status\" column and paste the error here so we can see it exactly as it appears? That may help. Logged OlivierH Member Posts: 14 Connection Error occured - Error 1208 (resolved) « Reply #4 on: September 14, 2010, 10:33:35 PM » Hi. Here you go:Connection error occurred (Error 1208: An extended error has occurred.) -> Hint: Try visiting \"\\\\AFCPT1SUPP1\" from Windows Explorer or IE.Visiting \\\\afcpt1supp1 works fine. Logged Komodo Support Administrator Member Posts: 760 Springboro, Ohio, USA Connection Error occured - Error 1208 (resolved) « Reply #5 on: September 15, 2010, 12:15:18 PM » Are you enteri
Management Converged Platforms Data Protection Infrastructure Management Platform Solutions Security Storage Dell Products for Work Network Servers Education Partners Programs Highlighted Communities Support » Connect » Developers » Partners » Downloads » 日本語コミュニティ EMC Community Dell Community A AppSync Application Xtender Atmos Avamar C Captiva Celerra Centera CLARiiON Cloud Tiering Appliance Connectrix D Data Domain Data Protection Advisor Disk Library DiskXtender Documentum E ECS eRoom G Greenplum H Host Systems I InfoArchive Isilon ISIS Document Imaging L Leap N NetWorker P PowerPath Prosphere R RecoverPoint Replication RSA S ScaleIO Secure Remote Smarts SourceOne & EmailXtender EMC Storage Analytics Symmetrix U Unity V ViPR Controller Product Communities > Celerra > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. 7 Replies Latest reply: Feb 28, 2014 12:34 PM by dynamox Network error 1208 Fabio_Nanni Feb 27, 2014 8:35 AM Hello,I can't access to the CIFS from a Windows Server 2012 R2. When I try to connect to the CIFS shares via Windows Explorer I get the error "Network error (1208)" after typing the username and password. While the access works from a XP and Windows Server 2003 platforms.Fabio. 1246Views Tags: none (add) support Content tagged with support , celerra_file_server Content tagged with celerra_file_server , celerra Content tagged with celerra 1. Re: Network error 1208 dynamox Feb 27, 2014 8:38 AM (in response to Fabio_Nanni) try disabling SMB Signing on Win2k12 server Report Abuse Like Show 0 Likes (0) 2. Re: Network error 1208 Jeffey Feb 28, 2014 12:36 AM (in response to Fabio_Nanni) I noticed the customer has encounter the same error messages when using windows2012 connect to Isilon (link: http://social.technet.microsoft.com/Forums/windowsserver/en-US/78d2fb4d-267f-4c7b-9766-7a249b8c71cb/ws2012w8-cant-connect-to-isilon-nas-network-error-1208-helpany-ideas?forum=winserver8gen)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. I think Dynamox provided a solution. Report Abuse Like Show 0 Likes (0) 3. Re: Network error 1208 Fabio_Nanni Feb 28, 2014 2:21 AM (in response to Jeffey) How can I check which SMB protocol is enabled on the NAS? Report Abuse Like Show 0 Likes (0) 4. Re: Network error 1208 Fabio_Nanni Feb 28, 2014 2: