Network Error 1208

[spamnchips]

I have a small home network connecting 2 PC's and a NAS drive. The network is hard wired using CAT 5 and there is also a wireless AP for the Wii console. When both PC's used XP either could access (read and write) to the NAS which is mainly used to store digital photos. Since upgrading one PC to Windows 7 I cannot access the NAS from this PC. I can see the drive and can logon via web brwoser to conduct maintenance but cannot read or write using Windows Explorer. I always get the Netwrok Error 1208 statement. I suspect it is to do with new security protocols in Windows 7 not talking to older Samba software. Could someone offer some help please ?

 

[zigzag3143]

I have a small home network connecting 2 PC's and a NAS drive. The network is hard wired using CAT 5 and there is also a wireless AP for the Wii console. When both PC's used XP either could access (read and write) to the NAS which is mainly used to store digital photos. Since upgrading one PC to Windows 7 I cannot access the NAS from this PC. I can see the drive and can logon via web brwoser to conduct maintenance but cannot read or write using Windows Explorer. I always get the Netwrok Error 1208 statement. I suspect it is to do with new security protocols in Windows 7 not talking to older Samba software. Could someone offer some help please ?

Might also be homegroup and IPv6. Homegroup is for Win 7 machines only. Since you have a mixed network it shoud be using "workgroup" model. You can verify that by simply making a new network using workgroup. If it works you can then disable IPv6 and kill homegroup.


Ken J

 

[spamnchips]

Thanks for the suggestion. I was joined in a homegroup as well as a workgroup. I removed the Homegroup but it still does not work.

 

[spamnchips]

Network Error - 1208 - Update

I reported this fault to Microsoft Technical Support who have been really helpful. It appears that quite a few people have been reporting this issue and some "fixes" work on some machines but not on others. Microsoft took control of my machine remotely and checked through the registry etc but everything was set OK and should have accessed the NAS. Antivurs software was removed but that did not work either. This problem has now been passed upward to the Research unit to find cause and solution. I can gain access by mapping the drive i.e. \\NAS\Public on my machine works, but direct access (double clicking) on the drive fails.

I will give some feedback when the matter is resolved.

 

[lightfinger]

I had the same issue working to my Smb server. Iomega NAS

Go to local Security policies -> Local Policies -> Security Options

Go to Network Security: Lan Manager Authentication Level

Change the value : Send LM and NTLM responses -> Send NTLM Responses Only

Also : Untick both options in Network Security: Minimum session security for NTLM SSP based ( No minimum)

That worked for me

 

[spamnchips]

Thanks for your suggestion. My PC already has these settings and they heve been checked many times by Microsoft. It appears that this is a real issue which Microsoft are researching.

 

[bowest]

Hi - I've got the same error as you - do you mind posting here any resolution if microsoft ever come up with any thing please?

cheers

 

[spamnchips]

I will be happy to but at the moment they seem stumped. It appears that Windows 7 is sending the correct information to the NAS. Unfortunately the NAS does not respond from the root level. I have another machine running on the network using Vista which does work OK. It appears that the issue lies with the Security and Permissions difference added in Windows 7. I can access the drive by mapping it which in my case is simply \\NAS\Public.

 

[spamnchips]

My last contact with Microsoft was that at the moment they are unable to offer a workable fix. The issue has now been passed back to the development team. Windows Vista and Windows 7 both pass and receive messages from the NAS which at root level responds with an error. Vista ignores the error and connects but Windows 7 will not. It looks as though the version of Samba on the NAS is now too old to talk to whatever protocols Microsoft are now using. The supplier of my NAS (Safecom) do not respond to my e-mails (perhaps they no longer exist). I have installed NAS-BASIC49b2 as firmaware but unless there is further development of this software to correct the error for Win 7 then I will have to stick to the drive mapping route or FTP, which also works. Yet another case of Windows losing its backward capability. Could this be the way the computer industry forces us to keep buying new kit while there is nothing wrong with the old stuff ?

 

[Usodimare]

Any news on the thread?

After having updated from Windows Vista to Windows 7 Home Premium, i am experiencing the same problem.
The samba share of NAS wired on my home network (LogiLink UA0056 case, housing Maxtor 250GB IDE HDD connected via Cat5) is no more accessible (it was in Vista).
I can access its http management URL and i can also ftp-ing it from the external. When trying to access from Windows Explorer, Network Error 1208 is reported.
Trying to map it does not help.
Is there any fix for that problem?
Thank you for the support.

Usodimare

My last contact with Microsoft was that at the moment they are unable to offer a workable fix. The issue has now been passed back to the development team. Windows Vista and Windows 7 both pass and receive messages from the NAS which at root level responds with an error. Vista ignores the error and connects but Windows 7 will not. It looks as though the version of Samba on the NAS is now too old to talk to whatever protocols Microsoft are now using. The supplier of my NAS (Safecom) do not respond to my e-mails (perhaps they no longer exist). I have installed NAS-BASIC49b2 as firmaware but unless there is further development of this software to correct the error for Win 7 then I will have to stick to the drive mapping route or FTP, which also works. Yet another case of Windows losing its backward capability. Could this be the way the computer industry forces us to keep buying new kit while there is nothing wrong with the old stuff ?

 

[spamnchips]

Unfortunatley there is no fix from Bill Gates' boys. It would appear that older NAS drives are not supported by the latest versions of Windows (like so much still usable hardware and software). The work around is to "map a network drive" manually. For example on my machines I have to map the drive by typing in the \\nas\public address which finds the drive OK. Hope this helps.

Regards
John

 

[AmbrosialPariah]

I have a small home network connecting 2 PC's and a NAS drive. The network is hard wired using CAT 5 and there is also a wireless AP for the Wii console. When both PC's used XP either could access (read and write) to the NAS which is mainly used to store digital photos. Since upgrading one PC to Windows 7 I cannot access the NAS from this PC. I can see the drive and can logon via web brwoser to conduct maintenance but cannot read or write using Windows Explorer. I always get the Netwrok Error 1208 statement. I suspect it is to do with new security protocols in Windows 7 not talking to older Samba software. Could someone offer some help please ?

I dont remeber where, but I have seen issues with Win 7 and NAS solutions. Check with google and Manufacturer it had something to do with Windows 7 interperting the date wrong from the NAS. The below should fix it. If not check with the manufacturer for updated firmware.

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

 

[brady]

computer browser service on and set to automatic?

 

[AmbrosialPariah]

computer browser service on and set to automatic?

The Computer Browser is wwhat controls which computer keeps an index of currently workgrouped comps. Automatic means if needed it will be master disabled means that computer will never become master and keep the index. You may not notice any difference all the way up until there are no Master Browser computer and you lose all computers in your network neighborhood listing. You can still connect via IP or DNS [DNS sometimes] but it does not hurt or change much of anything I HIGHLY SUGGEST YOU LEAVE IT ON AUTO

 

[asarisoy]

i found the solution
click map nework drive
choose "connect to a Web site that you can use to store your document and pictures"
this is all the way at bottom of the page
chose "next"
choose "choose a custom network location"
choose "next"
put the ip address of your storage device and share folder" \\***.***.***.***\<share name>
choose "next"
there you have it !!!!!!
this is win 7 64 bit home edition
let me know if its work

 

[Usodimare]

Dear Asarisoy,
no problem to map the NAS to access the files stored there, i've already done that.
However that's a backdoor, i would like to have the NAS accessible via the network as i did with Vista and i currently do with Linux. It isn't exactly the same think... It is absolutely bizarre that the files are there, i can map (mount) the Drive (so the system recognise it), but i cannot access it in the most simple and direct way.
That is OS bug, no doubt at all. I have recently installed Windows 7 SP1, but no fix for NetErr 1208.
However thank you for the suggestion.
Usodimare