I am running a clean install of W7beta and originally has no trouble accessing my network machines including a Buffalo Link station 500Gig NAS.On shutting down recently I have noted several times that Windows is installing updates which is allowed. On restarting I find that all of the internet and other sevices are available including my wifes Vista Laptop; but although I can see Buffalo - Win7 refuses to open it giving me an 0x80070035 code.When this first happened I did a restore and got my system working again - this did not work the second time!What has gone wrong and what am I doing wrong which is more important - My Vista Backups complete reside on the NASKaypee

That error is: ERROR_BAD_NETPATH winerror.h# The network path was not found. Some questions: Where do you see this error? Do you get the same error in Windows Explorer and CMD using NET USE or NET VIEW? If you recently installed windows updates, which ones were they (networking updates happen fairly often for some vendors) - does uninstalling the updates have any affect? Does the same issue occur when you boot in safe mode with networking support?Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

Hi sorry to keep you waiting. I read your message carefully and checked the updates but can find nothing relevant over the period. I shut down totally and re-booted both the Cable modem and router according the specifications - before restarting first the Buffalo and then the two computer stations. Buffalo apears on both but can only be accessed by the Toshiba of my wife running Vista Home Premium I can see Buffalo in Explorer but as soon as I try to expand I get the Cannot access check file name etc and then of course the error code. Net use initially says no entries in list but Net View Shows my Wifes Computer and My Acer plus an entry for Buffalo a space and then Link Station - so it is apparently there. Do I have to physically tell it to use by command or is there something deeper I am missing? I also note that similarly to when Vista first appeared - connectable recognized stations all appeared in the top panel but older machines did not. Similarly when looking at network view Buffalo is noted under the line but with no information on how to connect or re-connect with the other stations and networks. I can connect easily with my Wifes Toshiiba - it is only Buffalo and W7beta which seem to be having a problem. Looking forward to your reply laterin the day. Regards Kaypeene

>I am running a clean install of W7beta and originally has no trouble accessing my network machines including a Buffalo Link station 500Gig NAS.Do you know the IP address that is assigned to the Buffalo? If you have manually assigned an IP address use that or check the router table to see what it is passing out.Try using explorer and log into the Buffalo defalt page 192.168.x.xxx with user name = root, password = (blank, no password). This should bring up the opening page for managing the Buffalo.I just tried this from Win7 to the Buffalo on a Vista network and it sees it right off.Gib

Gib Macs of the Lumber Cartel said: >I am running a clean install of W7beta and originally has no trouble accessing my network machines including a Buffalo Link station 500Gig NAS.Do you know the IP address that is assigned to the Buffalo? If you have manually assigned an IP address use that or check the router table to see what it is passing out.Try using explorer and log into the Buffalo defalt page 192.168.x.xxx with user name = root, password = (blank, no password). This should bring up the opening page for managing the Buffalo.I just tried this from Win7 to the Buffalo on a Vista network and it sees it right off.GibI, too am having this problem with a LanServer NAS drive. I posted about this in another thread with no resolution. You can get to the NAS by typing the path in the address bar but not by clicking on it in the network browser. Below is the message I get: \\SERVERNAME is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. Network error (1208)I don't have any such problems from Vista Ultimate, XP Home, or Kubuntu Linux. I have a couple of suggestions of a Registry Edit and a Policy Edit change to the network security, neither worked.David

Can you try \\servername$nocsc$ ?So if the buffalo was named 'foo' and the share was named 'bar', the UNC path would be:\\foo$nocsc$\bar Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

Ned Pyle [MSFT] said: Can you try \\servername$nocsc$ ?So if the buffalo was named 'foo' and the share was named 'bar', the UNC path would be:\\foo$nocsc$\bar Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team There is no problem getting to the share by typing the path into the address bar. The problem comes when clicking on the share name in the network browser.David

I assume that means you tried using the path I specified and still had an issue? So are you saying that if you put in a UNC name everything works perfectly and you can access all data without issue, but if you browse your way through the share then you have an issue? BTW, I just noticed that you showed up in this thread with a different symptom and errorsand weren't the original poster. Confused me. You'll need a network trace to figure out your issue. Use NETMON 3.2 or Wireshark to get network captures of this working from another machine and failing from thie machine, match the frames, and post the differences here where things break down. Or share out the working and failing captures somwhere we can get to.Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

Ned Pyle [MSFT] said: I assume that means you tried using the path I specified and still had an issue? So are you saying that if you put in a UNC name everything works perfectly and you can access all data without issue, but if you browse your way through the share then you have an issue? BTW, I just noticed that you showed up in this thread with a different symptom and errorsand weren't the original poster. Confused me. You'll need a network trace to figure out your issue. Use NETMON 3.2 or Wireshark to get network captures of this working from another machine and failing from thie machine, match the frames, and post the differences here where things break down. Or share out the working and failing captures somwhere we can get to. Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team Don't understand what your $nocsc$ is for but it doesn't work when I have it in the path. I don't have any trouble accessing the share when I enter the path \\servername\sharename in the explorer address bar. The problem is when I click on the servername in the "Network Browser".David

Hi, It should be compatibility issue between the network drives and Windows 7 beta. I suggest that you change the authentication level on in Windows 7 beta. You can configure this security setting by opening the appropriate policy and expanding the console tree as such: Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\, open Network security: LAN Manager authentication level in the right pane. Change the level to Send LM & NTLM responses. If the issue still occurs, I suggest that you access the device manufacturers websites and try to find firmware upgrade. Arthur Xie - MSFT

Arthur Xie said: Hi, It should be compatibility issue between the network drives and Windows 7 beta. I suggest that you change the authentication level on in Windows 7 beta. You can configure this security setting by opening the appropriate policy and expanding the console tree as such: Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\, open Network security: LAN Manager authentication level in the right pane. Change the level to Send LM & NTLM responses. If the issue still occurs, I suggest that you access the device manufacturers websites and try to find firmware upgrade. Arthur Xie - MSFT Thanks Arthur,The Security Policy change is one of the first things I did. I will check to see if I can find a firmware upgrade for my device. I will post back.David

It appears that I have the latest firmware for my enclosure, so I guess it's time to start looking for a new one.David

I have just come back to this again after a week back on Vista to do some much needed backups.I have tried everything suggested to get the NAS on line but no deal. All the drivers and firmware are up to date but have no effect.In desperation I went to the top and asked Buffalo what the score was. ANSWER: It's a Beta and we ain't going to support it until it gets released!!Didn't we seem toget the same reaction when Vista came out with drivers etc being unsupported?Wouldn't it be great if we were all singing from the same hymn sheet?Come on Microsoft - can't you put a rocket up someones butt - Please........................Kaypee

I have just come back to this again after a week back on Vista to do some much needed backups.I have tried everything suggested to get the NAS on line but no deal. All the drivers and firmware are up to date but have no effect.In desperation I went to the top and asked Buffalo what the score was. ANSWER: It's a Beta and we ain't going to support it until it gets released!!Didn't we seem toget the same reaction when Vista came out with drivers etc being unsupported?Wouldn't it be great if we were all singing from the same hymn sheet?Come on Microsoft - can't you put a rocket up someones butt - Please........................Kaypee Hi!Is there still no solution for this problem?I now have installed the Windows 7 RC 32 Bit - and the problem persists :(My extra-problem is, that I have password-protectet smb-shares on my NAS.I once managed to access it ... but I was never able to repeat this.Any ideas?Don Hans

Hi!Is there still no solution for this problem?I now have installed the Windows 7 RC 32 Bit - and the problem persists :(My extra-problem is, that I have password-protectet smb-shares on my NAS.I once managed to access it ... but I was never able to repeat this.Any ideas?Don Hans I just installed the Windows 7 RC1 last night and I am having the sameproblem....I can not access an older Buffalo LinkStation from the Win7 RC1 system.I can see and access all the other Windows 2000 and XP systems on my home network, but when I click on the LinkStation icon in the Network folder, it wants a user name and password. I use the supposed user name and password I have set up on the LinkStation, but Win7 will never connect. I even set up a new user account with a password on the LinkStation and Win7 will not connect.I won't connect via a command prompt "net use z: \\linkstationname\sharename" either, it just keeps asking for a user name and password.This is strange, as I can bring in a 'foreign' XP system, point it at the LinkStation and it will connect with out asking for a user name or password.IIRC, even a Vista system will connect with out asking for a user name or password.So, seems MS has broken basic networking again....managed to make something that USED to be simple....impossible.

Hi!Is there still no solution for this problem?I now have installed the Windows 7 RC 32 Bit - and the problem persists :(My extra-problem is, that I have password-protectet smb-shares on my NAS.I once managed to access it ... but I was never able to repeat this.Any ideas?Don Hans I just installed the Windows 7 RC1 last night and I am having the sameproblem....I can not access an older Buffalo LinkStation from the Win7 RC1 system.I can see and access all the other Windows 2000 and XP systems on my home network, but when I click on the LinkStation icon in the Network folder, it wants a user name and password. I use the supposed user name and password I have set up on the LinkStation, but Win7 will never connect. I even set up a new user account with a password on the LinkStation and Win7 will not connect.I won't connect via a command prompt "net use z: \\linkstationname\sharename" either, it just keeps asking for a user name and password.This is strange, as I can bring in a 'foreign' XP system, point it at the LinkStation and it will connect with out asking for a user name or password.IIRC, even a Vista system will connect with out asking for a user name or password.So, seems MS has broken basic networking again....managed to make something that USED to be simple....impossible. I too, had problems with this on the public beta. Could not access the drive in the network browser. Had to type the path in the windows explorer address bar. But I havea new NAS and it's working perfectlyon the RC (no username or password requests). My new NAS is a LaCie HipServ.David

I have just come back to this again after a week back on Vista to do some much needed backups.I have tried everything suggested to get the NAS on line but no deal. All the drivers and firmware are up to date but have no effect.In desperation I went to the top and asked Buffalo what the score was. ANSWER: It's a Beta and we ain't going to support it until it gets released!!Didn't we seem toget the same reaction when Vista came out with drivers etc being unsupported?Wouldn't it be great if we were all singing from the same hymn sheet?Come on Microsoft - can't you put a rocket up someones butt - Please........................Kaypee Hi!Is there still no solution for this problem?I now have installed the Windows 7 RC 32 Bit - and the problem persists :(My extra-problem is, that I have password-protectet smb-shares on my NAS.I once managed to access it ... but I was never able to repeat this.Any ideas?Don Hans Hi - sounds familiar I am afraid.I too am now running the RC because I love W7 for all the good things about it! Microsoft Please take note!I refuse to go out and buy yet another piece of expensive equipment to overcome what is probably a minor glitch - after all - the other Windows systems operate happily with the Buffalo regardles of what internal OS it is running. There is nothing in the Buffalo instructions to aid in the search either - and my original mails indicate there is unlikely to be anything soon, although the outing on the general public of Win 7 RC should be shaking someones tree!I had hoped that after the correspondence of all of us suffering similar problems there would have been some response - if only a promise of a future solution but it seems as if silence is golden for all the wrong reasons.I am currently backing up my computer in extreme compressed format to my wifes Toshiba over the network (she runs VistaHome) and then copying the files from her machine to the Buffalo server to my storage folders.!! Restore would follow a similar route.This is not what home networks were designed for, folks!Anyone had better luck recently?Kaypee

Hi, It should be compatibility issue between the network drives and Windows 7 beta. I suggest that you change the authentication level on in Windows 7 beta. You can configure this security setting by opening the appropriate policy and expanding the console tree as such: Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\, open Network security: LAN Manager authentication level in the right pane. Change the level to Send LM & NTLM responses. If the issue still occurs, I suggest that you access the device manufacturers websites and try to find firmware upgrade. Arthur Xie - MSFT OK, progress!I tried the above suggestion...stumbled around in Administrative Tools, Local Security Policies, Security Options, Lan Manager authentication level, and changed it from whatever it was (didn't make note of it) to "Send LM & NTLM responses" andapplied it.I then double-clicked on my LinkStation in the Network folder in Windows Explorer and when it prompted me for a user name and password, I put in what is the matching pair that should have worked....it didn't.I then used the alternate account login option...and put in the new user name/password pair I set up the other evening, and it connected me to the LinkStation and all the shares on it.So now I can map a drive letter to the main storage area on it. I will test logging off and then re-connecting and report back shortly.OK, back....upon logging back in, the mappeddrive wouldn't re-connect.However, I discovered that I did not have a password on my user account on the Win7 system (I had removed it the other evening trying to connect to the LinkStation). After I added one back in, and used my regular name/password pair, I was able to connect to the LinkStation as myself. It also re-connects automatically upon logging back in again.This did not work the other evening, but since the change to the LanMan authentication level, it seems to be working as it should, and as it does on Win2K systems and XP systems (those both still do not ask for a name/password to connect to the LinkStation), but at least I can connect to the LinkStation on Win7 now.

Hallelujha - After going back to Vista to get some back ups done - I returned to Win 7 RC and found a couple of new downloads required to be installed via UPDATE - Lo and behold but the Buffalo is online and running perfectly.Whatever you did - thank you Microsoft - I haven't changed anything - Hope this worked for everyone else as well

I have two NAS boxes that I can't access directly anymore with Win7. One is the Hawking HNAS1, and I have the latest firmware from Hawking. The other is the Metalgear 3507, also with the latest firmware. The interesting thing is that I get a different error for each of them. Both of them run "wide open" with no login requirement. For the Hawking HNAS1: \\HAWKING is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. A remote procedure call (RPC) protocol error occured. For the Metalgear I sometimes get that same error, but I've also gotten the 1208 error at times. I can actually use my favorite sync application to access them, Beyond Compare. If I have a profile that access the units directly, it handles it with no issue. However, if I try to browse to them with Explorer, I get the crash. THis is a similar issue with Vista, however it was half solved when I applied the "Send LM & NTLM responses" fix to network responses. The Metalgear works fine with Vista with that change, but the Hawking still doesn't. Since it's obvious that Windows networking can indeed access these boxes in both Vista and Win7, I am at a total loss as to why Microsoft deemed it OK for Explorer to barf on accesses to them Obviously, this is because both of these units use an older version of Linux with SAMBA. There really should be a work-around that can be used to offer compatibility to such units, since it's unlikely they'll ever be updated. My D-Link DNS-323 works flawlessly with both Vista and Win7. MVP - Windows Desktop Experience

It is not windows at fault here, It issamba which needs an update (and has needed a LONG time)You can dumb down (weaken security)windows so it will talk to the NAS boxes / print serversfrom THIS thread....click the start button and type secpol.msc in the search function to start. Quote----Hi, It should be compatibility issue between the network drives and Windows 7 beta. I suggest that you change the authentication level on in Windows 7 beta. You can configure this security setting by opening the appropriate policy and expanding the console tree as such: Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\, open Network security: LAN Manager authentication level in the right pane. Change the level to Send LM & NTLM responses. If the issue still occurs, I suggest that you access the device manufacturers websites and try to find firmware upgrade. Arthur Xie - MSFTEnd quoteWe had to this in Vista as well.

Obviously, you missed where I said I had already done that with no effect on the errors. There is no update for the boxes, otherwise I wouldn't be concerned about this. MVP - Windows Desktop Experience

Hello outthere!I got a kind of "solution" ...it's not great - but it seems to work:- by entering the path to the (password-protected) sama-share on my nas I get the login-window (ex. \\nas\protectedshare).- then I enter any username (except "guest" or any other windows-log-in-name)- the password follows- and then I have toWAIT about a minute and after thispress enter- e voil: I can access the protected shareit's annoying that I have to wait - but better than nothing!entering only "\\nas " still causes error 1208 ...Greetings,Don Hans

I solved mine a different way, I've outlined how I got the two working in a separate thread here: http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/5915762b-2724-4652-9dc5-d1d34923bd25 FWIW, there's no waiting with this method, I have immediate access to both of the boxes. It appears that this is something pretty high up in the food chain in networking, since the lower level networking obviously has no issue talking to these boxes! MVP - Windows Desktop Experience

thank you!Iknew thissolution.But it was talking about password-protected shares ... ;)

Take the password off. ;)MVP - Windows Desktop Experience

This worked for me! "I tried the above suggestion...stumbled around in Administrative Tools, Local Security Policies, Security Options, Lan Manager authentication level, and changed it from whatever it was (didn't make note of it) to "Send LM & NTLM responses" and applied it." Windows 7 Ultimate 64 with Buffalo Linkstation HD-H250LAN. Thanks!