Error 1208 Windows 7
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 network error 1208 windows 8 vote I am getting the Network error 1208 with my NAS unit when trying to
Nätverksfel 1208
connect.After a google search on this i found it to be very common and no-one with a solution.I can access the NAS network error 1208 nas windows 7 with my other PC's with XP and Vista but 7 will only come up with this error.Any solutions?Nick Tuesday, June 30, 2009 10:49 AM Reply | Quote All replies 0 Sign in to vote Can you netwerkfout 1208 windows 7 see it in your network map? Can you map it as a network drive? Tuesday, June 30, 2009 1:34 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
Netzwerkfehler 1208 Unter Windows 7
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 ke
we highly recommend that you visit our Guide for New Members. Windows 7, network drives, error 1208 Discussion in 'Windows Vista' started by indecks, May 11, 2009. Thread Status: Not neogamma error 1208 open for further replies. Advertisement indecks Thread Starter Joined: May 11, 2009 Messages: 1 I dvd error 1208 have a 500gb Network drive on my home network, lets say the home network is named "MyHome" and the network drive is
Error 1208 Wii
called Bigboy. I have 3 'computers' total on MyHome. My desktop, my wifes notebook and BigBoy. Here's where you can see it. I can actually see all 3 devices but I keep getting \\Bigboy is inaccessible https://social.technet.microsoft.com/Forums/windows/en-US/cf59527d-d374-4274-86ae-734e546ccd72/network-error-1208-with-nas?forum=w7itpronetworking you might not have permission to use this network resource, contact your administrator blah blah blah error 1208. Now, this was working great 2 hours ago when I was running windowsXP. My wife's notebook (pinky) can access and browse Bigboy without a problem. From MY computer, I can ping Bigboy by name and IP address. Can someone explain to me why windows decided I can't access my own computers? indecks, May 11, 2009 https://forums.techguy.org/threads/windows-7-network-drives-error-1208.826108/ #1 robotb9 Joined: Jun 2, 2009 Messages: 1 This worked for me in Windows 7 and I've seen the same issue connecting XP to Win2000 shares. If you can browse your network and see your NAS drive, which if you are getting 1208 should be the case, one work around you can use is to map the drive to a drive letter. Click on the file explorer. Click on computer. Click on "Map network drive". Select the drive letter you want to assign to the drive. Key in the exact address, e.g., \\myNAS\folders I hope it works for you! robotb9, Jun 2, 2009 #2 This thread has been Locked and is not open to further replies. Please start a New Thread if you're having a similar issue.View our Welcome Guide to learn how to use this site. Show Ignored Content As Seen On Welcome to Tech Support Guy! Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations. If you're not already familiar with forums, watch our Welcome Guide to get started. Join over 733,556 other people just like you! Loading... Similar Threads - Windows network drives New Windows Vista main password, with no recovery disc Compume
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 http://www.squidworks.net/2015/10/network-drives-fail-to-connect-error-1208-and-system-error-2148073478/ browse the shares of another Windows 2012 R2 WorkGroup Server. We kept getting http://www.komodolabs.com/forum/index.php?topic=737.0 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 error 1208 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 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 error 1208 windows 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 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 discussio
next » Print Pages: [1] Go Down Author Topic: Connection Error occured - Error 1208 (resolved) (Read 6910 times) Omni Member Posts: 1 Connection Error occured - Error 1208 (resolved) « on: 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 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 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), 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